Description of problem: When nnce status is Progressing, nncp status is unknown Version-Release number of selected component (if applicable): CNV 4.10.0 (v4.10.0-46) How reproducible: Steps to Reproduce: 1. Configure nncp that should fail to configure Actual results: When nnce status is Progressing, nncp status is unknown Expected results: When nnce status is Progressing, nncp status should reflect nnce status (i.e Progressing) Additional info: ==================== nncp yaml ============================== apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: stam spec: desiredState: interfaces: - bridge: options: stp: enabled: false port: - name: eno1 (primary interface) ipv4: auto-dns: true dhcp: false enabled: false ipv6: auto-dns: true autoconf: false dhcp: false enabled: false name: brmaxunavail state: up type: linux-bridge ==================== nncp ============================== $ oc get nncp NAME STATUS stam $ oc get nncp -oyaml apiVersion: v1 items: - apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: annotations: nmstate.io/webhook-mutating-timestamp: "1644502557867894040" creationTimestamp: "2022-02-10T14:14:21Z" generation: 2 name: stam resourceVersion: "1715808" uid: 0fb5f7c6-140f-4337-8e70-73af48e2eae6 spec: desiredState: interfaces: - bridge: options: stp: enabled: false port: - name: eno1 ipv4: auto-dns: true dhcp: false enabled: false ipv6: auto-dns: true autoconf: false dhcp: false enabled: false name: brmaxunavail state: up type: linux-bridge status: conditions: - lastHearbeatTime: "2022-02-10T14:15:57Z" lastTransitionTime: "2022-02-10T14:15:57Z" status: Unknown type: Available - lastHearbeatTime: "2022-02-10T14:15:57Z" lastTransitionTime: "2022-02-10T14:15:57Z" status: Unknown type: Degraded lastUnavailableNodeCountUpdate: "2022-02-10T14:15:57Z" unavailableNodeCount: 1 kind: List metadata: resourceVersion: "" selfLink: "" ==================== nnce ============================== $ oc get nnce NAME STATUS cnv-qe-infra-23.cnvqe2.lab.eng.rdu2.redhat.com.stam Progressing $ oc describe nnce Name: cnv-qe-infra-23.cnvqe2.lab.eng.rdu2.redhat.com.stam Namespace: Labels: app.kubernetes.io/component=network app.kubernetes.io/managed-by=cnao-operator app.kubernetes.io/part-of=hyperconverged-cluster app.kubernetes.io/version=4.10.0 nmstate.io/node=cnv-qe-infra-23.cnvqe2.lab.eng.rdu2.redhat.com nmstate.io/policy=stam Annotations: <none> API Version: nmstate.io/v1beta1 Kind: NodeNetworkConfigurationEnactment Metadata: Creation Timestamp: 2022-02-10T14:14:21Z Generation: 1 Managed Fields: API Version: nmstate.io/v1beta1 Fields Type: FieldsV1 fieldsV1: f:metadata: f:labels: .: f:app.kubernetes.io/component: f:app.kubernetes.io/managed-by: f:app.kubernetes.io/part-of: f:app.kubernetes.io/version: f:nmstate.io/node: f:nmstate.io/policy: f:ownerReferences: .: k:{"uid":"fd5ab5c0-e135-493f-a757-d1e67d0b08ba"}: Manager: manager Operation: Update Time: 2022-02-10T14:14:21Z API Version: nmstate.io/v1beta1 Fields Type: FieldsV1 fieldsV1: f:status: .: f:conditions: f:desiredState: .: f:interfaces: f:desiredStateMetaInfo: .: f:time: f:version: f:policyGeneration: Manager: manager Operation: Update Subresource: status Time: 2022-02-10T14:15:57Z Owner References: API Version: v1 Kind: Node Name: cnv-qe-infra-23.cnvqe2.lab.eng.rdu2.redhat.com UID: fd5ab5c0-e135-493f-a757-d1e67d0b08ba Resource Version: 1715809 UID: f1da4c85-913d-49b9-9a08-24d8653004cf Status: Conditions: Last Hearbeat Time: 2022-02-10T14:15:57Z Last Transition Time: 2022-02-10T14:15:57Z Message: Applying desired state Reason: ConfigurationProgressing Status: True Type: Progressing Last Hearbeat Time: 2022-02-10T14:15:57Z Last Transition Time: 2022-02-10T14:15:57Z Reason: ConfigurationProgressing Status: Unknown Type: Failing Last Hearbeat Time: 2022-02-10T14:15:57Z Last Transition Time: 2022-02-10T14:15:57Z Reason: ConfigurationProgressing Status: Unknown Type: Available Last Hearbeat Time: 2022-02-10T14:15:57Z Last Transition Time: 2022-02-10T14:15:57Z Reason: ConfigurationProgressing Status: False Type: Pending Last Hearbeat Time: 2022-02-10T14:15:57Z Last Transition Time: 2022-02-10T14:15:57Z Reason: ConfigurationProgressing Status: False Type: Aborted Desired State: Interfaces: Bridge: Options: Stp: Enabled: false Port: Name: eno1 Vlan: Mode: trunk Trunk - Tags: Id - Range: Max: 4094 Min: 2 ipv4: Auto - Dns: true Dhcp: false Enabled: false ipv6: Auto - Dns: true Autoconf: false Dhcp: false Enabled: false Name: brmaxunavail State: up Type: linux-bridge Desired State Meta Info: Time: 2022-02-10T14:15:57Z Version: 0 Policy Generation: 2 Events: <none>
knmstate is not a part of CNV 4.11. Moving to the right component. Note that needed code was merged U/S, we just need to get it to openshift/kubernetes-nmstate.
Verified on Apply nncp: apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: stam-stam spec: desiredState: interfaces: - bridge: options: stp: enabled: false port: - name: enp0s3 ipv4: auto-dns: true dhcp: false enabled: false ipv6: auto-dns: true autoconf: false dhcp: false enabled: false name: brmaxunavail Result: The nncp Progressing status is corresponding to nnce status [kni@provisionhost-0-0 ocp-edge-auto_ocp-edge-cluster-0]$ oc get nncp -w NAME STATUS REASON stam Available SuccessfullyConfigured stam-stam Progressing ConfigurationProgressing upgrade-br-marker Available SuccessfullyConfigured stam-stam Progressing ConfigurationProgressing stam-stam Progressing ConfigurationProgressing stam-stam Progressing ConfigurationProgressing stam-stam Progressing ConfigurationProgressing stam-stam Progressing ConfigurationProgressing stam-stam Available SuccessfullyConfigured [kni@provisionhost-0-0 ocp-edge-auto_ocp-edge-cluster-0]oc get nncp stam-stam -o yaml .... status: conditions: - lastHeartbeatTime: "2022-05-17T14:32:41Z" lastTransitionTime: "2022-05-17T14:32:41Z" message: 5/5 nodes successfully configured reason: SuccessfullyConfigured status: "True" type: Available - lastHeartbeatTime: "2022-05-17T14:32:41Z" lastTransitionTime: "2022-05-17T14:32:41Z" reason: SuccessfullyConfigured status: "False" type: Degraded - lastHeartbeatTime: "2022-05-17T14:32:41Z" lastTransitionTime: "2022-05-17T14:32:41Z" reason: ConfigurationProgressing status: "False" type: Progressing lastUnavailableNodeCountUpdate: "2022-05-17T14:32:41Z" The only question, @cstabler , I have some "Degraded" type in the middle. Is it OK and it is just syncing?
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