Update foreman-debug to collect logs
#1 Updated by Anurag Patel over 5 years ago
- Assignee set to Anurag Patel
- Status changed from New to Assigned
#2 Updated by Ivan Necas over 5 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.
#3 Updated by Lukas Zapletal over 5 years ago
Bring it as a RPM dependency. I guess you require satellite to be present, do you? Problem solved.
#4 Updated by Ivan Necas over 5 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
#5 Updated by Lukas Zapletal about 5 years ago
- Legacy Backlogs Release (now unused) set to 330
#6 Updated by Ivan Necas about 5 years ago
- Bugzilla link set to 1538640
#7 Updated by Ivan Necas about 5 years ago
- % Done changed from 0 to 100
- Status changed from Assigned to Closed
Applied in changeset foreman:cfc1ba91d013124796661a41dd01388767beb14d.
#8 Updated by Anonymous over 4 years ago
- Target version deleted (
Fixes #21743 - include foreman-maintain in foreman-debug