nova-lvm tempest job failing with InvalidDiskInfo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann | ||
Ocata |
Fix Released
|
High
|
Lee Yarwood | ||
Pike |
Fix Released
|
High
|
Lee Yarwood | ||
Queens |
Fix Released
|
High
|
Lee Yarwood | ||
Ubuntu Cloud Archive |
Fix Released
|
High
|
Unassigned | ||
Ocata |
Fix Released
|
High
|
Unassigned | ||
Pike |
Fix Released
|
High
|
Unassigned | ||
Queens |
Fix Released
|
High
|
Unassigned | ||
Rocky |
Fix Released
|
High
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Unassigned | ||
Cosmic |
Fix Released
|
High
|
Unassigned |
Bug Description
There has been a recent regression in the nova-lvm tempest job. The most recent passing run was on 2018-05-11 [1][2], so something regressed it between then and yesterday 2018-05-15.
The build fails and the following trace is seen in the n-cpu log:
May 15 23:01:40.174233 ubuntu-
May 15 23:01:40.174457 ubuntu-
May 15 23:01:40.174699 ubuntu-
May 15 23:01:40.174922 ubuntu-
May 15 23:01:40.175170 ubuntu-
May 15 23:01:40.175414 ubuntu-
May 15 23:01:40.175641 ubuntu-
May 15 23:01:40.175868 ubuntu-
May 15 23:01:40.176091 ubuntu-
May 15 23:01:40.176333 ubuntu-
May 15 23:01:40.176555 ubuntu-
May 15 23:01:40.176773 ubuntu-
May 15 23:01:40.176994 ubuntu-
May 15 23:01:40.177215 ubuntu-
May 15 23:01:40.177452 ubuntu-
May 15 23:01:40.177674 ubuntu-
May 15 23:01:40.177902 ubuntu-
May 15 23:01:40.178118 ubuntu-
May 15 23:01:40.178344 ubuntu-
May 15 23:01:40.178989 ubuntu-
I think the failure is related to this change that merged on 2018-05-15:
https:/
which moved the call of disk_api.
[1] http://
[2] https:/
Changed in nova: | |
assignee: | Lee Yarwood (lyarwood) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Lee Yarwood (lyarwood) |
Changed in nova: | |
assignee: | Lee Yarwood (lyarwood) → Matt Riedemann (mriedem) |
Changed in nova (Ubuntu Cosmic): | |
importance: | Undecided → High |
status: | New → Fix Released |
Changed in nova (Ubuntu Bionic): | |
importance: | Undecided → High |
status: | New → Triaged |
Thanks Mel, qemu-img obviously works against block devices, the issue here is that we are using it against a block device as a non-privileged user, something I missed as it's buried deep down in our wonderfully convoluted stack to fetch basic disk details </rant>.
Would it be possible to run the nova-lvm job as a NV job against nova/virt/libvirt/* changes?