Bug 1768357

Summary: [BM]Installation return failed when default image-registry is Removed
Product: OpenShift Container Platform Reporter: XiuJuan Wang <xiuwang>
Component: Image RegistryAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0CC: adam.kaplan, aos-bugs, lbednar, ncredi, rmarasch
Target Milestone: ---   
Target Release: 4.3.0   
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: 2020-01-23 11:10:30 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 XiuJuan Wang 2019-11-04 08:00:11 UTC
Description of problem:
Report "image-registry has not yet successfully rolled out" during installation when set image-registry default to Removed in Baremetal platform.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-02-092336

How reproducible:
always

Steps to Reproduce:
1.Install latest 4.3 cluster in BM
2.
3.

Actual results:
Report "image-registry has not yet successfully rolled out" during installation when set image-registry default to Removed in Baremetal platform.

$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version             False       True          47m     Unable to apply 4.3.0-0.nightly-2019-11-02-092336: the cluster operator image-registry has not yet successfully rolled out

$ oc get co  image-registry  
NAME             VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
image-registry                                         True        False         False      20m

$oc describe co image-reigstry
=============snip=============
Status:
  Conditions:
    Last Transition Time:  2019-11-04T06:54:19Z
    Message:               All registry resources are removed
    Reason:                Removed
    Status:                False
    Type:                  Progressing
    Last Transition Time:  2019-11-04T06:18:50Z
    Message:               The registry is removed
    Reason:                Removed
    Status:                True
    Type:                  Available
    Last Transition Time:  2019-11-04T06:18:50Z
    Status:                False
    Type:                  Degraded
  Extension:               <nil>


Expected results:

Shouldn't report installation failed.

Additional info:

Comment 1 Adam Kaplan 2019-11-06 15:24:37 UTC
Underlying issue likely duplicates #1753778, but keeping this BZ open so that make sure we test on baremetal.

Comment 3 XiuJuan Wang 2019-11-07 03:03:22 UTC
Could install cluster succeed when default image-registry set to Removed.
image-registry has set version when status is removed.
$ oc describe co  image-registry

Status:
  Conditions:
    Last Transition Time:  2019-11-07T03:01:31Z
    Message:               All registry resources are removed
    Reason:                Removed
    Status:                False
    Type:                  Progressing
    Last Transition Time:  2019-11-07T02:03:35Z
    Message:               The registry is removed
    Reason:                Removed
    Status:                True
    Type:                  Available
    Last Transition Time:  2019-11-07T02:03:35Z
    Status:                False
    Type:                  Degraded
  Extension:               <nil>
  Related Objects:
    Group:     imageregistry.operator.openshift.io
    Name:      cluster
    Resource:  configs
    Group:     
    Name:      openshift-image-registry
    Resource:  namespaces
  Versions:
    Name:     operator
    Version:  4.3.0-0.nightly-2019-11-07-001158
Events:       <none>

Comment 5 errata-xmlrpc 2020-01-23 11:10:30 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:0062