harvester: [BUG] Harvester Cluster does not connect back to rancher when harvester is restarted in nested environment
Describe the bug
If user restarts harvester once it is connected to rancher, harvester cluster (through virtualization management) is in cluster agent is not connected
To Reproduce Steps to reproduce the behavior:
- deploy rancher on a harvester VM, and import a harvester cluster through
virtualization management - deploy a harvester node driver cluster through rancher (let it get to an active state)
- shut down the harvester cluster
- Shut down the Rancher cluster
- start the harvester cluster again and wait for it to get to a ready state
- Start the Rancher cluster again
- Note: the node driver cluster will come back to a ready state but the Virtualization management won’t. The management cluster never comes back online.
- Note: if you reboot the Harvester cluster after this and make sure that the Rancher cluster is on while Harvester comes online then it will reconnect.
Expected behavior harvester management cluster should come back to an active state after a restart.
Environment:
- Harvester ISO version: v1.0.1-rc1
- rancher version: v2.6.4-rc9
- Underlying Infrastructure: dell poweredge r510
- SSDs
- single node Harvester cluster
supportbundle_ef00de77-99f1-4876-a619-0b061548de01_2022-03-18T17-41-51Z.zip
Additional context this workflow was working fine on v1.0.0 + rancher v2.6.3
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23 (14 by maintainers)
@slickwarren can u please help to revalidate it with Harvester v1.0.3 + Rancher v2.6.7(when it is released), please let us know if this is still an issue, thanks.
I don’t think this is what was happening with my setup because I’d set a static IP for my VM running rancher, but its possible and I can try to reproduce once I get to harvester testing.
I was using ubuntu 20 but your image should be fine
@tlehman yes!