Project

General

Profile

Actions

Bug #17747

closed

Make foreman-debug aware of Puppet4

Added by Stephen Benjamin almost 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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 1 (0 open1 closed)

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

Updated by Stephen Benjamin almost 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
Actions #2

Updated by Eric Helms about 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
Actions #3

Updated by The Foreman Bot about 7 years ago

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

Updated by Eric Helms about 7 years ago

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

Updated by Eric Helms about 7 years ago

  • Translation missing: en.field_release set to 276
Actions #6

Updated by Ewoud Kohl van Wijngaarden about 3 years ago

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

Also available in: Atom PDF