Project

General

Profile

Feature #21743

Update foreman-debug to collect logs

Added by Lukas Zapletal 9 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

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

Associated revisions

Revision cfc1ba91 (diff)
Added by Ivan Necas 7 months ago

Fixes #21743 - include foreman-maintain in foreman-debug

History

#1 Updated by Anurag Patel 9 months ago

  • Assignee set to Anurag Patel
  • Status changed from New to Assigned

#2 Updated by Ivan Necas 9 months 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.

#3 Updated by Lukas Zapletal 9 months ago

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

#4 Updated by Ivan Necas 9 months 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

#5 Updated by Lukas Zapletal 7 months ago

  • Legacy Backlogs Release (now unused) set to 330

#6 Updated by Ivan Necas 7 months ago

  • Bugzilla link set to 1538640

#7 Updated by Ivan Necas 7 months ago

  • % Done changed from 0 to 100
  • Status changed from Assigned to Closed

#8 Updated by Anonymous about 1 month ago

  • Target version deleted (1.18.0)

Also available in: Atom PDF