Uploaded image for project: 'OpenShift Over the Air'
  1. OpenShift Over the Air
  2. OTA-1165

Add worker node status to the "upgrade status" output

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • OTA 248, OTA 249, OTA 250

    Description

      Add node status as mentioned in the sample output to "oc adm upgrade status" in OpenShift Update Concepts

      With this output, users will be able to see the state of the nodes that are not part of the master machine config pool and what version of RHCOS they are currently on. I am not sure if it is possible to also show corresponding OCP version. If possible we should display that as well.

      =Worker Upgrade=

Worker Pool: openshift-machine-api/machineconfigpool/worker
Assessment: Admin required
Completion: 25% (Est Time Remaining: N/A - Manual action required)
Mode: Manual | Assisted [- No Disruption][- Disruption Permitted][- Scaling Permitted]
Worker Status: 4 Total, 4 Available, 0 Progressing, 3 Outdated, 0 Draining, 0 Excluded, 0 Degraded

Worker Pool Node(s)
NAME					ASSESSMENT	PHASE		VERSION		EST		MESSAGE
ip-10-0-134-165.ec2.internal		Manual		N/A		4.12.1		?		Awaiting manual reboot
ip-10-0-135-128.ec2.internal		Complete	Updated		4.12.16		-
ip-10-0-138-184.ec2.internal		Manual		N/A		4.12.1		?		Awaiting manual reboot
ip-10-0-139-31.ec2.internal		Manual		N/A		4.12.1		?		Awaiting manual reboot

      Definition of done:

      • Add code to get similar output as listed above. if a particular field/column needs more work, create separate Jira cards.
      • This output should be shown even when control plane already updated but workers are not yet (as of Jan 2024, the status command will say that the cluster is not upgrading in such case)
      • Output should take into account that there can be multiple worker pools
      • We should capture fixtures for the following to scenarios:
      • cluster that finished control plane update but is still upgrading worker nodes
      • cluster that finished control plane update but is still upgrading worker nodes and there’s a restrictive PDB that prohibits draining

      Attachments

        Issue Links

          is depended on by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OTA-1036 Add control plane node status to the "upgrade status" output

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MCO-836 state reporting GA

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • New

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MCO-811 Create enhancement and discuss the implementation of MachineConfigNode

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/oc#1689: OTA-1165: `adm upgrade status`: Add Worker Node Status

          Activity

            People

              dhurta@redhat.com David Hurta
              afri@afri.cz Petr Muller
              Evgeni Vakhonin Evgeni Vakhonin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: