Volume attach sets mountpoint as /dev/na in Cinder attachment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Opinion
|
Wishlist
|
Unassigned | ||
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann |
Bug Description
The Nova volume attachment is causing the device / mount point of the volume attachment in Cinder to be set to /dev/na.
The Trove gate is doing the following steps, though it could probably be recreated with a simple volume attach:
1. Spawn instance with ephemeral disk and specify a BDM to attach an existing volume:
{"os:scheduler_
Trove log link [1]
2. Detach the volume.
3. Resize the volume.
4. Attach the volume back to the instance
Nova log link [2]
5. Call to get volume attachments using Cinder API / cinderclient. Code pointer [3]
At this point the 'device' field in the attachment returned by Cinder is /dev/na.
This 'na' value is a default in Cinder if the 'mountpoint' is not passed in on the connector in attachment_update (code [4]).
So its likely that the attachment update that is occurring during the volume attach is not passing in the mountpoint on the connector.
[3] https:/
[4] https:/
description: | updated |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Matt Riedemann (mriedem) |
no longer affects: | cinder |
Changed in cinder: | |
status: | New → Opinion |
importance: | Undecided → Wishlist |
I'm guessing that's why this was in the nova code:
https:/ /review. openstack. org/#/c/ 525787/ 3/nova/ virt/block_ device. py@448
But we didn't know why it was there....