OK. so, re-reading the above, and conversing with Martin. things of note: * after first boot, the volume showed as 'in-use', but the disk was not attached to the instance. * after re-boot, the volume showed as 'available' again. Basically, the volume got stuck in 'in-use' when it really wasnt.
I suspect that what happened was this: * initial attach failed badly, leaving 'in-use' * the reboot (or possibly a timeout) kicked nova to re-evaluate the situation, and it recognized that the volume was not in-use. So, i think the real issue is likely that the volume just got marked as in use, even though the libvirt (or something else) actually failed, and then it took something (timeout or reboot) to get back to sane state. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1000710 Title: Attaching volume during instance boot doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1000710/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
