Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I don't think this is a bug. qemu-nbd's job is to create /dev/nbd0,
which it is doing. It is the kernel's job to create /dev/nbd0p1 in your
case, which it is doing. There is nothing to say that it must do this
before you expect it to exist in your mount call. Similarly, partprobe
is not defined to block until the kernel has finished re-reading
devices. It only requests that the kernel start doing so.
If you need to block until /dev/nbd0p1 exists, you will need to wait for
it to appear yourself, or arrange to listen to the kernel's defined
interfaces for notification of it appearing, or just poll.
You might be interested in the mount-image-callback command from the
cloud-image-utils package, which does something very similar to what you
are doing. That would be the correct place to have handling for this
kind of blocking if it doesn't do it correctly already.
Or you could hook into udev, or use something like inotifywait to wait
for /dev/nbd0p1 to appear.
Since I don't think this is a valid bug, I'm marking this as Invalid.
But I'll subscribe to this bug and welcome further discussion.
** Changed in: qemu (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630341
Title:
yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't
automatically create partion devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1630341/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
