Okay, following instructions already provided by Chris Arges - responsible for the kernel bisection so far - and Ed - working on the case since its beginning - I was able to create another reproducer - not openstack dependant - that fails close to 100% of times.
Output: # running test ---- inaddy@alien:test$ ./teste.sh % RUN: 1 + Creating disk 0: /dev/vdb + Creating disk 1: /dev/vdc ! Starting virtual machine ! Adding disk 0: /dev/vdb ! Adding disk 1: /dev/vdc ! Waiting virtual machine network to be up ! Checking if disk is online: * Found 0 extra disks online $ Missing disk(s) exiting # checking results inaddy@alien:test$ ssh sf00068947precise Last login: Tue Aug 11 14:07:11 2015 from 192.168.128.1 inaddy@sf00068947precise:~$ ls -lah /dev/vd* brw-rw---- 1 root disk 253, 0 Aug 11 14:29 /dev/vda brw-rw---- 1 root disk 253, 1 Aug 11 14:29 /dev/vda1 brw-rw---- 1 root disk 253, 2 Aug 11 14:29 /dev/vda2 brw-rw---- 1 root disk 253, 5 Aug 11 14:29 /dev/vda5 inaddy@sf00068947precise:~$ echo 1 | sudo tee /sys/bus/pci/rescan 1 inaddy@sf00068947precise:~$ ls -lah /dev/vd* brw-rw---- 1 root disk 253, 0 Aug 11 14:29 /dev/vda brw-rw---- 1 root disk 253, 1 Aug 11 14:29 /dev/vda1 brw-rw---- 1 root disk 253, 2 Aug 11 14:29 /dev/vda2 brw-rw---- 1 root disk 253, 5 Aug 11 14:29 /dev/vda5 brw-rw---- 1 root disk 253, 16 Aug 11 14:29 /dev/vdb brw-rw---- 1 root disk 253, 32 Aug 11 14:29 /dev/vdc ---- Attaching files for this "second" reproducer. This will guide me on verifying a possible fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479031 Title: attached block devices not showing up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
