Project

General

Profile

Actions

Feature #21743

closed

Update foreman-debug to collect logs

Added by Lukas Zapletal over 6 years ago. Updated over 5 years ago.

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

Description

/var/log/foreman-maintain/foreman-maintain.log

Actions #1

Updated by Anurag Patel over 6 years ago

  • Status changed from New to Assigned
  • Assignee set to Anurag Patel
Actions #2

Updated by Ivan Necas over 6 years ago

Although foreman-debug has an ability to be extended via `.d` directroy (such as we do here https://github.com/theforeman/foreman-packaging/blob/rpm/develop/rubygem-foreman-tasks/rubygem-foreman-tasks.spec#L110), probably the most appropriate here would be to extend the foreman-debug itself to be aware of this file. The reason is we don't know, if the foreman-debug is actually present, when installing the foreman-maintain.

Actions #3

Updated by Lukas Zapletal about 6 years ago

Bring it as a RPM dependency. I guess you require satellite to be present, do you? Problem solved.

Actions #4

Updated by Ivan Necas about 6 years ago

Even simpler would be just extending the foreman-debug to collect the file: the goal was potentally being able to use f-m on client machines as well: I would not insist too much for on that, but would be happier, if it worked that way

Actions #5

Updated by Lukas Zapletal about 6 years ago

  • translation missing: en.field_release set to 330
Actions #6

Updated by Ivan Necas about 6 years ago

  • Bugzilla link set to 1538640
Actions #7

Updated by Ivan Necas about 6 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
Actions #8

Updated by Anonymous over 5 years ago

  • Target version deleted (1.18.0)
Actions

Also available in: Atom PDF