When creating an NNCP -
1. the NNCP gets stuck in `Progressing` state
2. there's no NNCE for one of the nodes.
    

OCP 4.19.0-rc.2
kubernetes-nmstate-operator.4.19.0-202506020913
    

Not sure.
    

    1.
Create a simple NNCP, for example:
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: bridge-marker1
spec:
  desiredState:
    interfaces:
    - bridge:
        options:
          stp:
            enabled: false
        port: []
      ipv4:
        auto-dns: true
        dhcp: false
        enabled: false
      ipv6:
        auto-dns: true
        autoconf: false
        dhcp: false
        enabled: false
      name: bridgemarker1
      state: up
      type: linux-bridge
 
(a simple NNCP that creates a linux-bridge interface without any ports).
    2.
Follow the NNCP - it remains stuck in `Progressing` state.
$ oc get nncp
NAME                 STATUS        REASON
bridge-marker1      Progressing   ConfigurationProgressing

    3.
Obtain the NNCEs - one is missing:
$ oc get nnce -w
NAME                                                   STATUS        STATUS AGE   REASON
cnvqe-043.lab.eng.tlv2.redhat.com.bridge-marker1      Progressing   3s           ConfigurationProgressing
cnvqe-045.lab.eng.tlv2.redhat.com.bridge-marker1      Pending       1s           MaxUnavailableLimitReached
cnvqe-043.lab.eng.tlv2.redhat.com.bridge-marker1      Available     0s           SuccessfullyConfigured
cnvqe-045.lab.eng.tlv2.redhat.com.bridge-marker1                                 
cnvqe-045.lab.eng.tlv2.redhat.com.bridge-marker1      Progressing   0s           ConfigurationProgressing
cnvqe-045.lab.eng.tlv2.redhat.com.bridge-marker1      Available     0s           SuccessfullyConfigured

The cluster also has a a node cnvqe-044, but there's no NNCE for it.
    

NNCP remains in `Progressing` state and doesn't report completion.
NNCE missing for some cluster nodes.
    

NNCE created for each node where the policy should be applied, and NNCP getting to a final state (`Succeeded` if the configuration is successful). 
    

1.
According to nmstate people, this is the result of an already known [nmstate bug|https://issues.redhat.com/browse/RHEL-93154]

2.
From Openshift Virtualization networking perspective this is a blocker for the upcoming 4.19.0 release.