Bug 1829645 - cluster-etcd-operator: add relatedObjects for immediate creation by CVO
Summary: cluster-etcd-operator: add relatedObjects for immediate creation by CVO
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.4.z
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On: 1829644
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-30 01:11 UTC by Sam Batschelet
Modified: 2020-06-29 15:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1829644
Environment:
Last Closed: 2020-06-29 15:33:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 315 0 None closed Bug 1829645: add relatedobjects for immediate creation by CVO 2020-06-22 03:56:30 UTC
Github openshift machine-config-operator pull 1764 0 None closed Bug 1829645: reconcile relatedObjects and place them in the clusteroperator for CVO 2020-06-22 03:56:30 UTC
Red Hat Product Errata RHBA-2020:2713 0 None None None 2020-06-29 15:34:08 UTC

Description Sam Batschelet 2020-04-30 01:11:13 UTC 
+++ This bug was initially created as a clone of Bug #1829644 +++

Description of problem: Currently must-gather 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.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: must-gather relatedObjects fail to populate in the case where the operator fails to start.


Expected results: must-gather relatedObjects are populated even if the operator fails to run


Additional info:
Comment 6 errata-xmlrpc 2020-06-29 15:33:54 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:2713
Note You need to log in before you can comment on or make changes to this bug.