-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
True
-
-
False
-
-
Steps to reproduce:
- Run OPCT with flag --sonobuoy-image <image> set, and check the image deployed:
$ ~/opct/bin/opct-devel run -w --sonobuoy-image docker.io/sonobuoy/sonobuoy@sha256:ea6855f836358e416fab82eb15629177331767e28cf90f7c730c2edd3857ce0c
$ oc get pods -n openshift-provider-certification
NAME READY STATUS RESTARTS AGE
sonobuoy 0/1 Error 0 10s
$ oc describe pod -n openshift-provider-certification sonobuoy |grep -i image
Image: quay.io/ocp-cert/sonobuoy:v0.56.10
Image ID: quay.io/ocp-cert/sonobuoy@sha256:f7f745d9f4025df8889a3949492bf9af2287652a4d5820583566a41447f40b48
Normal Pulled 45s kubelet Container image "quay.io/ocp-cert/sonobuoy:v0.56.10" already present on machine
Goal:
- Testing different arch, arm64, than the default supported (amd64).
Description:
The --sonobuoy-image override flag is overridden when constructing the custom images for disconnected feature.
This flag should be mostly in development environment as OPCT automates and embeds supported and tested images in the binary.
When testing the override of Sonobuoy Worker and Aggregator to run in ARM64 clusters, the pods never going up due the replacement.
- links to