Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-22602

As a cluster admin, I can see rollback conditions for each migration stage in case of failure

XMLWordPrintable

    • GH Train-31
    • Important
    • None

      Value Statement

      Implement rollback conditions and manual steps for each migration stage.

      Definition of Done for Engineering Story Owner (Checklist)

      Define and implement rollback conditions for each migration stage to ensure clusters are restored to a consistent state after failures:

      • Initializing: Remove migrating annotation and rbac resources.
      • Deploying: delete addonConfig and cluster from target hub. And the above initializing rollback
      • Registering: Remove migrating annotation, delete clusters/addonConfig from target hub, set hubAccepted = true, delete KlusterletConfig/secret from source hub.

      Normal flow

      **
      Pending → Validating → Initializing → Deploying → Registering → Cleaning → Completed
       

      Failure Handling Flow

      • Validating (failure) → Failed
      • Unknown macro: {

        {Initializing/Deploying/Registering (failure) → Rollbacking → Failed }

        }

      • Rollbacking (success/failure) → Failed
        • Initializing
          • Remove the migrating annoation from the managed cluster
          • Remove the klusterletconfig from source hub
          • Remove the rbac setting from the target hub
        • Deploying
      •  

      Development Complete

      • The code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [x] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      • [ ] Create an informative documentation issue using the Customer

      Portal Doc template that you can access from [The Playbook](

      https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

      and ensure doc acceptance criteria is met.

      • Call out this sentence as it's own action:
      • [ ] Link the development issue to the doc issue.

      Support Readiness

      • [ ] The must-gather script has been updated.

              rh-ee-myan Meng Yan
              clyang82 Chunlin Yang
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: