Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

1. - [x] Mandatory Add the required version to the Fix version/s field.

2. - [ ] Mandatory Choose the type of documentation change.

      - [ ] New topic in an existing section or new section
      - [x] Update to an existing topic

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] Add Required access level for the user to complete the task here:
       

       - [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
     
     
       - [ ] Add link to dev story here:

4. - [x] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

Add a new item under here https://github.com/stolostron/rhacm-docs/blob/2.10_stage/release_notes/known_issues_continuity.adoc#known-issues-continuity

Title :

open-cluster-management-backup namespace stuck in 'Terminating' state after disabling the component cluster-backup in MCH

Content:

If you have a hub where you run an ACM Restore operation, if you disable the component cluster-backup on the MultiClusterHub, the open-cluster-management-backup ns is stuck in 'Terminating' state. This is happening because the velero Restore resources are waiting on the restores.velero.io/external-resources-finalizer finalizers to complete. 

Workaround :

1.Before trying to disable the cluster-backup option on the MultiClusterHub resource delete all ACM Restore resources and wait for the velero Restores to be cleaned up.

2. If you are already in the state where open-cluster-management-backup namespace is stuck in 'Terminating', edit all velero Restore resources and remove the  finalizers. This will delete the resources and allow the namespace to be deleted.