Bug 2151449 - OSP17.1 | rsyslog container won't start without imfile module. [NEEDINFO]
Summary: OSP17.1 | rsyslog container won't start without imfile module.
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-rsyslog
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z2
: 17.1
Assignee: Martin Magr
QA Contact: Leonid Natapov
mgeary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-07 07:10 UTC by Leonid Natapov
Modified: 2023-08-03 15:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
ifrangs: needinfo? (mmagr)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-20795 0 None None None 2022-12-07 15:58:02 UTC

Description Leonid Natapov 2022-12-07 07:10:06 UTC 
rsyslog container won't start without imfile module.

In OSP16.2 we load imfile  module by default even if we don't have any actions configured in rsyslog.conf but in OSP17.1,if there are no actions configured, modules are not loaded at all. So even after you add actions to the rsyslog.conf,the  container will not start. That's a minor issue since usually actions will be defined *before* deploying rsyslog but still it's better to load at least imfiles module by default like we did in OSP16.
Comment 5 Lukas Svaty 2023-06-16 08:13:29 UTC 
Bulk moving target milestone to GA after the release of Beta on 14th June '23.
Comment 6 Leif Madsen 2023-06-16 18:25:19 UTC 
Shifting this to 17.1 z2 due to z1 being only for urgent bugs and this has missed beta and GA.
Note You need to log in before you can comment on or make changes to this bug.