Ok, if broken in pike+arm64 still that means it is broken in the latest qemu/libvirt we currently have (until we bumped for Bionic/Queens). That also implies that all fixes that were meant to be identified before can't be the fix as they are in arm64+pike.
This will get more complex once we need SRU's as I outlined in e.g. comment #19 and grows a bigger dependency chain of changes over time. But before any of that we have to find a combination that works at all. So for now I suggest to not think about anything but latest devel as it only makes the case more complex (we can think about that later once it works). I see three options here to continue: 1. we can wait for our bionic/queens bump of the virtualization stack and retry, but there are no indications that we should have more than a "trial and error" level of hope for that 2. someone in contact with Linaro should ask them about their setup exactly on which they fixed those bugs - I have to assume that after such a fix their testcase worked. If that holds true for us we have to start identifying what is different in our testcase. 3. Someone has to break the complexity of openstack out of this test and create a list of reproducible commands that "would do what openstack does" in regard to volume creation, guest spawning and attaching. Once reproducible that way we can start debugging and also call out for upstream to help thinking with us through this case. Mostly likely this will also be required for SRUs later on so maybe that is the best step to take. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664737 Title: [ARM] : Unable to use Cinder volumes on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1664737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
