Scrub residual iscsi devices before connecting iSCSI volume
Registered by
Yafei Yu
Some iscsi volumes create failed when creating volumes from image, especially in batch. The reason is some iscsi devices have existed, but they are not the connecting iscsi volume generated, which are residual iscsi devices. That is a problem. This blueprint proposes to import a way to scrub the residual iscsi devices before connecting iscsi volume in cinder.
Blueprint information
- Status:
- Not started
- Approver:
- Sean McGinnis
- Priority:
- Low
- Drafter:
- Yafei Yu
- Direction:
- Approved
- Assignee:
- Yafei Yu
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
| Bug #1553730: create volume from image failed, the residual device in host cause we can't find the multipath device to copy image | Incomplete |
Sprints
Whiteboard
I think the general idea is good, but we probably need a spec written up so we can discuss how something like this would be implemented.
Gerrit topic: https:/
Addressed by: https:/
Scrub residual iscsi devices before connecting iSCSI volume
(?)
