Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-24416

MachineConfigNode cannot be synced with node creation/deletion

XMLWordPrintable

    • +
    • No
    • MCO Sprint 246, MCO Sprint 247, MCO Sprint 248
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      When a new node is added to or removed from a cluster the MCN objects did not react. Now, the MCO removes and adds MCN objects when the associated node is removed from or added to the cluster. We wait for the node to be managed by the MCO before creating an MCN object for it. This means we wait for the node to complete provisioning.
      Show
      When a new node is added to or removed from a cluster the MCN objects did not react. Now, the MCO removes and adds MCN objects when the associated node is removed from or added to the cluster. We wait for the node to be managed by the MCO before creating an MCN object for it. This means we wait for the node to complete provisioning.
    • Bug Fix
    • In Progress

      unknown machine config node can be listed, the name is not in current cluster, in my cluster, there are 6 nodes, but I can see 10 machine config nodes

      // current node
$ oc get node
NAME                                        STATUS   ROLES                  AGE     VERSION
ip-10-0-12-209.us-east-2.compute.internal   Ready    worker                 3h48m   v1.28.3+59b90bd
ip-10-0-23-177.us-east-2.compute.internal   Ready    control-plane,master   3h54m   v1.28.3+59b90bd
ip-10-0-32-216.us-east-2.compute.internal   Ready    control-plane,master   3h54m   v1.28.3+59b90bd
ip-10-0-42-207.us-east-2.compute.internal   Ready    worker                 53m     v1.28.3+59b90bd
ip-10-0-71-71.us-east-2.compute.internal    Ready    worker                 3h46m   v1.28.3+59b90bd
ip-10-0-81-190.us-east-2.compute.internal   Ready    control-plane,master   3h54m   v1.28.3+59b90bd

// current mcn
$ oc get machineconfignode
NAME                                        UPDATED   UPDATEPREPARED   UPDATEEXECUTED   UPDATEPOSTACTIONCOMPLETE   UPDATECOMPLETE   RESUMED
ip-10-0-12-209.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-23-177.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-32-216.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-42-207.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-53-5.us-east-2.compute.internal     True      False            False            False                      False            False
ip-10-0-56-84.us-east-2.compute.internal    True      False            False            False                      False            False
ip-10-0-58-210.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-58-99.us-east-2.compute.internal    False     True             True             Unknown                    False            False
ip-10-0-71-71.us-east-2.compute.internal    True      False            False            False                      False            False
ip-10-0-81-190.us-east-2.compute.internal   True      False            False            False                      False            False

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

      4.15.0-0.nightly-2023-12-04-162702

      How reproducible:

      Consistently

      Steps to Reproduce:

      1. setup cluster with 4.15.0-0.nightly-2023-12-04-162702 on aws
2. enable featureSet: TechPreviewNoUpgrade
3. apply file based mc few times.
4. check node list
5. check machine config node list

      Actual results:

      there are some unknown machine config nodes found

      Expected results:

      machine config node number should be same as cluster node number

      Additional info:

      must-gather: https://drive.google.com/file/d/1-VTismwXXZ9sYMHi8hDL7vhwzjuMn92n/view?usp=drive_link

            cdoern@redhat.com Charles Doern
            rhn-support-rioliu Rio Liu
            Rio Liu Rio Liu
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: