Project

General

Profile

Bug #6965

disassociated VMs still appear in host listing

Added by Joshua Hoblitt about 7 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
VM management
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

In 1.5.2 I am able to disassociate a VM but it still appears in the host listing and counts towards the dashboard summary of inactive hosts. If I edit the VM a second time and click the disassociate (again) I get an error message of "Host foo... is not associated with a VM". Is this is the desired behavior? My expection was that the dissociated VM would now long be represented as a host.

History

#1 Updated by Joshua Hoblitt about 7 years ago

After a second observation, it appears that this may only happen with VMs that were not provisioned via foreman (they have a hardware type of KVM), so it should not be possible to disassociate them. This may be a dup of #6965.

#2 Updated by Dominic Cleal about 7 years ago

The hosts are still meant to be listed, but Foreman will treat them like bare metal hosts rather than hosts with an associated VM. This means the power and console options disappear and if you now delete the host, the VM won't be deleted.

Regarding the disassociate button, it should really be hidden when they're already in this state rather than being visible and showing a warning when clicked.

Also available in: Atom PDF