Bug 2056607

Summary: Running kubernetes-nmstate handler e2e tests stuck on OVN clusters
Product: OpenShift Container Platform Reporter: Christoph Stäbler <cstabler>
Component: NetworkingAssignee: Christoph Stäbler <cstabler>
Networking sub component: kubernetes-nmstate-operator QA Contact: Aleksandra Malykhin <amalykhi>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium    
Version: 4.10   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 10:50:27 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 Christoph Stäbler 2022-02-21 15:12:01 UTC 
Description of problem:

Running the e2e tests of kubernetes-nmstate, get stuck after applying the required machine configs: https://github.com/openshift/kubernetes-nmstate/blob/04bc29df70fc211be50573263740104e7e286e80/hack/ocp-e2e-tests-handler.sh#L49

Can be seen e.g in some CI jobs: 
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/25547/rehearse-25547-pull-ci-openshift-kubernetes-nmstate-master-e2e-ovn-ipv4/1489516359099355136

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_release/25547/rehearse-25547-pull-ci-openshift-kubernetes-nmstate-master-e2e-ovn-ipv4/1489516359099355136/artifacts/e2e-ovn-ipv4/kubernetes-nmstate-e2e/build-log.txt


How reproducible:
Always


Steps to Reproduce:
1. Setup a OVN cluster via dev-scripts
2. Start the k-nmstate e2e tests: make test-e2e-handler-ocp (inside the k-nmstate directory)
3. Tests stuck at setup on applying the machine configs


Actual results:
Tests stuck at setup on applying the machine configs


Expected results:
Tests start as expected
Comment 2 Aleksandra Malykhin 2022-03-02 11:44:44 UTC 
Cluster version is 4.11.0-0.nightly-2022-02-27-122819



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


 Result:
Ran 4 of 4 Specs in 150.509 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
Comment 5 errata-xmlrpc 2022-08-10 10:50:27 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