Bug 2004597

Summary:	Duplicate ramdisk log containers running
Product:	OpenShift Container Platform	Reporter:	Derek Higgins <derekh>
Component:	Bare Metal Hardware Provisioning	Assignee:	Derek Higgins <derekh>
Bare Metal Hardware Provisioning sub component:	cluster-baremetal-operator	QA Contact:	Lubov <lshilin>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	aos-bugs, lshilin
Version:	4.10	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2004600 (view as bug list)		Environment:
Last Closed:	2022-03-10 16:10:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2004600

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.

https://access.redhat.com/errata/RHSA-2022:0056