Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1023

Make it more clear that events are from past updates

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • 8
    • False
    • None
    • False
    • OCPSTRAT-763 - [TechPreview]Disconnected Cluster Update and Boot without local image registry
    • 0
    • 0.000

      • specify the reason and message for past events once the update has been completed
      • clear these out when the next update begins. They should revert to "This phase has not begun yet"

       

      Description:
      To ensure clarity and proper protocol, refine the handling of update events and statuses. Currently, statuses from past updates are preserved, which can create confusion. The goal is to clearly distinguish between past and current updates by implementing the following rules:

      Acceptance Criteria:
      1. Reset Conditions on New Update:

      When a new update begins (i.e., when a new MachineConfig is applied), all previous statuses and conditions should be cleared.
      The conditions should reset to the default message: "This phase has not begun yet."

      2. Specify Completion Details:

      Upon completion of an update, specify the reason and message for past events clearly.
      These details should indicate that they are from the last update cycle.
      Example: "Update completed successfully. Reason: Disk write completed. Message: System is stable and ready."

      3. Distinguish Past Events:

      Any preserved information from the previous update should be clearly marked as such.
      Example: "Previous update completed. Reason: Maintenance completed. Message: System ready. (From last update cycle)"

      4. Clear on New Update Initiation:

      Ensure that the statuses and conditions are cleared as soon as a new update process starts, not when it finishes.
      This prevents any confusion and provides a clear view of the current update process.

      5. Adherence to Protocol:

      Ensure the implementation follows the protocol where conditions reflect the current state accurately without historical muddling.
      Past statuses should only be preserved if explicitly required and should be clearly marked to avoid confusion.

      Context:
      This refinement is based on the observation that preserving past update statuses can lead to a muddled view of the system's current state.
      The change ensures that the status accurately reflects the current phase of the update process, providing clarity for all users.

            Unassigned Unassigned
            cdoern@redhat.com Charles Doern
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: