Bug 1496509
| Summary: | ceph-disk prepare cannot find paritition that does exist when run inside containers | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | jomurphy |
| Component: | Ceph-Disk | Assignee: | Kefu Chai <kchai> |
| Status: | CLOSED ERRATA | QA Contact: | John Fulton <johfulto> |
| Severity: | high | Docs Contact: | Aron Gunn <agunn> |
| Priority: | urgent | ||
| Version: | 2.4 | CC: | agunn, anharris, bniver, ceph-qe-bugs, dcadzow, flucifre, gfidente, gkadam, gmeno, hnallurv, jefbrown, johfulto, kchai, kdreyer, pgrist, sasha, shan, yrabl |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 2.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-10.2.10-9.el7cp Ubuntu: ceph_10.2.10-6redhat1xenial | Doc Type: | Bug Fix |
| Doc Text: |
.In containerized deployment, `ceph-disk` now retries when it cannot find a partition
Due to a possible race condition between kernel and the `udev` utility, the device file for a partition was not created when the `ceph-disk` utility searched for it. Consequently, the `ceph-disk` utility could not create the partition. In this release, when `ceph-disk` cannot find the partition, it retries the search again, thus working around this possible race condition.
|
Story Points: | --- |
| Clone Of: | 1494543 | Environment: | |
| Last Closed: | 2018-02-21 19:43:32 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: | |||
| Bug Depends On: | 1494543 | ||
| Bug Blocks: | 1496985, 1507644, 1536401 | ||
|
Comment 5
Sébastien Han
2017-12-15 16:32:51 UTC
Kefu, since https://github.com/ceph/ceph/pull/18169 did not make v10.2.10 upstream, would you please cherry-pick the changes for this BZ to ceph-2-rhel-patches, with "Resolves: rhbz#1496509" ? Ken, pushed to your mirror! thanks for unblocking me. =) verified 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, 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-2018:0340 |