Bug 1856309
| Summary: | [RFE] [cephadm] : save cephadm bootstrap logs in a log file | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vasishta <vashastr> | ||||||
| Component: | Cephadm | Assignee: | Juan Miguel Olmo <jolmomar> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Vasishta <vashastr> | ||||||
| Severity: | high | Docs Contact: | Karen Norteman <knortema> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 5.0 | CC: | pnataraj, sunnagar | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, TestBlocker | ||||||
| Target Release: | 5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-12-17 13:06:57 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Vasishta
2020-07-13 11:20:07 UTC
Created attachment 1730498 [details]
cephadm log
Created attachment 1730879 [details]
cehadm.log.1
@Juan, I was able to verify the logs again. We do not see the Dashboard credentials capturing in the cephadm.log file as displayed when bootstrap completes. If this is expected due to security reasons we can close this BZ. Please confirm. I assume rest all details are capturing in the cephadm.log except dashboard credentials displayed at the time of bootstrap completes @Juan, Is there a way to regenerate dashboard credentials as am not able to see the credentials getting captured in /var/log/cephadm.log and cephadm.log.1. We need them if we forget to login to dashboard url displayed at the time of bootstrap. Can we close this bug? The log file is created, the problem seen is because: https://bugzilla.redhat.com/show_bug.cgi?id=1901644 This is tracked in another BZ. https://bugzilla.redhat.com/show_bug.cgi?id=1901644. Hence, closing this as duplicate. *** This bug has been marked as a duplicate of bug 1901644 *** |