|Summary:||RFE: Staypuft should prevent users adding hosts through foreman UI|
|Product:||Red Hat OpenStack||Reporter:||Mike Burns <mburns>|
|Component:||rubygem-staypuft||Assignee:||Brad P. Crochet <brad>|
|Status:||CLOSED ERRATA||QA Contact:||Alexander Chuzhoy <sasha>|
|Version:||Foreman (RHEL 6)||CC:||adahms, ajeain, brad, jrist, mburns, mlopes, yeylon|
|Fixed In Version:||ruby193-rubygem-staypuft-0.4.2-1.el6ost||Doc Type:||Enhancement|
Previously, it was possible to directly assign hosts to the deployment host groups created by the installer. This would cause problems when attempting to provision a Red Hat Enterprise Linux OpenStack Platform environment using hosts manually assigned to these host groups. With this update, deployment host groups are no longer visible in the user interface for the installer or the corresponding API, making it impossible to directly assign hosts to these host groups.
|Last Closed:||2014-11-04 17:01:55 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Mike Burns 2014-08-08 19:23:00 UTC
Description of problem: Currently, a user can assign any host to any of the staypuft created host groups through the foreman UI. This causes problems when trying to orchestrate OpenStack deployments. The hosts show up as already provisioned.
Comment 2 Brad P. Crochet 2014-10-02 17:32:25 UTC
PR Submitted: https://github.com/theforeman/staypuft/pull/330
Comment 3 Brad P. Crochet 2014-10-02 17:33:14 UTC
The fix is to remove the hostgroups from the host edit form dropdown. It also will disallow setting it via the API.
Comment 4 Jason E. Rist 2014-10-09 21:06:40 UTC
Comment 7 Alexander Chuzhoy 2014-10-14 18:57:34 UTC
Verified: rhel-osp-installer-0.4.2-1.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch openstack-puppet-modules-2014.1-23.el6ost.noarch openstack-foreman-installer-2.0.29-1.el6ost.noarch Per comment #3 A new host can't be assigned to any hostgroup that was created by deployments.
Comment 10 errata-xmlrpc 2014-11-04 17:01:55 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2014-1800.html