Actions
Bug #17747
closed
Make foreman-debug aware of Puppet4
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1390929
Description of problem:
Puppet4 files live in different locations than for Puppet3.
This tools needs changes to be able to handle them.
Expected result:
foreman-debug(-proxy) should grab puppet4 files too.
Updated by Stephen Benjamin about 8 years ago
- Subject changed from Make foreman-debug aware of Puppet4 to Make foreman-debug aware of Puppet4
- Assignee deleted (
Lukas Zapletal) - Priority changed from High to Normal
Updated by Eric Helms over 7 years ago
- Project changed from Foreman to Smart Proxy
- Category deleted (
foreman-debug) - Status changed from New to Assigned
- Assignee set to Eric Helms
Updated by The Foreman Bot over 7 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/535 added
Updated by Eric Helms over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 0e0050af9ee0a57fc8e5ebc4199188fe7aeb0e7a.
Updated by Eric Helms over 7 years ago
- Translation missing: en.field_release set to 276
Updated by Ewoud Kohl van Wijngaarden over 3 years ago
- Has duplicate Bug #17261: Foreman debug does not collect Puppet 4.0+ paths added
Actions