Bug 2045065

Summary:	Scheduled pod has nodeName changed
Product:	OpenShift Container Platform	Reporter:	Maysa Macedo <mdemaced>
Component:	Networking	Assignee:	Maysa Macedo <mdemaced>
Networking sub component:	kuryr	QA Contact:	Itzik Brown <itbrown>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	itbrown, mdulko
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:43:39 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 Maysa Macedo 2022-01-25 14:37:54 UTC

Description of problem:

Kuryr SDN plugin started wiring a Pod (downloads-754f7b8c6b-b5bj7) that had a nodeName configured and while it was being processed the Pod was fetched again and no nodeName was present anymore[1]. Kuryr was not able to provide the connectivity to that Pod as it needs the nodeName info and installation did not progress.

Some additional information:
- the Pod UID remained the same.
- Kuryr did not use the resource version when fetching the Pod again.
- The Pod with nodeName[2] and without nodeName[3].

[1] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-kuryr/1479396174820544512/artifacts/e2e-openstack-kuryr/gather-must-gather/artifacts/must-gather/namespaces/openshift-kuryr/pods/kuryr-controller-75d67f7b9d-gt7d6/controller/controller/logs/current.log
[2] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-kuryr/1479396174820544512/artifacts/e2e-openstack-kuryr/gather-must-gather/artifacts/must-gather/namespaces/openshift-console/pods/downloads-754f7b8c6b-b5bj7/downloads-754f7b8c6b-b5bj7.yaml
[3] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-shiftstack-shiftstack-ci-main-periodic-4.10-e2e-openstack-kuryr/1479396174820544512/artifacts/e2e-openstack-kuryr/gather-must-gather/artifacts/must-gather/namespaces/openshift-console/core/pods.yaml


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Maysa Macedo 2022-01-25 14:39:14 UTC

The issue was reported in the apiserver https://bugzilla.redhat.com/show_bug.cgi?id=2042657

Comment 4 Itzik Brown 2022-02-24 14:34:19 UTC

Tempest plugin tests passed
OCP 4.11.0-0.nightly-2022-02-23-185405
OSP RHOS-16.2-RHEL-8-20211129.n.1

Comment 5 ShiftStack Bugwatcher 2022-03-05 07:07:34 UTC

Removing the Triaged keyword because:
* the QE automation assessment (flag qe_test_coverage) is missing

Comment 7 errata-xmlrpc 2022-08-10 10:43:39 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