Project

General

Profile

Bug #17747

Make foreman-debug aware of Puppet4

Added by Stephen Benjamin over 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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.


Related issues

Has duplicate Smart Proxy - Bug #17261: Foreman debug does not collect Puppet 4.0+ pathsDuplicate

Associated revisions

Revision 0e0050af (diff)
Added by Eric Helms over 5 years ago

Fixes #17747: Add Puppet 4 paths to debug

History

#1 Updated by Stephen Benjamin over 6 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

#2 Updated by Eric Helms over 5 years ago

  • Project changed from Foreman to Smart Proxy
  • Category deleted (foreman-debug)
  • Status changed from New to Assigned
  • Assignee set to Eric Helms

#3 Updated by The Foreman Bot over 5 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/535 added

#4 Updated by Eric Helms over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Eric Helms over 5 years ago

  • Legacy Backlogs Release (now unused) set to 276

#6 Updated by Ewoud Kohl van Wijngaarden over 1 year ago

  • Has duplicate Bug #17261: Foreman debug does not collect Puppet 4.0+ paths added

Also available in: Atom PDF