Bug 2004597 - Duplicate ramdisk log containers running
Summary: Duplicate ramdisk log containers running
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Derek Higgins
QA Contact: Lubov
Depends On:
Blocks: 2004600
TreeView+ depends on / blocked
Reported: 2021-09-15 16:08 UTC by Derek Higgins
Modified: 2022-03-10 16:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2004600 (view as bug list)
Last Closed: 2022-03-10 16:10:53 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-baremetal-operator pull 200 0 None open Bug 2004597: Remove duplicate ramdisk log container 2021-09-15 16:38:19 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:11:36 UTC

Description Derek Higgins 2021-09-15 16:08:56 UTC
The metal3 pod (and ironic on the bootstrap VM) both have 2 ramdisk-log containers running. 

This is a relic of have separate inspector and ironic images, now that the images are merged the runlogwatch.sh watches both log directories.

We only need one instance of the container.

Comment 3 Lubov 2021-10-13 08:48:18 UTC
verified on 4.10.0-0.nightly-2021-10-10-083341

Comment 6 errata-xmlrpc 2022-03-10 16:10:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.