On 27/04/2016, Martin Packman <martin.pack...@canonical.com> wrote: > > That gets us started on maas 2.0 as part of revision testing. > Currently it fails early in the bootstrap process, as our setup is a > little more complex than what's been validated with so far: > > "boot resource 2.0 schema check failed: kflavor: expected string, got > nothing" > <https://bugs.launchpad.net/juju-core/+bug/1575768> > > I tried manually removing our centos images, which got a little further: > > "filesystem 2.0 schema check failed: mount_point: expected string, got > nothing" > <https://bugs.launchpad.net/juju-core/+bug/1575808>
Thanks for fixing those two! So, next one, much like the first two: "blockdevice 2.0 schema check failed: model: expected string, got nothing" <https://bugs.launchpad.net/juju-core/+bug/1576368> It does actually bootstrap now, just fails trying to deploy. <http://reports.vapour.ws/releases/3932/job/maas-2_0-deploy-xenial-amd64/attempt/3> Also as can be seen from that run, in this error case juju is not then managing to release the maas machines, so they're left around afterwards. It's possible a successful run won't leak machines, but we should try to make sure we can clean up even in error cases. Martin -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
