| Summary: | [api-freeze] bump openshift/api for Controller Manager Operator | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Corey Daley <cdaley> |
| Component: | Build | Assignee: | Corey Daley <cdaley> |
| Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | aos-bugs, eparis, jokerman, mmccomas, pweil, wzheng |
| Target Milestone: | --- | ||
| Target Release: | 4.1.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-06-04 10:47:31 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: | |
|
Description
Corey Daley
2019-04-12 00:14:13 UTC
github.com/openshift/api dependency bump is included in https://github.com/openshift/cluster-openshift-controller-manager-operator/pull/86 @Corey Daley What checkpoint test should we cover for Controller Manager Operator about the bump? I'm not sure that there is a way to test for that. The pull request for the api bump has merged. @Corey Daley Just confirm with you below 2 part: I remembered it had the FAILING type before, but now it haven't, is it intended?
$ oc get clusteroperator |grep openshift-controller-manager
FAILING PROGRESSING
openshift-controller-manager 4.1.0-0.nightly-2019-04-22-005054 True False 8m25s
And when Updated the OpenShiftControllerManagerOperatorConfigs to unmanaged, type Proccessing in clusteroperator is Unknown, not false, right?
$ oc get clusteroperator |grep openshift-controller-manager
FAILING PROGRESSING
openshift-controller-manager Unknown Unknown 10s
The operator api is moving towards having a "Degraded" type instead of "Failing", and this operator has already moved to using it. The unmanaged one is correct, it will be in an unknown state because we are not in charge of it anymore. Yes, I can see a "Degraded" type, and did a regression test, no issue until now, so verify it. thanks@Corey Daley 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:0758 |