Bug 2215042
| Summary: | [CEE/SD][ceph-volume]Even though there is enough space in the DB device, the OSDs are not being created after attaching the device | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Guillaume Abrioux <gabrioux> |
| Component: | Ceph-Volume | Assignee: | Guillaume Abrioux <gabrioux> |
| Status: | CLOSED ERRATA | QA Contact: | Aditya Ramteke <aramteke> |
| Severity: | urgent | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | adking, akraj, bhull, ceph-eng-bugs, cephqe-warriors, gabrioux, gjose, kelwhite, msaini, msecaur, sostapov, tserlin, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 5.3z4 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.10-184.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.Re-running `ceph-volume lvm batch` command against created devices is now possible
Previously, in `ceph-volume`, `lvm` membership was not set for _mpath_ devices like it was for other types of supported devices. Due to this, re-running the `ceph-volume lvm batch` command against already created devices was not possible.
With this fix, the `lvm` membership is set for _mpath_ devices and re-running `ceph-volume lvm batch` command against already created devices is now possible.
|
Story Points: | --- |
| Clone Of: | 2203397 | Environment: | |
| Last Closed: | 2023-07-19 16:19:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2203397, 2239888 | ||
| Bug Blocks: | 2210690 | ||
|
Comment 1
Scott Ostapovicz
2023-06-14 16:00:16 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 (Red Hat Ceph Storage 5.3 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/RHBA-2023:4213 |