Trying to upgrade from version 1.15, we are using a fresh install of 1.19 using latest puppet module, and find that when we Create Host, and choose a Host Group, the Deploy On option is greyed out defaulting to Baremetal
In 1.15 we were able to select any Compute Resource we wanted for that given location
Foreman and Proxy versions:
v1.19 for both
Foreman and Proxy plugin versions:
MaaS Discovery Plugin engine for Foreman
alongoldboim, Alon Goldboim, amirfefer, Amit Karsale, Amos Benari, Avi Sharvit, Bryan Kearney, bshuster, Daniel Lobato, Daniel Lobato Garcia, Daniel Lobato García, Danny Smit, David Davis, Dominic Cleal, Eric D. Helms, Ewoud Kohl van Wijngaarden, Frank Wall, Greg Sutcliffe, ChairmanTubeAmp, Ido Kanner, imriz, Imri Zvik, Joseph Mitchell Magen, June Zhang, kgaikwad, Lars Berntzon, ldjebran, Lukas Zapletal, Lukáš Zapletal, Marek Hulan, Marek Hulán, Martin Bačovský, Matt Jarvis, Michael Moll, Nick, odovzhenko, Ohad Levy, Ondrej Prazak, Ori Rabin, orrabin, Partha Aji, Petr Chalupa, Phirince Philip, Rahul Bajaj, Robert Antoni Buj Gelonch, Scubafloyd, Sean O’Keeffe, Sebastian Gräßl, Shimon Shtein, Shlomi Zadok, Stephen Benjamin, Swapnil Abnave, Thomas Gelf, Timo Goebel, Tomas Strych, Tom Caspy, Tomer Brisker, and Yann Cézard
Plugin engine for Foreman that enables running custom hook scripts on Foreman events
Foreman-plugin to manage snapshots in a vSphere environment.
Engine to synchronise provisioning templates from GitHub
This plug-in copies the host comment to VMWare annotations in The Foreman.
Other relevant data:
Nothing exceptional in the logs showing a problem or error, normal rendering it seems
No, I am not, it becomes greyed out / unselectable, and I can’t X out the
I’ve checked everything from locations, to operating systems, template
associations, subnets, you name it - they all check out, I’ve installed
three different instances just to see if the behavior repeats, and it does
indeed all three times no matter how I slice up the hostgroups and compute
One thing I did notice, is there is a new column in the database for
hostgroups called compute_resource_id, which by default is Null, this
doesn’t exist in 1.15 I’m wondering if there’s some tie-in somewhere I’m
No it works fine if I select a compute resource inside the hostgroup itself.
However, this really messes things up for us, as we need to be able to select different compute resources during deployment like we did before, especially with Foreman hammer-cli - you were able to pick a hostgroup and a target compute resource to deploy to. Now that section is just plain greyed out, whether we select a compute resource inside the hostgroup or not.
So I don’t think this is Foreman itself, I tried rewinding many packages back to 1.17.1 and it still has the same behavior. I’m suspecting a rubygem or something was updated in the past couple of months and broke things.
This doesn’t sounds like a packaging or (system) config issue but rather in taxonomies. You mentioned location so can you verify all resources for the host allow the location? Is the compute resources also set to the correct location?
Thanks for the help, I think we found a workaround/fix!
First, just to go over the things I checked in the UI:
set up of location (taxonomies)
compute resources have proper location set
compute profile is set up and associated properly with compute resources (nothing to associate by location really)
hostgroup root is set with proper location
hostgroup child is set with proper root and proper location
hostgroup root “deploy on” is default (blank)
hostgroup child “deploy on” is default (inherit - baremetal)
domain location is set
subnet location is set
architectures has no location tab
installation media has all locations set by default, unable to edit this
has no location tab
partition table set
installation media set
provisioning template set, and has proper location association
So, like this, for whatever reason the Create Host “Deploy on” is always Baremetal, and something else: I click “Inherit” for “Deploy on” in 1.19 and 1.18 (not there in 1.17) and it can actually be pulled down, but the only choice is “Bare metal”.
The workaround we discovered, if it’s a workaround, is:
Click locations on top -> manage locations
There’s a button in the top right for “Report Mismatches”, clicking this actually reports problems despite the UI showing locations set properly everywhere
There’s another button on the report to “Fix Mismatches” - this solves the problem right away in 1.17.4, all compute resources are available in “Deploy to” under Create Host.
For 1.19 and 1.18 we have to click the “Inherit” button first on “Deploy to” for Create Host, before we can actually see and select the Compute Resources.
While this fixes our problem, I’m a little concerned if we add more stuff we have to click this fix mismatched locations every time…