When deploying a SNO + worker Node in two separate steps, the vg-manager pod on the newly added worker node remains in a Running 0/1 state and it does not create the expected LVMVolumeGroupNodeStatus resource for the worker node. This issue has been reproduced in both a customer environment and an internal lab.

lvms-operator.v4.18.0

1. Deploy the initial SNO Cluster
2. Attach extra disk to the master node
3. Install the LVMS Operator
4. Create the LVMCluster
5. Scale Up the cluster and add extra disk to the worker node
6. Verify the Pod Status

$ oc get pod -n openshift-storage
NAME                             READY   STATUS    RESTARTS      AGE
lvms-operator-85598566c6-tz9qw   1/1     Running   0             27m
vg-manager-m25l6                 1/1     Running   1 (25m ago)   25m
vg-manager-vsbvs                 0/1     Running   0             14m

# oc logs vg-manager-8jxbr -f
...
{"level":"error","ts":"2025-03-04T17:27:00Z","msg":"Reconciler error","controller":"lvmvolumegroup","controllerGroup":"lvm.topolvm.io","controllerKind":"LVMVolumeGroup","LVMVolumeGroup":{"name":"vg1","namespace":"openshift-storage"},"namespace":"openshift-storage","name":"vg1","reconcileID":"aa2f3e23-4adc-46c7-87cc-bdb671fa9a42","error":"could not get LVMVolumeGroupNodeStatus: LVMVolumeGroupNodeStatus.lvm.topolvm.io \"mno-worker-0.5g-deployment.lab\" not found","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:316\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:263\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:224"}
...

Actual results:
- vg-manager pod on the new worker node (vg-manager-xxxx) stays Running (0/1)
- the LVMVolumeGroupNodeStatus for the new worker node is not created

vg-manager pod on the new worker node (vg-manager-xxxx) stays Running (1/1)

- Restarting the lvms-operator-xxx pod forces it to reprocess and detect the new worker
- Create the LVMCluster with LVMCluster.spec.tolerations

Example:

spec:
  tolerations:
    - key: node.kubernetes.io/not-ready
      effect: NoExecute


- Create the LVMCluster to use a custom node label instead of "node-role.kubernetes.io/worker" and apply the label manually to nodes 

Example: 

nodeSelector:
  nodeSelectorTerms:
  - matchExpressions:
    - key: LVMOperator
      operator: In
      values:
      - "true"