Description of problem:

The nncp status is changing between  "ConfigurationProgressing" to "SuccessfullyConfigured" every few minutes without any change in the host labels or any change in the nncp configuration. The reconciliation is very frequent as below.

~~~
2021-12-14T14:48:42.275132493Z {"level":"info","ts":1639493322.275068,"logger":"enactmentconditions","msg":"Reset","enactment":"node-2.node-1"}

omg logs nmstate-handler-nkgwj| grep Reset|grep 2021-12-14T14|wc -l
113
~~~

If we took one event:

~~~
2021-12-07T18:11:28.818263447Z {"level":"info","ts":1638900688.8182015,"logger":"enactmentconditions","msg":"Reset","enactment":"node-2.node-2"}

2021-12-07T18:11:29.824451211Z {"level":"info","ts":1638900689.824379,"logger":"enactmentstatus","msg":"enactment updated at the node: true","enactment":"node-2.node-2"}

2021-12-07T18:11:29.833217028Z {"level":"info","ts":1638900689.8332036,"logger":"enactmentconditions","msg":"NotifyMatching","enactment":"node-2.node-2"}

2021-12-07T18:11:30.859917713Z {"level":"info","ts":1638900690.859867,"logger":"enactmentconditions","msg":"NotifyProgressing","enactment":"node-2.node-2"}
2021-12-07T18:11:42.771612096Z {"level":"info","ts":1638900702.771587,"logger":"enactmentconditions","msg":"NotifySuccess","enactment":"node-2.node-2"}

2021-12-07T18:11:43.839706501Z {"level":"info","ts":1638900703.839669,"logger":"policyconditions","msg":"enactments count: {failed: {true: 0, false: 3, unknown: 0}, progressing: {true: 0, false: 3, unknown: 0}, available: {true: 1, false
: 2, unknown: 0}, matching: {true: 1, false: 2, unknown: 0}, aborted: {true: 0, false: 3, unknown: 0}}","policy":"node-2"}
2021-12-07T18:11:43.839719857Z {"level":"info","ts":1638900703.8397038,"logger":"policyconditions","msg":"SetPolicySuccess"}
~~~

There were no manual changes in the nncp object or the host labels that can trigger the change.

Also, we watched the node manifests for changes (get nodes -o yaml -w) and the labels remain unchanged and the only change was heartbeat time in the status and annotation field.


Version-Release number of selected component (if applicable):

v4.8.3

How reproducible:

Observed in a customer environment. The issue is persistent even after a whole reboot of the nodes.

Steps to Reproduce:

Unknown

Actual results:

nncp changing its status between "ConfigurationProgressing" to "SuccessfullyConfigured" every few minutes

Expected results:

nncp should not go into reconciliation loop if there are no changes in the watched objects.

Additional info: