Bug 2062853
| Summary: | The Status of cephcluster and "ceph status" [via tool pod] is different | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Oded <oviner> | ||||
| Component: | rook | Assignee: | Travis Nielsen <tnielsen> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Elad <ebenahar> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.10 | CC: | madam, mmuench, ocs-bugs, odf-bz-bot | ||||
| Target Milestone: | --- | Flags: | tnielsen:
needinfo?
(oviner) |
||||
| Target Release: | --- | ||||||
| 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: | 2022-04-04 15:19:40 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
Oded
2022-03-10 17:09:06 UTC
Oded It seems I can't access the must-gather. Was the must-gather collected before restarting the rook operator? Otherwise the outdated state of the operator and cephcluster CR will be lost. If you don't see any errors in the operator log about failing to update the cephcluster CR status, it may help to enable debug logging for the operator. In the rook-config-overrides configmap, you would set ROOK_LOG_LEVEL: DEBUG. The status updates every minute are only debug-level unless perhaps there is an error with the update. The ceph status on the CR should only be at most a minute outdated from what is seen from the toolbox, so two hours was plenty to wait! Not a blocker for 4.10 at least until there is a repro Actually this was fixed last week with another 4.10 BZ, didn't realize previously a fix was needed. *** This bug has been marked as a duplicate of bug 2069795 *** |