Feature #21743: Update foreman-debug to collect logs - Foreman Maintain - Foreman

Actions

Copy link

Feature #21743

closed

Update foreman-debug to collect logs

Added by Lukas Zapletal almost 7 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Anurag Patel

Category:

Target version:

1.18.0

Difficulty:

Triaged:

Bugzilla link:

1538640

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

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

Actions

Copy link

Updated by Anurag Patel almost 7 years ago

Status changed from New to Assigned
Assignee set to Anurag Patel

Actions

Copy link

Updated by Ivan Necas almost 7 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

Copy link

Updated by Lukas Zapletal almost 7 years ago

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

Actions

Copy link

Updated by Ivan Necas almost 7 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

Copy link