Multipath connections can silently fall back to single path
Bug #1493962 reported by
Patrick East
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Right now when we are connecting with multipath you can get into a state where the iSCSI or FC volumes show up on the initiator, but multipath is broken enough that the multipath device does not appear. We handle this case gracefully and just pick one of the devices that did show up and use that to connect.
The problem though is that there isn't any log messaging to really make it apparent that even though configured for multipath it isn't really using the multipath device.
There isn't much we can do to prevent this from happening, and I would rather it fall back to the single path and keep working, but I do think maybe some log messaging could be helpful.
Changed in os-brick: | |
milestone: | none → 0.5.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/221913 /git.openstack. org/cgit/ openstack/ os-brick/ commit/ ?id=798f9650eaa 60f7fc5cad0acf5 67cd84b9d524ca
Committed: https:/
Submitter: Jenkins
Branch: master
commit 798f9650eaa60f7 fc5cad0acf567cd 84b9d524ca
Author: Patrick East <email address hidden>
Date: Wed Sep 9 11:51:32 2015 -0700
Log a message when can’t find multipath device
If we couldn’t find a multipath device we will now log a debug message
explaining as much. This can be helpful when troubleshooting issues with
multipath configurations and connections.
Change-Id: Ia41f65478df67d 5ff4857314aa749 cbf5cdc89d0
Closes-Bug: #1493962