Bug 1957856

Summary:	'resource name may not be empty' is shown in CI testing
Product:	OpenShift Container Platform	Reporter:	Tomofumi Hayashi <tohayash>
Component:	Networking	Assignee:	Douglas Smith <dosmith>
Networking sub component:	multus	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	aconstan, aos-bugs, dosmith, mfojtik, xxia
Version:	4.8
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 23:06:51 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:

Comment 1 Stefan Schimanski 2021-05-06 16:24:31 UTC

I don't see a proof that this is an apiserver fault. Actually in your linked search I see legitimate case of that error message

  Uninstall operator: delete customresourcedefinition ""

Many others are leader-election which suggests that leader election has a bug.

Comment 4 Douglas Smith 2021-05-12 16:23:25 UTC

*** Bug 1959927 has been marked as a duplicate of this bug. ***

Comment 7 Weibin Liang 2021-05-17 18:08:09 UTC

Tomofumi,

Check v4.8 in https://search.ci.openshift.org/?search=resource+name+may+not+be+empty&maxAge=48h&context=1&type=bug%2Bjunit&name=4.8&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

QE does not see the message about "status update failed for pod /: resource name may not be empty" in the past two days, but still see the tons of message about "resource name may not be empty". Should QE verify this bug?

Comment 8 Tomofumi Hayashi 2021-05-19 13:19:27 UTC

"resource name may not be empty" error message is pretty common because it is client-go message. This bz only mentioned error message that is:
 - Multus generates the this error message
 - "pod /" is contained (this means pod/podnamespace is empty, pretty weird)

Looking the error message in CI, we don't see any logs that met above condition, so I suppose we verify the bug.

Comment 11 errata-xmlrpc 2021-07-27 23:06:51 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 (Moderate: OpenShift Container Platform 4.8.2 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-2021:2438