Description of problem:

After an IBR/IBBF reinstall is completed successfully, the managedcluster's status remains "unknown" from the hub cluster. 

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

ACM 2.14

How reproducible:

Always

Steps to Reproduce:

1. Hub running latest OCP 4.20, ACM 2.14, and MCE 2.9

2. Spoke running latest OCP 4.20. In this case installed using IBI. I have not tested with a spoke installed with Assisted Installer workflow.

3. Initiate IBBF/IBR

4. Server is replaced. Observe managedcluster status

Actual results:

$ oc get managedcluster helix82 -ojson |jq -r .status.conditions
[
 

{     "lastTransitionTime": "2025-09-01T03:12:01Z",     "message": "Import succeeded",     "reason": "ManagedClusterImported",     "status": "True",     "type": "ManagedClusterImportSucceeded"   }

,
 

{     "lastTransitionTime": "2025-09-01T03:01:36Z",     "message": "Accepted by hub cluster admin",     "reason": "HubClusterAdminAccepted",     "status": "True",     "type": "HubAcceptedManagedCluster"   }

,
 

{     "lastTransitionTime": "2025-09-01T05:26:36Z",     "message": "Registration agent stopped updating its lease.",     "reason": "ManagedClusterLeaseUpdateStopped",     "status": "Unknown",     "type": "ManagedClusterConditionAvailable"   }

,
 

{     "lastTransitionTime": "2025-09-01T03:11:58Z",     "message": "Managed cluster joined",     "reason": "ManagedClusterJoined",     "status": "True",     "type": "ManagedClusterJoined"   }

,
 

{     "lastTransitionTime": "2025-09-01T03:11:58Z",     "message": "The clock of the managed cluster is synced with the hub.",     "reason": "ManagedClusterClockSynced",     "status": "True",     "type": "ManagedClusterConditionClockSynced"   }

]

Expected results:

managedcluster is "available" after the server is replaced using IBBF/IBR

Additional info: