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 2153709

Summary:	[RFE] Ceph orchestrator operations silently hang when one or more hosts have no space in /var/log directory
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Yalcin <yalbayra>
Component:	Cephadm	Assignee:	Adam King <adking>
Status:	CLOSED DUPLICATE	QA Contact:	Manisha Saini <msaini>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.2	CC:	cephqe-warriors
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	6.1
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-31 19:34:54 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 Yalcin 2022-12-15 09:41:45 UTC

Description of problem:When one or more hosts in the cluster have filled /var/log directory, commands like "ceph orch rm xxx" or "ceph orch apply yyy" hangs without any warning/error to see. This cause all orchestration to stop in case of an issue on a host without any feedback to identify the problem. 


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


How reproducible:
By filling /var/lib of a host in cluster and trying to apply/rm services

Steps to Reproduce:
1. Fill all space in /var/log of a host
2. ceph orch apply/rm service. This will hang with no errors showed
3. Free up some space in filled /var/log
4. Restart mgr service. After restart, apply/rm job will work

Actual results:
In case of full /var/log directory in a cluster host, ceph orch apply/rm commands hang silently.

Expected results:
In case of any health check fail in a cluster host, ceph orch apply/rm commands must fail with an error which identifies the possible issue.

Additional info:

Comment 7 Adam King 2023-03-31 19:34:54 UTC


*** This bug has been marked as a duplicate of bug 2151908 ***