Red Hat Bugzilla – Bug 1319283
Puppet Master/CA fields are not inherited for discovered hosts via auto-provisioning
Last modified: 2016-12-12 12:11:14 EST
Created attachment 1137828 [details] hostgroup Description of problem: puppet is not installed in discovered hosts although the hostgroup has puppet settings configured Version-Release number of selected component (if applicable): Satellite 6.2.0-beta-snap4 How reproducible: Always Steps to Reproduce: 1.Setup a hostgroup and configure all required settings including PuppetCA, Puppet Master 2. Automatically discover/provision a host Actual results: Host is discovered and provisioned successfully. But puppet is not installed in the host so it is not reporting to satellite. Expected results: Puppet should be automatically installed (when setup in hostgroup) and the host should start reporting automatically. Additional info:
Created attachment 1137829 [details] provisioned host
It's because Puppet Master flag is not inherited from hostgroup, therefore it's not installed (when it's blank).
Are you doing auto-provisioning or provisioning via the interactive form?
I tried two auto provisioning scenarios, both failed for this bug: 1. Auto provision is disabled in satellite settings. Trigger provisioning from virt-manager. I went to Satellite -> Discovered Hosts and manually triggered auto provision. After provision, host did not have puppet configured. 2. Auto provision is enabled and discovery rules are setup in satellite. Trigger provisioning from virt-manager. The discovery rules worked and provision triggered fine. Again after provision, host did not have puppet configured.
I am seeing this now with RHCI on Satellite 6.2 as well.
Commented on the upstream PR's. I am not having any luck with them. They're breaking viewing Hostgroups and I'm still not inheriting values on converting hosts.
Proposing for 6.2.z, this makes discovery nearly useless for anyone using puppet, also some RHCI concern
Moving to POST since upstream bug http://projects.theforeman.org/issues/9784 has been closed
Created attachment 1169928 [details] Two required patches
Created attachment 1169929 [details] Two required patches
Ignore comments 16, 17 and 18. The attached patch is only for UI provisioning. This bug is all about auto-provisioning. I am editing the subject to avoid confusion, we may backport the UI patch at some point too, but we need to fix auto-provisioning first.
Blocked with https://bugzilla.redhat.com/show_bug.cgi?id=1364544
Failed. I tried the exact same steps as mentioned in the bug description. The Puppet Master/CA fields are still not inherited which causes puppet not to be installed. Verified in satellite-6.2.0-21.2.el7sat.noarch
*** Bug 1379108 has been marked as a duplicate of this bug. ***
HOTFIX for this bug is in different BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1367136
Verified with Sat6.2.5 snap1 To test the issue: 1 created a hostgroup with Puppet Master/CA fields associated to hostgroup 2 later defined a discovery rule and associated the hg created in above step2 3. Enabled auto-provisioning 4. discovered a host and auto-provosioning started. Once host is provisioned, I see that both fields are correctly associated to provisioned host (checked from edit host page). Please see the attachment. Also, I can see puppet correctly installed when I reviewed the provisioning template. Please see the attachment.
Created attachment 1227285 [details] puppet Master/CA fileds are inherited for discovered host via auto-prov
Created attachment 1227287 [details] on reviewing provisioning template of provisioned discovered host, it correctly renders the puppet
Please note that when we manually associate a hostgroup with discovered host for provisioning then puppet CA/master fields doesn't auto-populate. for this bz is already there: https://bugzilla.redhat.com/show_bug.cgi?id=1370022#c7
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://access.redhat.com/errata/RHBA-2016:2940