Bug #25799
open
Bare-metal host 'Deploy On' setting doesn't persist
Description
I have some bare-metal hosts in a hostgroup that has 'Deploy On' defaulted to a vmware compute resource.
Each time I edit the hosts, I have to set 'Deploy On' back to 'bare metal'. I need to do this before I can 'submit' any changes I've made, but afterwards, the host page still has a 'VM' tab and the 'Deploy On' change isn't persisted.
I found this in 1.18.3, but areyus in IRC has confirmed this also exists in 1.20
Updated by Alex Fisher about 6 years ago
- Subject changed from Host 'Deploy-on' setting doesn't persist to Bare-metal host 'Deploy On' setting doesn't persist
Updated by Sebastian Bublitz about 6 years ago
I can confirm this is still in 1.20.1.
It only applies to hosts created after "deploy on" was set in the hostgroup.
Hosts created before that do not seem to have this issue.
Also, hosts created with this issue show the VM tab on host detail page and model is set to the VMWare compute instance anyways. In the hosts table in the DB, compute_resource_id gets set to what is set in the hostgroup, too.
Updated by Tomer Brisker almost 6 years ago
- Related to Feature #5790: Default "Deploy on" value for host groups. added
Updated by Bernhard Suttner over 5 years ago
Looks like the issue occurs in Foremn 1.21 and 1.22.
Setting deploy on "bare metal" for a new host group can not be selected => means, a host group for bare metal hosts can not be configured right now.
Updated by Bernhard Suttner over 5 years ago
- Found in Releases 1.21.0, 1.21.1, 1.21.2, 1.21.3, 1.22.0 added
Updated by Matt Darcy over 4 years ago
- Found in Releases 1.24.2 added
- Found in Releases deleted (
1.18.3, 1.20.2, 1.21.0, 1.21.1, 1.21.2, 1.21.3, 1.22.0)
also present in 1.24.2. in this instance with a librit compute host but the problem is the same core problem detailed.
Unable to progress a work around beyond destroy host and re-add host details.