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

status message not populated as expected

XMLWordPrintable

    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          %s is not populated with authoritativeAPI , when cluster is enabled for migration

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

          4.18.0-0.nightly-2024-09-23-182657

      How reproducible:

          Always

      Steps to Reproduce:

      Set featuregate as below 
      spec:
  featureSet: CustomNoUpgrade
  customNoUpgrade:
    enabled:
    - MachineAPIMigration    

Update - oc edit --subresource status` to add the `.status.authoritativeAPI` field to see the behaviour of the pausing.

eg- oc edit --subresource status machineset.machine.openshift.io miyadav-2709a-5v7g7-worker-eastus2

       

      Actual results:

          status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2024-09-27T07:22:58Z"
    reason: AuthoritativeAPI is set to MachineAPI
    severity: The AuthoritativeAPI is set to %s
    status: "False"
    type: Paused
  fullyLabeledRepl

      Expected results:

          status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2024-09-27T07:22:58Z"
    reason: AuthoritativeAPI is set to MachineAPI
    severity: The AuthoritativeAPI is set to MachineAPI
    status: "False"
    type: Paused
  fullyLabeledRepl

      Additional info:

          related to - https://issues.redhat.com/browse/OCPCLOUD-2565

    message: 'The AuthoritativeAPI is set to '
    reason: AuthoritativeAPIMachineAPI
    severity: Info
    status: "False"
    type: Paused

       

            rh-ee-tbarberb Theo Barber-Bany
            rh-ee-miyadav Milind Yadav
            Milind Yadav Milind Yadav
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: