Bug 1217527
Summary: | [RFE] Provide a newer version of Puppet for Satellite 6 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Chris Roberts <chrobert> |
Component: | Configuration Management | Assignee: | Mike McCune <mmccune> |
Status: | CLOSED ERRATA | QA Contact: | Corey Welton <cwelton> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | Nightly | CC: | adahms, bbuckingham, bkearney, cwelton, dcaplan, ehelms, jswensso, mburgerh, mmccune, oshtaier, peter.vreman, riehecky, rjerrido, sauchter, xdmoon |
Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | puppet-3.8.6-2,puppet-server-3.8.6-2,facter-2.4.6-2 | Doc Type: | Enhancement |
Doc Text: |
Red Hat Satellite 6.2 upgrades to the 3.8 stream of puppet.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-27 08:51:03 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1315284 |
Comment 1
RHEL Program Management
2015-04-30 15:03:12 UTC
Sorry.. moving this back. When updating Puppet version, please also include the newer version of hiera. Facter 2.4 would be very welcome as well. Hi, please provide verification steps thanks and regards, Tazim rpm -qa | grep puppet result: puppet-3.8.6-2 rpm -qa | grep hiera result: hiera-1.3.1-2 Test on both RHEL6 & RHEL7 Thanks, Chris Sorry, wrong package. Wish I could edit comments in bugzilla. rpm -qa | grep puppet result: puppet-3.8.6-2 rpm -qa | grep facter result: facter-2.4.6-2 VERIFIED: # rpm -qa foreman foreman-1.11.0.11-1.el7sat.noarch Steps: # rpm -qa | grep puppet puppet-3.8.6-2.el7sat.noarch # rpm -qa | grep hiera hiera-1.3.1-2.el7sat.noarch 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:1500 |