Bug 2052840

Summary: IMAGE_BUILDER=docker make test-e2e-operator-ocp runs with podman instead of docker
Product: OpenShift Container Platform Reporter: Aleksandra Malykhin <amalykhi>
Component: NetworkingAssignee: Christoph Stäbler <cstabler>
Networking sub component: kubernetes-nmstate-operator QA Contact: Aleksandra Malykhin <amalykhi>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: aos-bugs
Version: 4.10   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 10:48:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aleksandra Malykhin 2022-02-10 06:55:56 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
kubernetes-nmstate 4.10.0-202201310820
Cluster version is 4.10.0-0.nightly-2022-02-02-000921


How reproducible:
100%

Steps to Reproduce:

Req:
install  go >= 1.17 
install  docker

You need to run the tests from the kubernetes-nmstate folder. As the test setup will build and push the operator image, you must be able to pull & push from your registry and the repository where the operator is pushed to must be readable from your cluster (-> easiest is to make the repository public)

You can use this command to create the repos 'IMAGE_BUILDER=<podman/docker> IMAGE_REPO=<your repo user> make push' and change it permissions manually if you have problems

Steps to reproduce:
git clone https://github.com/openshift/kubernetes-nmstate
cd kubernetes-nmstate/
docker login -u="..." -p="..." <your image repo>
KUBEVIRT_PROVIDER=external KUBECONFIG=<path to kubeconfig> DEV_IMAGE_REGISTRY=<your image repo> IMAGE_REPO=<your repo user> IMAGE_BUILDER=docker make test-e2e-operator-ocp


Actual results:
The error
+ podman manifest rm quay.io/amalykhi/kubernetes-nmstate-handler:latest
hack/build-push-container.podman.sh: line 18: podman: command not found
+ true
+ podman manifest create quay.io/amalykhi/kubernetes-nmstate-handler:latest
hack/build-push-container.podman.sh: line 19: podman: command not found
make[2]: *** [Makefile:148: push-handler] Error 127
make[2]: Leaving directory '/home/kni/kubernetes-nmstate'

Expected Result:
Ran 4 of 4 Specs in 174.214 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS
Comment 2 Aleksandra Malykhin 2022-02-10 09:59:05 UTC 
Verified
kubernetes-nmstate 4.10.0-202201310820
Cluster version is 4.10.0-0.nightly-2022-02-02-000921

The steps to reproduse see in the description.


[kni@provisionhost-0-0 kubernetes-nmstate]$ KUBEVIRT_PROVIDER=external KUBECONFIG=<path to kubeconfig> DEV_IMAGE_REGISTRY=<your image repo> IMAGE_REPO=<your repo user> IMAGE_BUILDER=docker make test-e2e-operator-ocp

Result

Ran 4 of 4 Specs in 156.036 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS
Comment 4 errata-xmlrpc 2022-08-10 10:48:34 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069