Back to bug 1319853
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| mulhern | 2016-03-21 16:31:19 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1319819 | |
| mulhern | 2016-03-21 17:41:52 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1319870 | |
| Ben Marzinski | 2016-03-22 18:26:16 UTC | Status | NEW | ASSIGNED |
| Assignee | lvm-team | bmarzins | ||
| Lin Li | 2016-03-23 02:30:21 UTC | CC | lilin | |
| QA Contact | storage-qe | lilin | ||
| mulhern | 2016-04-04 18:39:33 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1323806 | |
| Milan P. Gandhi | 2016-04-13 12:47:16 UTC | CC | mgandhi | |
| Ben Marzinski | 2016-04-20 18:06:36 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | device-mapper-multipath-0.4.9-89.el7 | |||
| Ben Marzinski | 2016-04-20 18:18:20 UTC | Doc Text | Cause: multipath thinks that anything device that isn't a block device path or major:minor number is a multipath alias. Consequence: If you use a path to something that is not a valid block device, multipath will tell you that it "requires a path to check", which is unhelpful Fix: Multipath will not treat fully qualified paths to things that aren't block devices as multipath aliases Result: Multipath will state the that path is "not a valid argument" for paths that don't belong to block devices. |
|
| errata-xmlrpc | 2016-07-05 20:14:01 UTC | Status | MODIFIED | ON_QA |
| Lin Li | 2016-07-07 01:47:38 UTC | Status | ON_QA | VERIFIED |
| Milan Navratil | 2016-10-10 12:45:44 UTC | Docs Contact | slevine | |
| Steven J. Levine | 2016-10-14 18:26:47 UTC | Doc Text | Cause: multipath thinks that anything device that isn't a block device path or major:minor number is a multipath alias. Consequence: If you use a path to something that is not a valid block device, multipath will tell you that it "requires a path to check", which is unhelpful Fix: Multipath will not treat fully qualified paths to things that aren't block devices as multipath aliases Result: Multipath will state the that path is "not a valid argument" for paths that don't belong to block devices. | Multipath now states that a path is "not a valid argument" for paths that do not belong to block devices Previously, if you used a path to something that is not a valid block device, multipath would tell you that it "requires a path to check", which is unhelpful. This is because multipath considered anything that is not a block device path or major:minor number to be a multipath alias. With this fix, multipath will not treat fully qualified paths to anything that is not a block devices as a multipath alias. As a result, multipath will state the that path is "not a valid argument" for paths that don't belong to block devices. |
| Steven J. Levine | 2016-10-19 18:42:18 UTC | Doc Text | Multipath now states that a path is "not a valid argument" for paths that do not belong to block devices Previously, if you used a path to something that is not a valid block device, multipath would tell you that it "requires a path to check", which is unhelpful. This is because multipath considered anything that is not a block device path or major:minor number to be a multipath alias. With this fix, multipath will not treat fully qualified paths to anything that is not a block devices as a multipath alias. As a result, multipath will state the that path is "not a valid argument" for paths that don't belong to block devices. | Multipath now states that a path is `not a valid argument` for paths that do not belong to block devices Previously, if you used a path to something that is not a valid block device, multipath would tell you that it `requires a path to check`, which is unhelpful. This is because multipath considered anything that is not a block device path or major:minor number to be a multipath alias. With this fix, multipath will not treat fully qualified paths to anything that is not a block devices as a multipath alias. As a result, multipath will state the that path is `not a valid argument` for paths that don't belong to block devices. |
| errata-xmlrpc | 2016-11-02 14:09:42 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-04 08:19:00 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-04 04:19:00 UTC | |||
| Lenka Špačková | 2016-11-23 13:14:33 UTC | Doc Text | Multipath now states that a path is `not a valid argument` for paths that do not belong to block devices Previously, if you used a path to something that is not a valid block device, multipath would tell you that it `requires a path to check`, which is unhelpful. This is because multipath considered anything that is not a block device path or major:minor number to be a multipath alias. With this fix, multipath will not treat fully qualified paths to anything that is not a block devices as a multipath alias. As a result, multipath will state the that path is `not a valid argument` for paths that don't belong to block devices. | Multipath now states that a path is `not a valid argument` for paths that do not belong to block devices Previously, if you used a path to something that is not a valid block device, multipath would tell you that it `requires a path to check`, which is unhelpful. This is because multipath considered anything that is not a block device path or major:minor number to be a multipath alias. With this fix, multipath will not treat fully qualified paths to anything that is not a block devices as a multipath alias. As a result, multipath will state the that path is `not a valid argument` for paths that do not belong to block devices. |
| Pavel Najman | 2021-09-03 11:57:53 UTC | Pool ID | sst_platform_storage_rhel_7 | sst_logical_storage_rhel_7 |
Back to bug 1319853