Bug 1883538 - must gather report "cannot file manila/aws ebs/ovirt csi related namespaces and objects" error
Summary: must gather report "cannot file manila/aws ebs/ovirt csi related namespaces a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.0
Assignee: Christian Huffman
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-29 14:04 UTC by Qin Ping
Modified: 2021-02-24 15:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:21:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-storage-operator pull 133 0 None open Bug 1883538: Only include the relevant drivers in relatedObjects 2021-02-01 15:10:27 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:21:38 UTC

Description Qin Ping 2020-09-29 14:04:52 UTC
Description of problem:
must gather report "cannot file manila/aws ebs/ovirt csi related namespaces and objects" error

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-09-27-075304

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
skipping gathering namespaces/openshift-manila-csi-driver due to error: namespaces "openshift-manila-csi-driver" not found, skipping gathering clustercsidrivers.operator.openshift.io/ebs.csi.aws.com due to error: clustercsidrivers.operator.openshift.io "ebs.csi.aws.com" not found, skipping gathering clustercsidrivers.operator.openshift.io/csi.ovirt.org due to error: clustercsidrivers.operator.openshift.io "csi.ovirt.org" not found, skipping gathering clustercsidrivers.operator.openshift.io/manila.csi.openstack.org due to error: clustercsidrivers.operator.openshift.io "manila.csi.openstack.org" not found, skipping gathering 

In some cloud providers, some or all of these namespaces and objects are not created.

Seems must gather gets these info from:
$ oc get co storage -ojson |jq .status.relatedObjects
[
  {
    "group": "",
    "name": "openshift-cluster-storage-operator",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-cluster-csi-drivers",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-manila-csi-driver",
    "resource": "namespaces"
  },
  {
    "group": "operator.openshift.io",
    "name": "cluster",
    "resource": "storages"
  },
  {
    "group": "operator.openshift.io",
    "name": "ebs.csi.aws.com",
    "resource": "clustercsidrivers"
  },
  {
    "group": "operator.openshift.io",
    "name": "csi.ovirt.org",
    "resource": "clustercsidrivers"
  },
  {
    "group": "operator.openshift.io",
    "name": "manila.csi.openstack.org",
    "resource": "clustercsidrivers"
  }
]


Expected results:
These errs didn't break the must gather, if there are no there err messages in must gather output would be better.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 1 Jan Safranek 2020-09-29 14:11:21 UTC
This is limitation of library-go, it does not allow CSO to set RelatedObjects dynamically, after checking the actual cloud. So CSO adds all possible related objects there.

Comment 5 Qin Ping 2021-02-02 09:16:33 UTC
Verified with: 4.7.0-0.nightly-2021-02-02-052812

Comment 8 errata-xmlrpc 2021-02-24 15:21:17 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.7.0 security, bug fix, and enhancement 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-2020:5633


Note You need to log in before you can comment on or make changes to this bug.