Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1726449

Summary: DNS operator does not have a level gate
Product: OpenShift Container Platform Reporter: Justin Pierce <jupierce>
Component: NetworkingAssignee: Dan Mace <dmace>
Networking sub component: DNS QA Contact: Hongan Li <hongli>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: urgent CC: aos-bugs, mifiedle
Version: 4.1.z   
Target Milestone: ---   
Target Release: 4.2.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: 2019-10-16 06:32:48 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 Justin Pierce 2019-07-02 21:20:18 UTC
Description of problem:
The dns clusteroperator does not set a level gate which allows the CVO to incorrectly believe it has been upgraded even if it fails. 

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

Steps to Reproduce:
1. oc adm release extract --to=/tmp/folder quay.io/openshift-release-dev/ocp-release:4.1.4
2. edit 0000_70_dns-operator_03-cluster-operator.yaml and notice it does not have the level gate present in, for example, 0000_50_cluster-monitoring-operator_05-clusteroperator.yaml

status:
  versions:
  - name: operator
    version: "4.1.4"


Actual results:
Without this level gate, the CVO can pass by the operator during the upgrade even if the operator fails to upgrade. 

Additional info:
Urgency at request of ccoleman. release info should include:
status:
  versions:
  - name: operator
    version: "0.0.1-snapshot"

Comment 2 Hongan Li 2019-07-29 00:46:33 UTC
Verified with 4.2.0-0.nightly-2019-07-28-222114 the issue has been fixed.

# oc adm release extract --to=/tmp/2114 "registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-07-28-222114"

# cat 0000_70_dns-operator_03-cluster-operator.yaml 
# This resource is not created by CVO, it is only used as a communication
# mechanism to tell the CVO which ClusterOperator resource to wait for.
# DNS operator creates and updates this resource.
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  name: dns
status:
  versions:
    - name: operator
      version: "4.2.0-0.nightly-2019-07-28-222114"

Comment 3 errata-xmlrpc 2019-10-16 06:32:48 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-2019:2922