I'm seeing an issue after clusterctl move where my already-provisioned BareMetalHosts come up in the new…
I'm seeing an issue after clusterctl move where my already-provisioned BareMetalHosts come up in the new…: a task in MiMo-V2.6-RL-harbor-code: MiMo-V2.6-RL Code (Harbor) (Harbor dataset). Expected outcomes: - Pause/move preservation: when CAPM3 prepares a BareMetalHost for migration, the migrated…
Part of FineEnvs/MiMo-V2.6-RL-harbor-code.