Bug 2042657

Summary:	Scheduled pod has nodeName changed
Product:	OpenShift Container Platform	Reporter:	Maysa Macedo <mdemaced>
Component:	openshift-apiserver	Assignee:	Lukasz Szaszkiewicz <lszaszki>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Rahul Gangwar <rgangwar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	aos-bugs, mfojtik, nagrawal, pehunt
Target Milestone:	---
Target Release:	---
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-05-24 12:09:43 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-19 20:51:17 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.

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:
Pod has nodeName set only once.

Additional info:

Comment 1 Peter Hunt 2022-01-19 21:11:21 UTC

I'll take this for initial triage, it's as it's not related to pod resource API