Feature Overview

related to https://issues.redhat.com/browse/ACM-16851 opened by ODF

In a hub disaster recovery scenario, when the restore is executed on the new hub, the last step is to run an auto import operation on the managed clusters. The issue is that some of the managed clusters could be down at the time of the restore so the auto import tries for a number of times ( I think 5 times ) and then gives up completely.

This results in managed clusters not being auto imported. The only way to fix the issue is, after starting the managed cluster , to manually run a new import or rerun the last step of the restore operation to force another auto import call.

We request with this feature that the auto import component continues trying the auto import if the managed cluster was identified to be down. Possible approaches would be :

• set a very big value for the auto import retry in a restore situation; but this may not work all the time. If the managed cluster is started after the nb of trials is exhausted
• the auto import sees that the auto import secret comes from a restore operation ( tagged by a secret annotation ). In this case, the auto import keeps trying. An auto-import-secret created by the restore operation has this label: 
  cluster.open-cluster-management.io/restore-auto-import-secret: true

Goals

The auto import for the managed clusters always succeeds when running a hub disaster recovery, even when the managed clusters are not active at the time of the restore operation.

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• ...

Out of Scope

• ...

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?