Bug #11599
Parsing environments/manifests in Puppet 4 fails
Pull request:
Fixed in Releases:
Found in Releases:
Description
When using the smart-proxy with Puppet 4, the proxy fails to scan both environments and manifests due to api/config option changes.
I don't have the exact error messages or tracebacks any more, however the fixes are available in https://github.com/theforeman/smart-proxy/pull/313.
Related issues
Associated revisions
refs #11599 - permit Puppet 4.x in Gemfile
History
#1
Updated by Dominic Cleal almost 7 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/313 added
- Pull request deleted (
)
#2
Updated by Dominic Cleal almost 7 years ago
- Related to Tracker #8447: Puppet 4 support added
#3
Updated by Dominic Cleal over 6 years ago
- Assignee set to Dmitri Dolguikh
- Legacy Backlogs Release (now unused) set to 63
#4
Updated by Dmitri Dolguikh over 6 years ago
Updated by - Status changed from Ready For Testing to Closed
merged in at 763d7ae.
#5
Updated by Dmitri Dolguikh over 6 years ago
- Pull request https://github.com/theforeman/smart-proxy/pull/317 added
- Pull request deleted (
https://github.com/theforeman/smart-proxy/pull/313)
#6
Updated by Dominic Cleal over 6 years ago
- % Done changed from 0 to 100
Note there's no need to close the ticket manually, Redmine will do it hourly.
#7
Updated by Dominic Cleal over 6 years ago
- Related to Feature #11992: Support loading Puppet from AIO packages added
Fixes #11599: introduced support for puppet 4.0 These changes are based on Damien Churchil's PR