Description of problem:

In 2.11, we found in some cases the restored clusters were not available, and we figured out that after the import controller on the new hub created the correct bootstrap kubeconfig secret to the managed cluster, but before rebootstrap, the old work-agent on the managed cluster reverted the bootstrap kubeconfig from there cache, which cause the agent can not connect to the hub. we fix this by restart the agent immediately https://github.com/stolostron/ocm/pull/90 if the bootstrap kubeconfig secret changes in 2.11, but we are seeking a better solution for 2.10, 2.12.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: