Bug 1414914
Summary: | When defining hostgroup, content host should inherit Puppet Environment from it. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Waldirio M Pinheiro <wpinheir> |
Component: | Host Group | Assignee: | Kavita <kgaikwad> |
Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2.6 | CC: | ahuchcha, bbuckingham, inecas, jcallaha, kbidarka, kgaikwad, oshtaier, vgunasek |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:54:37 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Waldirio M Pinheiro
2017-01-19 17:33:46 UTC
Upstream bug assigned to kgaikwad Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18478 has been resolved. *** Bug 1421832 has been marked as a duplicate of this bug. *** 1) Added puppet environment "production" to hostgroup "rhel7grp" 2) Assign this hostgroup to host "rhel7host" 3) observe that the puppet environment is "production" 4) Now changed the puppet environment to "kbidarka" in the hostgroup 5) Edited host and clicked the inherit button next to puppet environment 6) submitted form 7) Now from the UI it shows the puppet environment as "kbidarka" VERIFIED with Sat630-snap14.0 As mentioned above, behaviour of inheriting puppet env from hostgroup will be available in 6.3. For sat 6.2, I think the only way is to explicitly update correct puppet env for host. If it is not working as expected, please feel free to add your observations. 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/RHSA-2018:0336
|