Bug 1828830

Summary: Provide cluster's related object immediately during CVO creation for must-gather
Product: OpenShift Container Platform Reporter: Maciej Szulik <maszulik>
Component: kube-controller-managerAssignee: Maciej Szulik <maszulik>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1829319 (view as bug list) Environment:
Last Closed: 2020-07-13 17:32:20 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:
Bug Depends On:    
Bug Blocks: 1829319    

Description Maciej Szulik 2020-04-28 12:54:20 UTC 
Currently relatedobjects are only filled when an operator is running, with https://github.com/openshift/cluster-version-operator/pull/318 we should be able to report that information during operator creation.
Comment 4 zhou ying 2020-05-07 04:02:31 UTC 
Checked with payload: 4.5.0-0.nightly-2020-05-06-003431, the issue has fixed:

During installation, login bootstrap , check the operator:
After the master running immediately , we could see: 

oc get co kube-controller-manager kube-apiserver -o json --kubeconfig=/opt/openshift/auth/kubeconfig | jq '.items[].status.relatedObjects'
[
  {
    "group": "operator.openshift.io",
    "name": "cluster",
    "resource": "kubecontrollermanagers"
  },
  {
    "group": "",
    "name": "openshift-config",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-config-managed",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-kube-controller-manager",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-kube-controller-manager-operator",
    "resource": "namespaces"
  }
]
[
  {
    "group": "operator.openshift.io",
    "name": "cluster",
    "resource": "kubeapiservers"
  },
  {
    "group": "apiextensions.k8s.io",
    "name": "",
    "resource": "customresourcedefinitions"
  },
  {
    "group": "security.openshift.io",
    "name": "",
    "resource": "securitycontextconstraints"
  },
  {
    "group": "",
    "name": "openshift-config",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-config-managed",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-kube-apiserver-operator",
    "resource": "namespaces"
  },
  {
    "group": "",
    "name": "openshift-kube-apiserver",
    "resource": "namespaces"
  }
]
Comment 5 errata-xmlrpc 2020-07-13 17:32:20 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, 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:2409