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

(GA) Adding oc adm upgrade status command (Phase-3)


    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • (GA) Adding oc adm upgrade status command (Phase-3)
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-1356 - 'oc adm upgrade status' command
    • OCPSTRAT-1356'oc adm upgrade status' command
    • 90% To Do, 5% In Progress, 5% Done

      Epic Goal*

      Add a new command `oc adm upgrade status` command which is backed by an API.  Please find the mock output of the command output attached in this card.

      Why is this important? (mandatory)

      • From the UI we can see the progress of the update. Using OC CLI we can see some of the information using "oc get clusterversion" but the output is not readable and it is a lot of extra information to process. 
      • Customer as asking us to show more details in a human-readable format as well provide an API which they can use for automation.

      Scenarios (mandatory) 

      Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  


      Dependencies (internal and external) (mandatory)

      What items must be delivered by other teams/groups to enable delivery of this epic. 

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Provide some (testable) examples of how we will know if we have achieved the epic goal.  

      Drawbacks or Risk (optional)

      Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing - Tests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Other 

            afri@afri.cz Petr Muller
            lmohanty@redhat.com Lalatendu Mohanty
            Jian Li Jian Li
            0 Vote for this issue
            3 Start watching this issue