I thought with juju 2.1+ we no longer configure storage for LXD, which means we would no longer conflict.
I suppose as we introduce support for more directly controlling storage for lxd resources, we'll want to be using the new APIs and carving out our own pools. Can we confirm if 2.1+ still experiences this failure? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573681 Title: conflict when managing LXD storage with Juju 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-lxd/+bug/1573681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
