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

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2160633

Summary:	[RFE] : Assign container name to single command temporary containers also
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vasishta <vashastr>
Component:	Cephadm	Assignee:	Adam King <adking>
Status:	CLOSED DEFERRED	QA Contact:	Mohit Bisht <mobisht>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.3	CC:	cephqe-warriors, saraut
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-08-28 10:41:21 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 Vasishta 2023-01-13 06:12:46 UTC

Description of problem:
As of now we are not assigning container names to single command usage temporary containers.
Eg: ceph-volume config containers.

It would be nice to assign the names to all the containers so that it becomes easier for users to understand better incase of analysing.
In our case ceph-volume command was hung and the temp container was alive for considerable amount of time.
It would be nice if we can assign a suitable name so that it becomes easy to analyse.

Version-Release number of selected component (if applicable):
16.2.10-94.el9cp

How reproducible:
Always (* when there is an issue with temporary containers)

Comment 2 Sahina Bose 2025-08-28 10:41:21 UTC

Closing this bug as part of bulk closing of bugs that have been open for more than 2 years without any significant updates for the last 3 months. Please reopen with justification if you think this bug is still relevant and needs to be addressed in an upcoming release