Platform support for fabric8-launcher/launcher-application on PowerPC64LE

[sarveshtamba]

• I have been able to successfully deploy fabric8-launcher/launcher-operator on PowerPC64LE as mentioned in "Route Laucher not found on PPC64LE launcher-operator#50 (comment)"

• Currently working on step to "Install the Launcher (via the installed operator)". Facing issues with the example launcher yaml which makes use of image: fabric8/launcher-backend:latest, which for now is available only for x86_64.

• I was facing the below failures on ppc64le while building fabric8/launcher-backend:

08:57:58.095 [main] INFO io.specto.hoverfly.junit.core.TempFileManager - Selecting the following binary based on the current operating system: hoverfly_linux_amd64

08:57:58.280 [Thread-2] INFO hoverfly - /root/fabric8/src/github.com/launcher-application/base/target/hoverfly.8425973283270400848/hoverfly_linux_amd64: /root/fabric8/src/github.com/launcher-application/base/target/hoverfly.8425973283270400848/hoverfly_linux_amd64: cannot execute binary file

• Built hoverfly for ppc64le successfully using https://github.com/SpectoLabs/hoverfly and then tried to use this locally built hoverfly installation in the fabric8/launcher-backend build. However I was not successful in that, so by-passed the test cases which made use of hoverfly(by deleting temporarily):-

deleted:    ../base/src/test/java/io/fabric8/launcher/base/http/HttpClientTest.java
deleted:    ../core/core-impl/src/test/java/io/fabric8/launcher/core/impl/identity/KeycloakIdentityProviderHoverflyTest.java
deleted:    ../core/core-impl/src/test/java/io/fabric8/launcher/core/impl/identity/KeycloakPublicKeyProviderHoverflyTest.java
deleted:    ../services/git-service-impl/src/test/java/io/fabric8/launcher/service/git/OAuthTokenProviderHoverflyTest.java
deleted:    ../services/git-service-impl/src/test/java/io/fabric8/launcher/service/git/bitbucket/BitbucketServiceTest.java
deleted:    ../services/git-service-impl/src/test/java/io/fabric8/launcher/service/git/gitea/GiteaServiceTest.java
deleted:    ../services/git-service-impl/src/test/java/io/fabric8/launcher/service/git/github/GitHubServiceTest.java
deleted:    ../services/git-service-impl/src/test/java/io/fabric8/launcher/service/git/gitlab/GitLabServiceTest.java

• With this the build proceeded ahead, however it fails at the below step:-

[INFO] --- frontend-maven-plugin:1.8.0:install-node-and-yarn (install node and yarn) @ launcher-frontend ---
[INFO] Installing node version v11.12.0
[INFO] Unpacking /root/.m2/repository/com/github/eirslett/node/11.12.0/node-11.12.0-linux-ppc64le.tar.gz into /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/tmp
[INFO] Copying node binary from /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/tmp/node-v11.12.0-linux-ppc64le/bin/node to /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/node
[INFO] Installed node locally.
[INFO] Installing Yarn version v1.13.0
[INFO] Unpacking /root/.m2/repository/com/github/eirslett/yarn/1.13.0/yarn-1.13.0.tar.gz into /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/yarn
[INFO] Installed Yarn locally.
[INFO]
[INFO] --- frontend-maven-plugin:1.8.0:yarn (yarn install) @ launcher-frontend ---
[INFO] Running 'yarn ' in /root/fabric8/src/github.com/launcher-application/frontend/target/frontend
[INFO] node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for launcher-parent 1-SNAPSHOT:
[INFO]
[INFO] launcher-parent .................................... SUCCESS [  3.589 s]
[INFO] launcher-base-test ................................. SUCCESS [  3.395 s]
[INFO] launcher-base ...................................... SUCCESS [  7.860 s]
[INFO] launcher-creator ................................... SUCCESS [ 59.977 s]
[INFO] launcher-service-git-api ........................... SUCCESS [  1.927 s]
[INFO] launcher-service-openshift-api ..................... SUCCESS [  1.657 s]
[INFO] launcher-core-api .................................. SUCCESS [  3.983 s]
[INFO] launcher-service-git-impl .......................... SUCCESS [  5.672 s]
[INFO] launcher-service-openshift-impl .................... SUCCESS [  4.156 s]
[INFO] launcher-core-impl ................................. SUCCESS [  9.747 s]
[INFO] launcher-frontend .................................. FAILURE [  2.773 s]
[INFO] launcher-app ....................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:47 min
[INFO] Finished at: 2019-09-25T08:24:12-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.8.0:yarn (yarn install) on project launcher-frontend: Failed to run task: 'yarn ' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :launcher-frontend

• I also built Node 11.12.0 locally on ppc64le successfully to workaround the above issue , but I was not able to make use of this in fabric8/launcher-backend build.

Any help towards this would be greatly appreciated.

[gastaldi]

@sarveshtamba hi! Thank you for looking into this. Unfortunately we don't have access to a ppc64le machine to test this, but I think you also need to build yarn to achieve that. About the Hoverfly tests, you can skip them using mvn clean install -DskipTests

We also currently have no plans to support ppc64le at the moment, but would be glad if you could make it work.

[sarveshtamba]

Hi @gastaldi

The build system seems to be fetching & installing it's own version of node package and not using the one I built locally which is causing the issue:-

[INFO] Unpacking /root/.m2/repository/com/github/eirslett/node/11.12.0/node-11.12.0-linux-ppc64le.tar.gz into /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/tmp
[INFO] Copying node binary from /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/tmp/node-v11.12.0-linux-ppc64le/bin/node to /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/node
[INFO] Installed node locally.
[INFO] Installing Yarn version v1.13.0
[INFO] Unpacking /root/.m2/repository/com/github/eirslett/yarn/1.13.0/yarn-1.13.0.tar.gz into /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/yarn
[INFO] Installed Yarn locally.
[INFO]
[INFO] --- frontend-maven-plugin:1.8.0:yarn (yarn install) @ launcher-frontend ---
[INFO] Running 'yarn ' in /root/fabric8/src/github.com/launcher-application/frontend/target/frontend
[INFO] node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node)

Any way I can force the build system to use the node version that I have built locally?

[gastaldi]

Looking at https://github.com/eirslett/frontend-maven-plugin#frontend-maven-plugin I don't think that's possible, since it always attempt to download it first. Perhaps instead of installing yarn through the plugin you could run a npm install yarn -g?

[sarveshtamba]

Hi @gastaldi , using node v12.11.0 as below worked fine and I was able to complete the maven build:

diff --git a/frontend/pom.xml b/frontend/pom.xml
index f443c4e3..7d894672 100644
--- a/frontend/pom.xml
+++ b/frontend/pom.xml
@@ -30,7 +30,7 @@
               <goal>install-node-and-yarn</goal>
             </goals>
             <configuration>
-              <nodeVersion>v11.12.0</nodeVersion>
+              <nodeVersion>v12.11.0</nodeVersion>
               <yarnVersion>v1.13.0</yarnVersion>
             </configuration>
           </execution>

[gastaldi]

Excellent! Want to provide a PR with this change?

[sarveshtamba]

@gastaldi sure, will raise a PR for this soon.

[sarveshtamba]

@gastaldi raised PR "#1004"

[gastaldi]

Closed in 1f1d6db