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

Add control plane node status to the "upgrade status" output

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • OTA 251

    Description

      Add node status as mentioned in the sample output to "oc adm upgrade status".

      With this output, users will be able to see the state of the nodes that are 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.

      Control Plane Node(s)
NAME                                ASSESSMENT        PHASE              VERSION   	 
ip-10-0-128-174.ec2.internal        Complete          Updated   	 4.12.16   
ip-10-0-142-240.ec2.internal        Progressing       Rebooting          -   		  
ip-10-0-137-108.ec2.internal        Outdated   	      Pending   	 4.12.1

      Definition of done:

      • Add code to get similar output as listed above. if a particular field/column needs more work, create separate Jira cards.

      Attachments

        Issue Links

          depends on

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OTA-1165 Add worker 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#1731: OTA-1036: `adm upgrade status`: Add control plane nodes status

          GitHub openshift/oc#1732: OTA-1036: `adm update status`: Refactor node status

          Activity

            People

              dhurta@redhat.com David Hurta
              lmohanty@redhat.com Lalatendu Mohanty
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: