Feature #3909
closed
compute resources prevent or disassciate host from VM prevent vm deletion
Added by Jelle B. over 10 years ago.
Updated about 6 years ago.
Description
As discussed on IRC.
Create a solution where by a host in foreman can be deledet without deletion of the actuall virtual host when using compute resources.
Chat log to clarify :
[14:14] <cyberkov> hmm. is it somehow possible to disable the deletion of a VM on the Compute Resource when deleting it from Foreman?
[14:15] <karim> cyberkov, maybe unmanaging it first
[14:15] <Dominic> cyberkov: only be manually disassociating the compute_resource_id and uuid in the hosts table in the DB, you can't through the UI
[14:17] <cyberkov> thanks :) Dominic: so unmanaging it (as karim meant) is not sufficient i guess?
[14:17] <Dominic> I don't think that works, I remember somebody saying reecntly it still deleted the VM..
- Category set to VM management
- Related to Bug #3795: "Associate VM's" Doesn't Re-associate when compute resource changes added
- Status changed from New to Ready For Testing
- Target version set to 1.9.2
- Assignee set to Anonymous
- Translation missing: en.field_release set to 4
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Feature #4155: API for CR association and disassociation added
- Related to deleted (Bug #3795: "Associate VM's" Doesn't Re-associate when compute resource changes)
- Has duplicate Bug #3795: "Associate VM's" Doesn't Re-associate when compute resource changes added
- Has duplicate Bug #4252: Correctly handle when VM is migrated between datacenters added
- Related to Feature #2049: Allow removal of host when not found in VCenter added
- Related to Feature #5464: Delete unamanged compute resource host without deleting the virtual machine. added
- Related to Bug #5707: disassociate is highlighted for physical host added
Also available in: Atom
PDF