odidev commented on issue #5026: URL: https://github.com/apache/openwhisk/issues/5026#issuecomment-829162194
@rabbah Thank you for the response. I have again forked the repo and the ansible issue has not occurred again. I have replicated the travis jobs for arm64-graviton2, and have come across the issue with epmd services for ARM64. It seems that `sudo systemctl stop epmd.socket epmd.service` command does not work for ARM64, and shows the below error: ~~~ Failed to stop epmd.socket: Unit epmd.socket not loaded. Failed to stop epmd.service: Unit epmd.service not loaded. ~~~ As the script is already stopping epmd sockets and services, I have skipped this command for ARM64 and moved ahead. Another issue I have faced is related to the `com.google.protobuf:protoc:3.4.0` dependency. ~~~ Execution failed for task ':core:scheduler:generateProto'. > Could not resolve all files for configuration ':core:scheduler:protobufToolsLocator_protoc'. > Could not find protoc-linux-aarch_64.exe (com.google.protobuf:protoc:3.4.0). ~~~ Protoc version 3.4.0 is not available for AArch64. And the maven protoc support for AArch64 is launched from version 3.5.0 onwards. I have analysed that this dependency is not directly used in openwhisk. After running openwhisk in debug mode, I have analysed that the exceptions come from gradle. It seems that gradle implements the protoc dependency in openwhisk. Openwhisk uses gradle version 5.5.1, which does not directly contain protoc dependency in the source code. However, the latest version of gradle has protoc defined in the source code with the updated version. I have tried upgrading gradle to the latest version, but it seems that the dependency ‘build-scan’ is not compatible with the gradle version greater than 5.6. Do you have any plans to upgrade gradle to the latest version 7.0? If yes, then it will be helpful in adding ARM64 support to openwhisk. Please suggest your opinion on this, and provide some pointers on the same. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
