Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsthirugn@redhat.com
2016-03-18 17:22:53 UTC
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:
Comment 1sthirugn@redhat.com
2016-03-18 17:24:19 UTC
Are you doing auto-provisioning or provisioning via the interactive form?
Comment 5sthirugn@redhat.com
2016-03-21 14:36:20 UTC
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.
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.
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.
Comment 23sthirugn@redhat.com
2016-08-12 17:47:27 UTC
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
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.
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
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: