Ok, found the issue. This is in the juju logs: 68eb7d4f-c5f6-436c-82fb-5cd7a12cee2c: machine-0 2017-11-03 14:41:38 WARNING juju.provisioner provisioner_task.go:1070 failed to start instance (cannot run instances: cannot run instance: constraint match storage "5": 9 does not match a physical block device for the machine), retrying in 10s (10 more attempts)
Looking at the MAAS provider, I see this in volumes.go: deviceInfo, ok := mi.maasObject.GetMap()["physicalblockdevice_set"] The raid won't be in physicalblockdevice_set. Juju should look at blockdevice_set instead. Although I don't think that will fix it, since I also see that Juju uses id_path, which will be null for raid devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729127 Title: storage: No available machine matches constraints To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1729127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
