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

CPMS leaves only 2 masters during update


    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.14.z
    • 4.13, 4.12, 4.14, 4.15, 4.16
    • None
    • No
    • CLOUD Sprint 250
    • 1
    • Proposed
    • False
    • Hide



      This is a clone of issue OCPBUGS-29419. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-29249. The following is the description of the original issue:

      Observed during testing of candidate-4.15 image as of 2024-02-08.

      This is an incomplete report as I haven't verified the reproducer yet or attempted to get a must-gather. I have observed this multiple times now, so I am confident it's a thing. I can't be confident that the procedure described here reliably reproduces it, or that all the described steps are required.

      I have been using MCO to apply machine config to masters. This involves a rolling reboot of all masters.

      During a rolling reboot I applied an update to CPMS. I observed the following sequence of events:

      • master-1 was NotReady as it was rebooting
      • I modified CPMS
      • CPMS immediately started provisioning a new master-0
      • CPMS immediately started deleting master-1
      • CPMS started provisioning a new master-1

      At this point there were only 2 nodes in the cluster:

      • old master-0
      • old master-2

      and machines provisioning:

      • new master-0
      • new master-1

            joelspeed Joel Speed
            openshift-crt-jira-prow OpenShift Prow Bot
            Huali Liu Huali Liu
            0 Vote for this issue
            6 Start watching this issue