fails gracefully when hypervisor has gone away
|Velocity based estimate||-|
(Even just turning off a hypervisor seems to cause issues).
In this case, I've rebuilt the hypervisor. I'd like to destroy the old VMs from foreman. Clicking "host -> delete" ends with this stack track. Unmanaging the node doesn't seem to help.
undefined method `connect' for nil:NilClass
#2 Updated by Benjamin Papillon about 1 year ago
- Tracker changed from Bug to Feature
- Subject changed from fails when hypervisor has gone away to fails gracefully when hypervisor has gone away
Aside from using computer ressources instead of Hypervisor code, try to get a graceful error when hypervisor/computer ressource is not available