Bug 1906335
| Summary: | The lastTransitionTime, message, reason field of operatorcondition should be optional | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
| Component: | OLM | Assignee: | Alexander Greene <agreene> |
| OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | krizza, vdinh |
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The lastTransitionTime was required when overriding an OperatorCondition.
Consequence: The feature was difficult to use as users were forced to provide a timestamp when overriding an OperatorCondition.
Fix: The lastTransitionTime field is no longer required when overriding an OperatorCondition.
Result: Users no longer need to provide a lastTransitionTime when overriding an OperatorCondition.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:41:51 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
Jian Zhang
2020-12-10 09:55:35 UTC
This will no longer be required once the changes introduced to the CRD in this PR [1] are pulled into OLM, which will happen as a part of the kube dependency bump [2]. Ref: [1] https://github.com/operator-framework/api/pull/91 [2] https://github.com/operator-framework/operator-lifecycle-manager/pull/1903 I am not marking the message or reason fields as optional because I believe they should be required. I have updated the example documentation in this PR: https://github.com/operator-framework/olm-docs/pull/90 The PR linked to this ticket has been merged fixing the issue. Cluster version is 4.7.0-0.nightly-2021-01-04-215816
[root@preserve-olm-env data]# oc -n openshift-operator-lifecycle-manager exec catalog-operator-5b4b6587c4-2qgfb -- olm --version
OLM version: 0.17.0
git commit: 69dc076d610b033d3964ed40c4ac27ece3424851
It works as expected. Verify it.
[root@preserve-olm-env data]# oc edit operatorcondition etcdoperator.v0.9.4
operatorcondition.operators.coreos.com/etcdoperator.v0.9.4 edited
...
overrides:
- message: This is a known issue with the operator where it always reports that it cannot be upgraded.
reason: upgradeIsSafe
status: "True"
type: Upgradeable
# operatorconditions.operators.coreos.com "etcdoperator.v0.9.4" was not valid:
# * spec.overrides.message: Required value
# * spec.overrides.reason: Required value
# * spec.overrides.status: Required value
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633 |