Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1825949

Summary:	You have to remove that container to be able to reuse that name.: that name is already in use
Product:	OpenShift Container Platform	Reporter:	Dan Williams <dcbw>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Status:	CLOSED DUPLICATE	QA Contact:	Sunil Choudhary <schoudha>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, jokerman, mfojtik
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:	2020-04-20 22:09:50 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 Dan Williams 2020-04-20 14:52:20 UTC

level=error msg="Cluster operator kube-controller-manager Degraded is True with InstallerPodContainerWaiting_CreateContainerError::NodeInstaller_InstallerPodFailed: NodeInstallerDegraded: 1 nodes are failing on revision 3:\nNodeInstallerDegraded: static pod of revision 3 has been installed, but is not ready while new revision 4 is pending; 1 nodes are failing on revision 4:\nNodeInstallerDegraded: \nInstallerPodContainerWaitingDegraded: Pod \"installer-5-ci-op-ltcxb-m-2.c.openshift-gce-devel-ci.internal\" on node \"ci-op-ltcxb-m-2.c.openshift-gce-devel-ci.internal\" container \"installer\" is waiting for 36m6.357583743s because \"the container name \\\"k8s_installer_installer-5-ci-op-ltcxb-m-2.c.openshift-gce-devel-ci.internal_openshift-kube-controller-manager_c6b1de04-5995-453e-9877-b52a009bc695_0\\\" is already in use by \\\"312675bbf30ed5bf9cbdc50d55260ff6abc2ed44414b7e5b0bb99e7b0d6f8464\\\". You have to remove that container to be able to reuse that name.: that name is already in use\""
level=info msg="Cluster operator kube-controller-manager Progressing is True with NodeInstaller: NodeInstallerProgressing: 2 nodes are at revision 0; 1 nodes are at revision 4; 0 nodes have achieved new revision 7"

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1615/pull-ci-openshift-machine-config-operator-release-4.4-e2e-gcp-upgrade/183

Comment 1 Maciej Szulik 2020-04-20 16:16:42 UTC

The pod naming is coming from kubelet, moving to node team for verification.

Comment 2 Ryan Phillips 2020-04-20 22:09:50 UTC


*** This bug has been marked as a duplicate of bug 1823949 ***