Bug 2097162

Summary: Inspect namespace showing egress egressfirewalls not found
Product: OpenShift Container Platform Reporter: Paige Rubendall <prubenda>
Component: ocAssignee: Filip Krepinsky <fkrepins>
oc sub component: oc QA Contact: zhou ying <yinzhou>
Status: CLOSED DUPLICATE Docs Contact:
Severity: low    
Priority: low CC: ffernand, fkrepins, maszulik, mfojtik
Version: 4.11   
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-06-20 11:47:22 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 Paige Rubendall 2022-06-15 02:33:38 UTC
Description of problem:
When doing an inspect of a namespace on an SDN cluster, I get an error from the server saying that it doesn't have a resource type "egressfirewalls"

This only effects sdn clusters not ovn

Version-Release number of selected component (if applicable):4.11.0-0.nightly-2022-06-11-054027


How reproducible: 100% 


Steps to Reproduce:
1. Install sdn type of cluster (saw on azure and alibaba)
2. Perform action 
`oc adm inspect namespace openshift-machine-api`
3. Error getting inspect

Actual results:
error: errors occurred while gathering data:
    the server doesn't have a resource type "egressfirewalls"

Expected results:
No errors occur in getting inspect of namespace and output is there

Additional info:
 % oc adm inspect namespace openshift-sdn  --kubeconfig ~/.kube/111846/config          
Gathering data for ns/openshift-sdn...
Wrote inspect data to inspect.local.3868338835030329377.
error: errors occurred while gathering data:
    the server doesn't have a resource type "egressfirewalls"

Could be related to https://bugzilla.redhat.com/show_bug.cgi?id=2072171

Comment 2 Nadia Pinaeva 2022-06-15 14:38:56 UTC
Hey Paige, I think this log is expected and kind of info level, it shouldn't affect logs collection process - do you see any log files missing?
We may need to change the log message though.

Comment 3 Paige Rubendall 2022-06-15 14:49:44 UTC
If it is an "info level" log, I definitely do not think it should say "error". From what I can see there is no data missing.

Comment 5 Maciej Szulik 2022-06-20 11:47:22 UTC

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