Bug 2342822
Summary: | [8.0z backport] RBD migration execute reports incorrect status when NBD export on the source is disconnected | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Bipin Kunal <bkunal> |
Component: | RBD | Assignee: | Ilya Dryomov <idryomov> |
Status: | CLOSED ERRATA | QA Contact: | Sunil Angadi <sangadi> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 | CC: | bhkaur, bkunal, ceph-eng-bugs, cephqe-warriors, idryomov, rgeorge, sangadi, tserlin |
Target Milestone: | --- | ||
Target Release: | 8.0z2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-19.2.0-76.el9cp | Doc Type: | Bug Fix |
Doc Text: |
.RBD migration execute command now no longer returns success when the import is interrupted
Previously, due to an implementation defect, the rbd migration execute command returned success even if the import was interrupted due to a network issue. As a result, the rbd status command reported the migration as executed, even though the import was left unfinished. The import appeared partially or completely unusable to the user.
With this fix, the rbd migration execute command no longer returns success when the import is interrupted due to a network issue, and the import remains usable to the user.
|
Story Points: | --- |
Clone Of: | 2339092 | Environment: | |
Last Closed: | 2025-03-06 14:21:07 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: |
Description
Bipin Kunal
2025-01-29 16:06:06 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 8.0 security, bug fixes, and enhancement updates), 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-2025:2457 |