Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2238296

Summary:	[Tech preview] Designate containers use > 3GB likely because /openstack/healthcheck script doesn't exist
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	openstack-designate	Assignee:	Brent Eagles <beagles>
Status:	CLOSED WONTFIX	QA Contact:	Bruna Bonguardo <bbonguar>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	beagles, scohen
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-26 12:17:11 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:

Description Alex Stupnikov 2023-09-11 09:53:58 UTC

Description of problem:
Recently one of our customers reported a problem with designate in RHOSP 16.2: The designate containers use about 12GB of disk on all controllers while other clusters are using about 1 GB. The disk usage of /var/lib/containers/storage/overlay-containers/<container_id> to be >3GB for the containers: designate_central, designate_mdns, designate_producer, designate_worker.

Customer figured out that healthcheck loop created a lot of "ExecIDs" (visible from podman inspect) which wasn't always cleaned. Script /openstack/healthcheck does not exist on designate 16.2.2.

I checked if it exists in latest RHOSP 16.2.5 and found out that it doesn't.

I understand that Designate in RHOSP 16.2 is in tech preview, but reporting this BZ to ask to double-check if this was fixed in RHOSP 17 and if we can fix this basic problem in RHOSP 16.2.

Version-Release number of selected component (if applicable):
RHOSP 16.2

Comment 2 Brent Eagles 2023-09-26 12:18:22 UTC

Closed as WONTFIX for 16.2 but note that the suspected root cause has already been reported in https://bugzilla.redhat.com/show_bug.cgi?id=2116300