Bug 1901644

Summary:	[cephadm] 5.0 - bootstrap logs are not getting captured fully in a cephadm.log due to less file size
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Preethi <pnataraj>
Component:	Cephadm	Assignee:	Adam King <adking>
Status:	CLOSED ERRATA	QA Contact:	Rahul Lepakshi <rlepaksh>
Severity:	low	Docs Contact:
Priority:	high
Version:	5.0	CC:	agunn, jolmomar, rlepaksh, vashastr, vereddy
Target Milestone:	---
Target Release:	5.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-16.2.6-1.el8cp	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-04 10:19: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:

Description Preethi 2020-11-25 17:35:43 UTC

Description of problem:[cephadm] 5.0 - bootstrap logs are not getting captured fully in a cephadm.log due to less file size


Version-Release number of selected component (if applicable):
[root@magna106 ubuntu]# sudo cephadm version
Using recent ceph image registry.redhat.io/rhceph-alpha/rhceph-5-rhel8:latest
ceph version 16.0.0-7209.el8cp (dc005a4e27b091d75a4fd83f9972f7fcdf9f2e18) pacific (dev)
[root@magna106 ubuntu]# 


How reproducible:


Steps to Reproduce:
1.Perform boot strap
2. once bootstrap completes verify the logs in /varlog/ceph/ 


Actual results: bootstrap logs are not captured fully in cephadm.log and cephadm.log.1 files. We need to increase the log file to max and provide more backup files for log rotation.


Expected results:


Additional info:
magna106 root/q - setup details

Comment 1 Preethi 2020-12-17 13:06:55 UTC

*** Bug 1856309 has been marked as a duplicate of this bug. ***

Comment 2 Yaniv Kaul 2021-04-18 15:24:36 UTC

Juan, any updates?

Comment 3 Juan Miguel Olmo 2021-04-23 06:56:42 UTC

@Yaniv: lets go with this ... I think i should have changed severity and priority (to low) long time ago.

Comment 4 Sebastian Wagner 2021-04-26 08:12:33 UTC

Thinking. There is nothing the cephadm bootstrap logs that is not available afterwards. Which info were you looking for?

Comment 6 Veera Raghava Reddy 2021-05-06 11:31:15 UTC

Vasi can you look into this BZ and provide info to take to closure.

Comment 7 Sebastian Wagner 2021-05-06 12:52:58 UTC

Wait, the cephadm log file is outside of the cluster's log directory. Is https://github.com/ceph/ceph/blob/f454a77d5ebd3f01a79c19c4420e3b9a9b96ac68/src/cephadm/cephadm#L2992-L3003 really affecting the cephadm.log?

Comment 8 Vasishta 2021-05-06 13:17:47 UTC

I think Preethi is pointing out https://github.com/ceph/ceph/blob/f454a77d5ebd3f01a79c19c4420e3b9a9b96ac68/src/cephadm/cephadm#L216-L217

(Clearing needinfo as previous required info has been provided offline)

Comment 10 Sebastian Wagner 2021-05-31 12:34:07 UTC

pending backport

Comment 11 Daniel Pivonka 2021-06-01 19:18:40 UTC

upstream pr: https://github.com/ceph/ceph/pull/41283(merged already pending backport to pacific)
upstream tracker: https://tracker.ceph.com/issues/51056

Comment 12 Sebastian Wagner 2021-06-29 11:50:41 UTC

fix is now in pacific

Comment 23 errata-xmlrpc 2022-04-04 10:19: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: Red Hat Ceph Storage 5.1 Security, Enhancement, and Bug Fix 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:1174