Bug 2052054
| Summary: | multipath removal (multipath -f) should return non zero when attempted on a non existent device | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> | |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | |
| Status: | CLOSED ERRATA | QA Contact: | Lin Li <lilin> | |
| Severity: | low | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 8.6 | CC: | agk, bmarzins, heinzm, lilin, msnitzer, prajnoha, zkabelac | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | device-mapper-multipath-0.8.4-24.el8 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: "multipath -f <device>" was returning success if there was no work that needed to be done.
Consequence: If "multipath -f" was run on a non-existent or non-multipath device, it would return success, since there was no device to remove
Fix: multipath now returns failure when a remove is attempted on an invalid device.
Result: running "multipath -f" on a non-existent device now fails.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2084358 (view as bug list) | Environment: | ||
| Last Closed: | 2022-11-08 10:47:39 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: | ||||
| Bug Blocks: | 2084358 | |||
|
Description
Corey Marthaler
2022-02-08 15:36:42 UTC
Verified on device-mapper-multipath-0.8.4-24.el8 [root@storageqe-05 ~]# rpm -qa | grep multipath device-mapper-multipath-0.8.4-24.el8.x86_64 device-mapper-multipath-libs-0.8.4-24.el8.x86_64 [root@storageqe-05 ~]# multipath -ll 360a98000324669436c2b45666c567865 dm-3 NETAPP,LUN size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 1:0:0:0 sdj 8:144 active ready running | `- 4:0:0:0 sdb 8:16 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 1:0:1:0 sdn 8:208 active ready running `- 4:0:1:0 sdf 8:80 active ready running 360a98000324669436c2b45666c567867 dm-4 NETAPP,LUN size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 1:0:0:1 sdk 8:160 active ready running | `- 4:0:0:1 sdc 8:32 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 1:0:1:1 sdo 8:224 active ready running `- 4:0:1:1 sdg 8:96 active ready running 360a98000324669436c2b45666c567869 dm-5 NETAPP,LUN size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 1:0:0:2 sdl 8:176 active ready running | `- 4:0:0:2 sdd 8:48 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 1:0:1:2 sdp 8:240 active ready running `- 4:0:1:2 sdh 8:112 active ready running 360a98000324669436c2b45666c56786b dm-6 NETAPP,LUN size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 1:0:0:3 sdm 8:192 active ready running | `- 4:0:0:3 sde 8:64 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 1:0:1:3 sdq 65:0 active ready running `- 4:0:1:3 sdi 8:128 active ready running [root@storageqe-05 ~]# multipath -f foobar May 23 03:46:05 | foobar is not a multipath device <--------------------------------- [root@storageqe-05 ~]# echo $? 1 <------------------------------------ [root@storageqe-05 ~]# multipath -f 360a98000324669436c2b45666c56786b [root@storageqe-05 ~]# echo $? 0 Test result: multipath removal (multipath -f) returns non zero when attempted on a non existent device 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 (device-mapper-multipath bug fix and enhancement 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-2022:7714 |