I wondered on an all numerical sha but found:
commit 5729746543cf4df5c7b1adea877b4fe45bf67e51
Author: Nitesh Konkar <[email protected]>
Date: Wed Feb 15 16:44:58 2017 +0530
Ensure disk names follow the disk name regex
Currently disk names do not follow the
(regex) /^[fhv]d[a-z]+[0-9]*$/ completely
and hence one can assign disk names like
vd2 etc. This patch ensures that the
disk names follow the regex mentioned.
This patch also adds a testcase.
So it is not a bug to handle it wrong, but instead to allow those names while
they should not be allowed. And then by being a specifier outside of the
expected specification failing to process correctly.
TL;DR of the bug "[a-z]+ was actually a [a-z]*"
I checked and the fix would apply cleanly to Xenial, Yakkety and Zesty.
To some extend (the fix yes, the change to the testcase no) also to Trusty.
** Also affects: libvirt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Zesty)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: Confirmed
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665410
Title:
Libvirt allows specifying out-of-spec disk dev attributes it is then
unable to handle
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1665410/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
