Bug 2053118
| Summary: | nncp Available condition reason should be exposed in `oc get` | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ruth Netser <rnetser> |
| Component: | Networking | Assignee: | Christoph Stäbler <cstabler> |
| Networking sub component: | kubernetes-nmstate | QA Contact: | Aleksandra Malykhin <amalykhi> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | low | CC: | aos-bugs, cnv-qe-bugs, cstabler, phoracek, rhrazdil |
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.11.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: | 2022-08-10 10:49:18 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: | |||
Hello Ruth, We have added a Progressing condition [0], so now when a policy is in progress, you should get $ oc get nncp NAME STATUS stam Progressing Do you find this good enough or do you want to add the Rason column? [0] https://github.com/nmstate/kubernetes-nmstate/pull/982 @rhrazdil thanks for the fix; if this is not a big issue, adding the Reason column would be very useful as well. PR adding Reason column to NNCP `oc/kubectl get nncp` list: https://github.com/nmstate/kubernetes-nmstate/pull/1023 Waiting for the U/S PR to get to OpenShift's D/S This fix was merged U/S. Verified on kubernetes-nmstate-operator.4.11.0-202205171127 The reason column is displayed correctly and showing corresponding values. [kni@provisionhost-0-0 ocp-edge-auto_ocp-edge-cluster-0]$ oc get nncp -w NAME STATUS REASON upgrade-br-marker Progressing ConfigurationProgressing upgrade-br-marker Progressing ConfigurationProgressing upgrade-br-marker Available SuccessfullyConfigured 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069 |
Description of problem: nncp Available condition reason should be exposed in `oc get` When the status is Unknown, there's no visible status of the resource. For easier debugging it will be useful to add a column with the current reason for "'status': 'Unknown', 'type': 'Available'" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: When the conditions are: {'lastHearbeatTime': '2022-02-10T14:08:39Z', 'lastTransitionTime': '2022-02-10T14:08:39Z', 'message': 'Policy is progressing 0/1 nodes finished', 'reason': 'ConfigurationProgressing', 'status': 'Unknown', 'type': 'Available'} This is what is displayed: $ oc get nncp NAME STATUS stam When the conditions are: {'lastHearbeatTime': '2022-02-10T14:11:44Z', 'lastTransitionTime': '2022-02-10T14:11:44Z', 'message': '1/1 nodes successfully configured', 'reason': 'SuccessfullyConfigured', 'status': 'True', 'type': 'Available'} Status is Available