Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-1172

Enhance machine status relating to IPAddressClaimed

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • openshift-4.15


      Please make sure to fill all story details here with enough information so
      that it can be properly sized and is immediately actionable. Our Definition
      of Ready for user stories is detailed in the link below:


      As much as possible, make sure this story represents a small chunk of work
      that could be delivered within a sprint. If not, consider the possibility
      of splitting it or turning it into an epic with smaller related stories.

      Before submitting it, please make sure to remove all comments like this one.


      {}USER STORY:{}

      As a cluster admin, the status field relating to the IPAddressClaimed is a bit confusing and should be improved to make it better to understand.



      Currently the machine object has the following status:


          - lastTransitionTime: "2023-09-04T17:50:34Z"
            message: All IP address claims are bound
            reason: WaitingForIPAddress
            status: "False"
            type: IPAddressClaimed 

      The reason, status and message are a bit confusing when IP address claim is bound.  The above is an example of what it says when it is finished.




      The status should look something like the following when IP is claimed:


          - lastTransitionTime: "2023-09-06T13:52:51Z"
            message: All IP address claims are bound
            reason: IPAddressesClaimed
            status: "True"
            type: IPAddressClaimed 

      reason text may change to match other condition fields formatting.




      This most likely will involve updating a few different projects:

      • openshift/machine-api-operator
      • openshift/api

            rhn-support-ngirard Neil Girard
            rhn-support-ngirard Neil Girard
            0 Vote for this issue
            1 Start watching this issue