E2E tests failing on Power - FATA[0004] Failed to build test binary

[shreyakajbaje]

E2E tests running on Minikube setup throwing below error -

./operator-sdk test local ./test/e2e --verbose --debug --operator-namespace default --global-manifest ./deploy/crds/wildfly.org_wildflyservers_crd.yaml --namespaced-manifest ./deploy/operator.yaml --image "localhost:5000/wildfly-operator:latest"
DEBU[0000] Debug logging is set
INFO[0000] Testing operator locally.
DEBU[0000] Running []string{"go", "test", "-mod=vendor", "./test/e2e/...", "-namespacedMan", "./deploy/operator.yaml", "-globalMan", "./deploy/crds/wildfly.org_wildflyservers_crd.yaml", "-root", "/home/go/src/github.com/wildfly/wildfly-operator", "-parallel=1", "-skipCleanupOnError=false"}
time="2023-02-01T03:23:23Z" level=fatal msg="Failed to create framework: failed to build the kubeconfig: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable"
FAIL github.com/wildfly/wildfly-operator/test/e2e 0.065s
FAIL
FATA[0004] Failed to build test binary: failed to exec []string{"go", "test", "-mod=vendor", "./test/e2e/...", "-namespacedMan", "./deploy/operator.yaml", "-globalMan", "./deploy/crds/wildfly.org_wildflyservers_crd.yaml", "-root", "/home/go/src/github.com/wildfly/wildfly-operator", "-parallel=1", "-skipCleanupOnError=false"}: exit status 1
make: *** [Makefile:73: test-e2e-minikube] Error 1

Minikube cluster configurartion -

• [minikubeN] minikube v1.27.0 on Centos 8 (ppc64le)
• Kubernetes 1.25.0 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.25.0
• Using the docker driver based on existing profile
• Starting control plane node minikubeN in cluster minikubeN
• Pulling base image ...
• Updating the running docker "minikubeN" container ...
• Preparing Kubernetes v1.23.15 on Docker v20.10.17 ...
• Verifying Kubernetes components...
  • Using image gcr.io/k8s-minikube/storage-provisioner:v5
• Enabled addons: storage-provisioner, default-storageclass
• Done! kubectl is now configured to use "minikubeN" cluster and "default" namespace by default

looks quay.io images being used are not available for power. will it be possible to share dockerfiles for the same?

[yersan]

Hi @shreyakajbaje

It seems you are using an old branch. There is some documentation about how to run the Operator tests (either in local or deploy mode) with a local Minikube cluster: e.g https://github.com/wildfly/wildfly-operator#run-end-to-end-e2e-tests-in-local-mode

Did you follow the instructions described there?

[shreyakajbaje]

Hi @yersan, Thank you for your response. Yes I have followed these instructions for local mode.

[yersan]

Ok, that's weird, your error trace describes the uses of ./operator-sdk test local, which makes me think your branch is lagging behind the main. Can you double-check if you are using the main branch and if your local repository is up to date with the remote one?

[shreyakajbaje]

Yes repository is up to date