Bug 1823886 - collect oc get subscription as part of ocs must-gather
Summary: collect oc get subscription as part of ocs must-gather
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: must-gather
Version: 4.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 4.5.0
Assignee: Pulkit Kundra
QA Contact: Aviad Polak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-14 17:53 UTC by Neha Berry
Modified: 2020-09-15 10:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-15 10:16:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3754 0 None None None 2020-09-15 10:17:21 UTC

Description Neha Berry 2020-04-14 17:53:01 UTC
Description of problem (please be detailed as possible and provide log
snippests):
-------------------------------------------------------------------------
The current OCS must-gather logs do not contain the details of 

#
$ oc get subscription -n openshift-storage
NAME                                                                     PACKAGE                  SOURCE                CHANNEL
lib-bucket-provisioner-alpha-community-operators-openshift-marketplace   lib-bucket-provisioner   community-operators   alpha
ocs-operator                                                             ocs-operator             redhat-operators      stable-4.3

It would be good to collect the yaml outputs for the ocs-operator subscription atleast. 

This was needed for upgrade tests to confirm if the subscription is indeed changed.

Refer logs:  OCS 4.3.0 to 4.4 upgrade which wa sunsuccessful
 
http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jnk-vu1cv33-ua/jnk-vu1cv33-ua_20200414T140529/logs/failed_testcase_ocs_logs_1586876888/test_upgrade_ocs_logs/ocp_must_gather/quay-io-openshift-origin-must-gather-sha256-605d33681323ff3d4db3711ec45d223d6b0c882431d571a0c07208868996be55/namespaces/openshift-marketplace/



Version of all relevant components (if applicable):
----------------------------
OCS 4.3, OCS 4.4

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
-------------------------
No

Is there any workaround available to the best of your knowledge?
--------------------------
no

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
-----------------------
2

Can this issue reproducible?
-----------------------
yes


Can this issue reproduce from the UI?
---------------------
yes


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create an OCS 4.3 or 4.4 cluster
2. Collect OCS must-gather
    oc adm must-gather --image=quay.io/rhceph-dev/ocs-must-gather:latest-4.3
3. Search for the yaml file for kind: subscription in the must-gather folder


Actual results:
-----------------
oc get subscription -n openshift-storage -o yaml ocs-operator is not collected

Expected results:
----------------------

Collect oc get subscription -n openshift-storage -o yaml ocs-operator


Additional info:
--------------------

An upgraded CSV looks like this and this output is helpful in analysing upgrade failures

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  creationTimestamp: "2020-04-14T08:40:14Z"
  generation: 2
  name: ocs-operator
  namespace: openshift-storage
  resourceVersion: "73769"
  selfLink: /apis/operators.coreos.com/v1alpha1/namespaces/openshift-storage/subscriptions/ocs-operator
  uid: 7e6d5ab6-51d0-445b-8e1d-b71ba42bd3a7
spec:
  channel: stable-4.3
  installPlanApproval: Automatic
  name: ocs-operator
  source: redhat-operators
  sourceNamespace: openshift-marketplace
  startingCSV: ocs-operator.v4.2.3
status:
  catalogHealth:
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: certified-operators
      namespace: openshift-marketplace
      resourceVersion: "19500"
      uid: b9fb102a-6338-4746-b09c-09a3cb6f3a52
    healthy: true
    lastUpdated: "2020-04-14T08:40:14Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: community-operators
      namespace: openshift-marketplace
      resourceVersion: "19501"
      uid: 1d5b0cc6-7112-4814-a8c2-483f6aed2d72
    healthy: true
    lastUpdated: "2020-04-14T08:40:14Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: redhat-operators
      namespace: openshift-marketplace
      resourceVersion: "19502"
      uid: c28e214e-5151-49ce-b59c-95fedc3e3435
    healthy: true
    lastUpdated: "2020-04-14T08:40:14Z"
  conditions:
  - lastTransitionTime: "2020-04-14T08:40:14Z"
    message: all available catalogsources are healthy
    reason: AllCatalogSourcesHealthy
    status: "False"
    type: CatalogSourcesUnhealthy
  currentCSV: ocs-operator.v4.3.0
  installPlanRef:
    apiVersion: operators.coreos.com/v1alpha1
    kind: InstallPlan
    name: install-wlvm9
    namespace: openshift-storage
    resourceVersion: "73505"
    uid: e41f0f42-04ee-4a18-a40a-c8d709fa40c7
  installedCSV: ocs-operator.v4.3.0
  installplan:
    apiVersion: operators.coreos.com/v1alpha1
    kind: InstallPlan
    name: install-wlvm9
    uuid: e41f0f42-04ee-4a18-a40a-c8d709fa40c7
  lastUpdated: "2020-04-14T10:06:40Z"
  state: AtLatestKnown

Comment 3 Yaniv Kaul 2020-06-24 15:24:57 UTC
It's MODIFIED, without devel-ack ?

Comment 10 errata-xmlrpc 2020-09-15 10:16:49 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 (Red Hat OpenShift Container Storage 4.5.0 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/RHBA-2020:3754


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