> Although the effect of Juju using the series flagged by distro data as latest LTS means that it will attempt to use bionic before it is ready.
distro-info-data clearly flags bionic as not released yet. For example, "distro-info --devel" works as expected. So please have Juju use that information. Wouldn't that be sufficient? I suggest that Juju adds to its CI tests to ensure Juju continues to work on all releases after the release marked "devel" becomes released, for example by bringing the release forward in distro-info-data. You should also add a separate test that adds the next release (make up a name!) to make sure it will work too. Please don't consider Juju fixed until you have CI in place for future updates to distro-info-data in all supported releases. See also bug 1314686 and bug 1321025 and the dep8 test I wrote that verifies that there is not a regression in a similar issue. I'm disappointed to hear that this type of issue is still happening. Perhaps the Juju architects need to rethink how you handle new distribution releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727355 Title: Juju attempts to bootstrap bionic by default To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
