[Bug 1756863] Re: package golang-juju-loggo-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gocode/src/github.com/juju/loggo/formatter_test.go', which is also in package
I can't re-assign it seems. Poke @thumper. ** Changed in: golang-juju-loggo (Ubuntu) Assignee: Nicholas Skaggs (nskaggs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756863 Title: package golang-juju-loggo-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gocode/src/github.com/juju/loggo/formatter_test.go', which is also in package golang-github-juju-loggo-dev 0.0~git20150527.0.8477fc9-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-juju-loggo/+bug/1756863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766415] Re: [SRU] Juju 2.3.7
** Changed in: juju-core (Ubuntu) Status: New => Fix Committed ** Changed in: juju-core (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766415 Title: [SRU] Juju 2.3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1766415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766415] Re: [SRU] Juju 2.3.7
** Description changed: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.3.7 + Specifically, we are seeking to avoid changing the default bootstrap + series for the archive package of juju in an LTS. This change ensures + xenial remains the default series. See bug 1762741. + [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here (Canonical VPN access is required): http://10.125.0.203:8080/job/ci-run/621/ In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Description changed: This syncs juju with the upstream release bringing the latest bugfixes - and enhancements. + and enhancements. It also solves bug 1762741. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.3.7 Specifically, we are seeking to avoid changing the default bootstrap series for the archive package of juju in an LTS. This change ensures xenial remains the default series. See bug 1762741. [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here (Canonical VPN access is required): http://10.125.0.203:8080/job/ci-run/621/ In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Description changed: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. It also solves bug 1762741. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] - A full list of targeted bugs can be seen against the milestone, and the intervening milestones: + Specifically, we are seeking to avoid changing the default bootstrap series for the archive package of juju in an LTS. This change ensures xenial remains the default series. See bug 1762741. + A full list of targeted bugs can be seen against the milestone, and the + intervening milestones: + + https://launchpad.net/juju/+milestone/2.3.3 + https://launchpad.net/juju/+milestone/2.3.4 + https://launchpad.net/juju/+milestone/2.3.5 + https://launchpad.net/juju/+milestone/2.3.6 https://launchpad.net/juju/+milestone/2.3.7 - - Specifically, we are seeking to avoid changing the default bootstrap - series for the archive package of juju in an LTS. This change ensures - xenial remains the default series. See bug 1762741. [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here (Canonical VPN access is required): http://10.125.0.203:8080/job/ci-run/621/ In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766415 Title: [SRU] Juju 2.3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1766415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766415] Re: [SRU] Juju 2.3.7
I tested juju 2.3.7 and found no issues. Tested: Bootstrap xenial and bionic controllers Deploy various workloads, including percona Installed and bootstrapped 2.3.2 controller and model, upgraded package, and tested juju-upgrade 2.3.2 -> 2.3.7 Checked bash-completion Deployed offline (xenial and bionic controllers) ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766415 Title: [SRU] Juju 2.3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1766415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766415] Re: [SRU] Juju 2.3.7
The source package can be found in https://git.launchpad.net/~juju- qa/ubuntu/+source/juju-core, master branch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766415 Title: [SRU] Juju 2.3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1766415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765257] Re: [SRU] Juju 2.3.6
** Changed in: juju-core (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765257 Title: [SRU] Juju 2.3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1765257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761807] Re: [FFe] Bump mongodb to 3.6.X
As an update to note, the juju team has done further manual testing on the build in ppa:racb/experimental to ensure it meets our needs. This included running real workloads and performing controller operations like migration and HA. We're happy with the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761807 Title: [FFe] Bump mongodb to 3.6.X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongo-tools/+bug/1761807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761807] [NEW] [FFe] Bump mongodb to 3.6.X
Public bug reported: I am requesting we bump mongodb to the latest 3.6 version. Rationale: The default version of openssl in bionic is 1.1. Mongo3.4 doesn't support this version, while mongo3.6 does. Mongo upstream support generally averages 3 to 3.5 years, see https://www.mongodb.com/support-policy. At the moment, mongo hasn't decided on the support lifetime for mongo3.6. However, there's reason to believe it will be both supported for longer than mongo3.4, and perhaps longer than previous releases. This will allow more upstream overlap for the life of the LTS. Finally, juju itself will benefit from the newer version of mongo3.6, and can take advantage of features exposed at a later date. Logs: Package: The proposed package has already been built thanks to Robie Basak, and can be seen in his ppa: ppa:racb/experimental. Robie has also graciously volunteered to upload this package to fufill this FFe. Testing: The juju team has done initial validation to ensure this meets our needs. This included running our test suite utilizing the packaged mongodb from Robie's ppa. ** Affects: mongodb (Ubuntu) Importance: Undecided Status: Triaged ** Tags: upgrade-software-version ** Summary changed: - [FFe] Rev mongodb-server-core to 3.6.X + [FFe] Bump mongodb to 3.6.X -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761807 Title: [FFe] Bump mongodb to 3.6.X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1761807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756432] Re: [FFe] Split out mongodb-server-core
Thanks. You are correct. This is just playing with packaging; the source is unchanged. I was thinking the same about not needing an FFe, but I filed one anyway. If nothing else, it can provide clarity for anyone who may have wondered why the split occurred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756432 Title: [FFe] Split out mongodb-server-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1756432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756432] [NEW] [FFe] Split out mongodb-server-core
Public bug reported: I am requesting a mongodb-server-core package that provides only mongodb-server-binaries, with no user or services management. The package should remain in universe, and be supported accordingly. Rationale: Juju is migrating to mongodb 3.4 for bionic, and would like to phase out the usage of juju-mongodb packages. The proposed mongodb-server-core package will meet juju's needs, as well as potentially other users needs within the archive who may have utilized juju-mongodb for it's similar properties. Lifespan: Juju is actively working to migrate to a more tightly coupled distribution for mongodb (as with juju agents, simplestreams) that would better serve the fast paced nature of the project. Therefore the juju team anticipates no longer depending on this package post-bionic. Logs: There is no upstream changelog, as the version hasn't changed. https://launchpadlibrarian.net/357300754/buildlog_ubuntu-bionic- amd64.mongodb_1%3A3.4.7-1ubuntu3~ppa2_BUILDING.txt.gz Package: The proposed package has already been built thanks to Robie Basak, and can be seen in his ppa: ppa:racb/experimental. Robie has also graciously volunteered to upload this package to fufill this FFe. Testing: The juju team has done initial validation to ensure this meets our needs. This included running our test suite utilizing the packaged mongodb from Robie's ppa. ** Affects: mongodb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756432 Title: [FFe] Split out mongodb-server-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1756432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744968] Re: [SRU] Juju 2.3.2
** Changed in: juju-core (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744968] Re: [SRU] Juju 2.3.2
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744968] Re: [SRU] Juju 2.3.2
I tested juju 2.3.2 and found it working, able to bootstrap, deploy, bash completion all work. I deployed a bionic controller and workload as well without any apparent issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744968] Re: [SRU] Juju 2.3.2
** Changed in: juju-core (Ubuntu Xenial) Status: New => In Progress ** Changed in: juju-core (Ubuntu Artful) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744968] [NEW] [SRU] Juju 2.3.2
Public bug reported: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.3.2 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here: http://qa.jujucharms.com/releases/6159 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Affects: juju-core (Ubuntu) Importance: Undecided Assignee: Nicholas Skaggs (nskaggs) Status: In Progress ** Affects: nplan (Ubuntu) Importance: High Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: In Progress ** Affects: juju-core (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: nplan (Ubuntu Xenial) Importance: High Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: In Progress ** Affects: juju-core (Ubuntu Artful) Importance: Undecided Status: New ** Affects: nplan (Ubuntu Artful) Importance: High Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: In Progress ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) ** Changed in: juju-core (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
Confirming 2.3.1 proposed package works for xenial and zesty. 1. Bootstrap completes successfully 2. Agent is used from stream 3. default-series in metadata is xenial 4. distro-info-data contains bionic ** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-zesty -- 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
[Bug 1718213] Re: [SRU] Juju 2.3.1
Both zesty and xenial are verified. Bootstrap and deploy, update-clouds and tab completion all working. ** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718213 Title: [SRU] Juju 2.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
** Changed in: juju Status: Triaged => Invalid ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718213] Re: [SRU] Juju 2.3.1
** Summary changed: - [SRU] Juju 2.2.6 + [SRU] Juju 2.3.1 ** Description changed: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.0.3 https://launchpad.net/juju/+milestone/2.0.4 https://launchpad.net/juju/+milestone/2.1.0 https://launchpad.net/juju/+milestone/2.1.1 https://launchpad.net/juju/+milestone/2.1.2 https://launchpad.net/juju/+milestone/2.1.3 https://launchpad.net/juju/+milestone/2.2.0 https://launchpad.net/juju/+milestone/2.2.1 https://launchpad.net/juju/+milestone/2.2.2 https://launchpad.net/juju/+milestone/2.2.3 https://launchpad.net/juju/+milestone/2.2.4 https://launchpad.net/juju/+milestone/2.2.5 https://launchpad.net/juju/+milestone/2.2.6 + https://launchpad.net/juju/+milestone/2.3.0 + https://launchpad.net/juju/+milestone/2.3.1 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here: http://qa.jujucharms.com/releases/5729 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Description changed: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.0.3 https://launchpad.net/juju/+milestone/2.0.4 https://launchpad.net/juju/+milestone/2.1.0 https://launchpad.net/juju/+milestone/2.1.1 https://launchpad.net/juju/+milestone/2.1.2 https://launchpad.net/juju/+milestone/2.1.3 https://launchpad.net/juju/+milestone/2.2.0 https://launchpad.net/juju/+milestone/2.2.1 https://launchpad.net/juju/+milestone/2.2.2 https://launchpad.net/juju/+milestone/2.2.3 https://launchpad.net/juju/+milestone/2.2.4 https://launchpad.net/juju/+milestone/2.2.5 https://launchpad.net/juju/+milestone/2.2.6 https://launchpad.net/juju/+milestone/2.3.0 https://launchpad.net/juju/+milestone/2.3.1 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here: - http://qa.jujucharms.com/releases/5729 + http://qa.jujucharms.com/releases/6058 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718213 Title: [SRU] Juju 2.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730706] Re: RM FTBFS with new scons, new g++, new C++ standards
We will seek to ship juju-mongo3.6 in leiu of this package. We need mongo3.6 for juju 2.4, which will ship with bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730706 Title: RM FTBFS with new scons, new g++, new C++ standards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1730706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
Frode, the procps restart is necessary to apply the sysctl parameters we set for LXD containers to provide a better experience for the juju use case. If we don't do this, it would require a system restart for the parameters to apply. -- 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
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
It seems systemd has always acted this way, but apparently there's a fix in 232+. -- 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
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
For SRU verification, we want to ensure juju bootstrap still selects xenial, even after distro-info-data shows bionic as an LTS. I confirmed using the restored distro-info-data packages in zesty and xenial proposed that juju is selecting xenial as the proper default series. In addition, I confirmed juju will select bionic as the new default on it's prescribed release day. ** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-zesty -- 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
[Bug 1718213] Re: [SRU] Juju 2.2.6
Both zesty and xenial are verified and working successfully. I was able to bootstrap and deploy on multiple providers, update-clouds and tab completion worked, binaries and version are all as expected. ** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718213 Title: [SRU] Juju 2.2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
** Changed in: juju-core (Ubuntu Trusty) Status: New => Invalid -- 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
[Bug 1718213] Re: [SRU] Juju 2.2.6
Due to bug 1727355 which has a critical fix required for juju to operate properly on xenial, we're aiming to land juju 2.2.6 now. ** Description changed: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.0.3 https://launchpad.net/juju/+milestone/2.0.4 https://launchpad.net/juju/+milestone/2.1.0 https://launchpad.net/juju/+milestone/2.1.1 https://launchpad.net/juju/+milestone/2.1.2 https://launchpad.net/juju/+milestone/2.1.3 https://launchpad.net/juju/+milestone/2.2.0 https://launchpad.net/juju/+milestone/2.2.1 https://launchpad.net/juju/+milestone/2.2.2 https://launchpad.net/juju/+milestone/2.2.3 https://launchpad.net/juju/+milestone/2.2.4 + https://launchpad.net/juju/+milestone/2.2.5 + https://launchpad.net/juju/+milestone/2.2.6 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here: http://qa.jujucharms.com/releases/5729 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718213 Title: [SRU] Juju 2.2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
Tested working on zesty:
# juju bootstrap lxd --debug
18:41:15 INFO juju.cmd supercommand.go:63 running juju [2.0.2 gc go1.7.4]
...
18:41:15 DEBUG juju.cmd.juju.commands bootstrap.go:834 provider attrs: map[]
18:41:16 INFO cmd cmd.go:141 Adding contents of
"/root/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
18:41:16 DEBUG juju.cmd.juju.commands bootstrap.go:890 preparing controller
with config: map[... default-series:xenial
...
18:41:16 INFO cmd cmd.go:129 Creating Juju controller "lxd-localhost" on
lxd/localhost
18:41:16 INFO juju.cmd.juju.commands bootstrap.go:507 combined bootstrap
constraints:
18:41:16 DEBUG juju.environs.bootstrap bootstrap.go:202 model "controller"
supports service/machine networks: false
18:41:16 DEBUG juju.environs.bootstrap bootstrap.go:204 network management by
juju enabled: true
18:41:16 INFO cmd cmd.go:141 Loading image metadata
18:41:16 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0.2 for
amd64
18:41:16 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent
binaries: version=2.0.2
18:41:16 INFO juju.environs.tools tools.go:101 finding agent binaries in
stream "released"
18:41:16 INFO juju.environs.tools tools.go:103 reading agent binaries with
major.minor version 2.0
18:41:16 INFO juju.environs.tools tools.go:111 filtering agent binaries by
version: 2.0.2
18:41:16 INFO juju.environs.tools tools.go:117 filtering agent binaries by
architecture: amd64
18:41:16 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone
catalog"
18:41:17 DEBUG juju.environs.simplestreams simplestreams.go:680 using default
candidate for content id "com.ubuntu.juju:released:tools" are {20161007
mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
18:41:20 INFO juju.environs.bootstrap tools.go:74 found 16 packaged agent
binaries
18:41:20 INFO cmd cmd.go:141 Starting new instance for initial controller
...
18:41:20 DEBUG juju.provider.lxd environ_broker.go:41 StartInstance: "0", xenial
18:41:20 DEBUG juju.cloudconfig.instancecfg instancecfg.go:782 Setting numa ctl
preference to false
18:41:20 DEBUG juju.environs imagemetadata.go:112 obtained image datasource
"default cloud images"
18:41:20 DEBUG juju.environs imagemetadata.go:112 obtained image datasource
"default ubuntu cloud images"
18:41:20 DEBUG juju.provider.lxd environ_broker.go:113 LXD requires https://,
using: https://cloud-images.ubuntu.com/releases/
18:41:20 DEBUG juju.tools.lxdclient client.go:199 connecting to LXD remote
"default cloud images": "https://streams.canonical.com/juju/images/releases/";
18:41:20 INFO juju.tools.lxdclient client_image.go:118 no image for
ubuntu-xenial found in https://streams.canonical.com/juju/images/releases/
18:41:20 DEBUG juju.tools.lxdclient client.go:199 connecting to LXD remote
"default ubuntu cloud images": "https://cloud-images.ubuntu.com/releases/";
18:41:27 INFO juju.tools.lxdclient client_image.go:124 found image from
https://cloud-images.ubuntu.com/releases/ for xenial =
61d54418874f2f84e24ddd6934b3bb759ca76cbc49820da7d34f8b5b778e4816
...
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
--
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
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
Tested working on xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
$ juju bootstrap lxd --debug
..
18:25:50 DEBUG juju.cmd.juju.commands bootstrap.go:988 preparing controller
with config: map[https-proxy: no-proxy:127.0.0.1,localhost,::1
provisioner-harvest-mode:destroyed test-mode:false image-stream:released
apt-http-proxy: default-series:xenial ...
...
18:25:50 INFO cmd bootstrap.go:296 Looking for packaged Juju agent version
2.2.5 for amd64
...
18:25:52 DEBUG juju.environs.simplestreams simplestreams.go:683 using default
candidate for content id "com.ubuntu.juju:released:tools" are {20161007
mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
18:25:55 INFO juju.environs.bootstrap tools.go:74 found 15 packaged agent
binaries
...
18:25:55 DEBUG juju.provider.lxd environ_broker.go:40 StartInstance: "0", xenial
...
18:26:08 INFO juju.environs.bootstrap bootstrap.go:606 newest version: 2.2.5
18:26:08 INFO juju.environs.bootstrap bootstrap.go:621 picked bootstrap agent
binary version: 2.2.5
--
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
[Bug 1727355] Re: no matching agent binaries available with 2.2.5
For SRU purposes, you can verify this changed against juju via the
following:
juju bootstrap --debug lxd (or any provider you wish)
Confirm the following from the output:
1. Bootstrap completes successfully
2. Agent is used from stream
Look for something similar to:
juju.environs.bootstrap bootstrap.go:621 picked bootstrap agent binary version:
2.2.5
Fetching agent: curl -sSfw 'tools from %{url_effective} downloaded: HTTP
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz
<[https://streams.canonical.com/juju/tools/agent/2.2.5/juju-2.2.5-ubuntu-amd64.tgz]>
We don't want to see
juju.cmd.juju.commands bootstrap.go:496 failed to bootstrap model: no matching
agent binaries available
or a note about juju uploading it's own agent.
3. default-series in metadata is xenial
Look for default-series in the config map. All options will be listed, but
default-series is among them.
juju.cmd.juju.commands bootstrap.go:988 preparing controller with config:
map[image-metadata-url: ... default-series:xenial ...]
** Summary changed:
- no matching agent binaries available with 2.2.5
+ Juju attempts to bootstrap bionic by default
--
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
[Bug 1727355] Re: no matching agent binaries available with 2.2.5
** Changed in: juju Status: Triaged => In Progress ** Changed in: juju Status: In Progress => Fix Committed -- 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: no matching agent binaries available with 2.2.5 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
[Bug 1718213] Re: [SRU] Juju 2.2.4
The package works successfully, however, dh_install is missing a file required for bash completion. We should ensure this file is also copied to ensure bash completion continues to work for new installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718213 Title: [SRU] Juju 2.2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699354] Re: upgrade juju-mongodb3.2 to 3.2.15
We've been using and testing against this newer version in our CI for more than a month without seeing any issues. All normal juju operations work, and I can connect to the juju database as expected. I tested this on xenial and zesty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699354 Title: upgrade juju-mongodb3.2 to 3.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1699354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699354] Re: upgrade juju-mongodb3.2 to 3.2.15
** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699354 Title: upgrade juju-mongodb3.2 to 3.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1699354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718213] [NEW] [SRU] Juju 2.2.4
Public bug reported: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.0.3 https://launchpad.net/juju/+milestone/2.0.4 https://launchpad.net/juju/+milestone/2.1.0 https://launchpad.net/juju/+milestone/2.1.1 https://launchpad.net/juju/+milestone/2.1.2 https://launchpad.net/juju/+milestone/2.1.3 https://launchpad.net/juju/+milestone/2.2.0 https://launchpad.net/juju/+milestone/2.2.1 https://launchpad.net/juju/+milestone/2.2.2 https://launchpad.net/juju/+milestone/2.2.3 https://launchpad.net/juju/+milestone/2.2.4 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here: http://qa.jujucharms.com/releases/5729 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718213 Title: [SRU] Juju 2.2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
** Changed in: juju-core (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699354] Re: upgrade juju-mongodb3.2 to 3.2.15
Michael, these failed to build on some arches; so looks like they didn't move into proposed (we are always running proposed). Nevertheless, I've installed them now onto our xenial and zesty CI slaves so they will run through the slew of testing now. We'll monitor for regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699354 Title: upgrade juju-mongodb3.2 to 3.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1699354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1669507] Re: Remove juju-core from artful
** Summary changed: - Remove juju-core from zesty + Remove juju-core from artful ** Description changed: Juju is now releasing as a snap as the primary means of consumption. For those still needing a debian package the juju ppas will be maintained. However from a distro perspective, folks wanting juju should snap install juju rather than apt install juju. With that in mind, we won't - need the juju-core package in zesty. - - For upgrade purposes, is there a defined method of transitioning yet - from a deb to a snap? This would also potentially have bearing on the - current xenial package. + need the juju-core package in artful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669507 Title: Remove juju-core from artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1669507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
** Changed in: juju-core-1 (Ubuntu Xenial) Status: New => Fix Released ** Changed in: conjure-up (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624914] Re: juju fails to build on all 32bit architectures
** Changed in: juju-core (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624914 Title: juju fails to build on all 32bit architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1624914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646913] Re: [SRU] Juju 1.25.9
** Changed in: juju-core-1 (Ubuntu) Status: In Progress => Fix Released ** Changed in: juju-core (Ubuntu) Status: In Progress => Fix Released ** Changed in: juju-core-1 (Ubuntu) Status: Fix Released => Invalid ** Changed in: juju-core (Ubuntu) Status: Fix Released => Invalid ** Changed in: juju-core-1 (Ubuntu Xenial) Status: New => Invalid ** Changed in: juju-core-1 (Ubuntu Yakkety) Status: New => Invalid ** Changed in: juju-core (Ubuntu Trusty) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706071] [NEW] Hdparm
Public bug reported: Instaling subiquity package and running it results in this runtime error. 2017-07-24 15:00:05,407 subiquity:77 Starting SUbiquity v0.0.5 2017-07-24 15:00:05,407 subiquity:78 Arguments passed: ['/usr/bin/subiquity'] 2017-07-24 15:00:05,407 subiquitycore.utils:31 Checking environment for installer requirements... 2017-07-24 15:00:05,409 subiquitycore.utils:72 FAIL: /sbin/hdparm is not found on the filesystem Installing hdparm fixes the issue and allows installation to continue. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706071 Title: Hdparm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1706071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1669507] [NEW] Remove juju-core from zesty
Public bug reported: Juju is now releasing as a snap as the primary means of consumption. For those still needing a debian package the juju ppas will be maintained. However from a distro perspective, folks wanting juju should snap install juju rather than apt install juju. With that in mind, we won't need the juju-core package in zesty. For upgrade purposes, is there a defined method of transitioning yet from a deb to a snap? This would also potentially have bearing on the current xenial package. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669507 Title: Remove juju-core from zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1669507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574076] Re: juju package should suggest juju-1.25 not juju-core
The packages for X and Y need to retain this behavior. However, the zesty archive won't have juju-core or juju-1.25. ** Project changed: juju-reports => juju-release-tools ** Changed in: juju-release-tools Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574076 Title: juju package should suggest juju-1.25 not juju-core To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1574076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574076] Re: juju package should suggest juju-1.25 not juju-core
** Also affects: juju-reports Importance: Undecided Status: New ** Changed in: juju-reports Status: New => Triaged ** Changed in: juju-reports Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574076 Title: juju package should suggest juju-1.25 not juju-core To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1574076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613864] Re: Missing "juju-2"/"juju2" command.
This issue should be corrected now as of 2.1-beta5. There is a juju-2 symlink you can depend on that will point to the latest juju-2 binary on your system. ** Changed in: juju-core (Ubuntu) Status: Confirmed => Invalid ** Changed in: juju Status: Triaged => Invalid ** Changed in: juju-release-tools Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613864 Title: Missing "juju-2"/"juju2" command. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1613864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611078] Re: Support snaps inside of lxd containers
I can confirm this works on xenial after installing squashfuse. root@clean-lark:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial root@clean-lark:~# uname -a Linux clean-lark 4.4.0-63-generic #84-Ubuntu SMP Wed Feb 1 17:20:32 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@clean-lark:~# dpkg -l | grep -i 'apparmor\|snap\|squash' ii apparmor 2.10.95-0ubuntu2.5 amd64 user-space parser utility for AppArmor ii libapparmor-perl 2.10.95-0ubuntu2.5 amd64 AppArmor library Perl bindings ii libapparmor1:amd64 2.10.95-0ubuntu2.5 amd64 changehat AppArmor library ii snap-confine 2.21 amd64 Support executable to apply confinement for snappy apps ii snapd2.21 amd64 Tool to interact with Ubuntu Core Snappy. ii squashfs-tools 1:4.3-3ubuntu2 amd64 Tool to create and append to squashfs filesystems ii ubuntu-core-launcher 2.21 amd64 Launcher for ubuntu-core (snappy) apps root@clean-lark:~# snap list Name Version Rev Developer Notes core 16.04.1 888 canonical - hello-world 6.3 27 canonical - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611078 Title: Support snaps inside of lxd containers To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630789] Re: normal users can't run snaps inside of LXD containers
Yakkety still has 1.0.43. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630789 Title: normal users can't run snaps inside of LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1630789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648894] Re: [SRU] Juju 2.0.2
I have verified both xenial and yakkety functionality. In particular, I've been using this version on xenial for some time without realizing it hadn't yet been verified (I'm always running -proposed). I'll note the bash completion functionality is the same as the previous package, and doesn't contain the improvements found in 2.1. That will come of course with 2.1. ** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648894 Title: [SRU] Juju 2.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Milestone: None => 2.1-rc1 ** Changed in: juju Status: New => Triaged ** Changed in: juju Importance: Undecided => Critical ** Changed in: juju Assignee: (unassigned) => Menno Smits (menno.smits) ** Changed in: juju (Ubuntu) Status: New => Invalid ** Changed in: juju (Ubuntu) Assignee: Menno Smits (menno.smits) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1269163] Re: phablet-click-test-setup should support launchpad branches
** Changed in: phablet-tools Assignee: Nicholas Skaggs (nskaggs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269163 Title: phablet-click-test-setup should support launchpad branches To manage notifications about this bug go to: https://bugs.launchpad.net/phablet-tools/+bug/1269163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646913] Re: [SRU] Juju 1.25.8
** Description changed: - Juju 1.25.8 is a stable update containing critical bug fixes, for backup - restore, charm metrics, and mac os sierra for the 1.25 series. + Juju 1.25.8 is a stable update containing critical bug fixes including + backup restore, charm metrics, openstack security group removal, and mac + os sierra for the 1.25 series. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This update brings critical fixes and enhancements in comparison to the current 1.25.6 release. A full list of targeted bugs can be seen against the milestones: https://launchpad.net/juju-core/+milestone/1.25.7 https://launchpad.net/juju-core/+milestone/1.25.8 + https://launchpad.net/juju-core/+milestone/1.25.9 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/4572 In addition, juju has adt test coverage for all supported archs: http://autopkgtest.ubuntu.com/packages/j/juju-core/ http://autopkgtest.ubuntu.com/packages/j/juju-core-1/ Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Description changed: - Juju 1.25.8 is a stable update containing critical bug fixes including + Juju 1.25.9 is a stable update containing critical bug fixes including backup restore, charm metrics, openstack security group removal, and mac os sierra for the 1.25 series. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This update brings critical fixes and enhancements in comparison to the current 1.25.6 release. A full list of targeted bugs can be seen against the milestones: https://launchpad.net/juju-core/+milestone/1.25.7 https://launchpad.net/juju-core/+milestone/1.25.8 https://launchpad.net/juju-core/+milestone/1.25.9 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/4572 In addition, juju has adt test coverage for all supported archs: http://autopkgtest.ubuntu.com/packages/j/juju-core/ http://autopkgtest.ubuntu.com/packages/j/juju-core-1/ Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Summary changed: - [SRU] Juju 1.25.8 + [SRU] Juju 1.25.9 ** Changed in: juju-core (Ubuntu Xenial) Status: New => Invalid ** Changed in: juju-core (Ubuntu Yakkety) Status: New => Invalid ** Changed in: juju-core-1 (Ubuntu Trusty) Status: New => Invalid ** Changed in: juju-core (Ubuntu) Status: Confirmed => In Progress ** Changed in: juju-core-1 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648894] Re: [SRU] Juju 2.0.2
** Branch linked: lp:~juju-qa/ubuntu/xenial/juju/2.0.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648894 Title: [SRU] Juju 2.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648894] [NEW] [SRU] Juju 2.0.2
Public bug reported: This syncs juju with the upstream releases bringing the latest bugfixes. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/2.0/2.0.1 https://launchpad.net/juju/2.0/2.0.2 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/4568 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Description changed: This syncs juju with the upstream releases bringing the latest bugfixes. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/2.0/2.0.1 https://launchpad.net/juju/2.0/2.0.2 - In addition, this SRU unblocks zesty by building agents and binaries for - zesty. - [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/4568 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648894 Title: [SRU] Juju 2.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646913] Re: [SRU] Juju 1.25.8
** Branch linked: lp:~juju-qa/ubuntu/trusty/juju/juju-1.25.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646913] Re: [SRU] Juju 1.25.8
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646913] [NEW] [SRU] Juju 1.25.8
Public bug reported: Juju 1.25.8 is a stable update containing critical bug fixes, for backup restore, charm metrics, and mac os sierra for the 1.25 series. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This update brings critical fixes and enhancements in comparison to the current 1.25.6 release. A full list of targeted bugs can be seen against the milestones: https://launchpad.net/juju-core/+milestone/1.25.7 https://launchpad.net/juju-core/+milestone/1.25.8 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/4572 In addition, juju has adt test coverage for all supported archs: http://autopkgtest.ubuntu.com/packages/j/juju-core/ http://autopkgtest.ubuntu.com/packages/j/juju-core-1/ Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Affects: juju-core-1 (Ubuntu) Importance: Undecided Status: New ** Package changed: juju-core (Ubuntu) => juju-core-1 (Ubuntu) ** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
** Changed in: juju-release-tools Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
Just adding a comment to note that indeed on 32-bit arches both the install and upgrade show the DEBCONF message and remove all associated binaries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2 GA
** Tags removed: verification-needed ** Tags added: v-done-yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
Works properly for yakkety. juju.conf installed and values set properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
@Nicolas, /usr/lib/sysctl.d/ does override /etc/sysctl.conf. Note, these settings are already an increase from the default. These are lower values than in the wiki, but are deemed safe enough to deploy to all users. You should absolutely bump these values should you wish to run a more production environment. That wiki page suggest modifying /etc/sysctl.conf. I would suggest not modifying that file directly, and instead adding something to /usr/lib/sysctl.d/. We can also inform folks of the existence of this file so folks don't fall over. If you make changes to the values, indeed you no longer want the juju default settings used. Let's improve that page to help make these clear. Any other suggestions? I would expect someone wanting to set there own settings to modify or remove the juju.conf. ** Tags removed: verification-needed ** Tags added: v-done-yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
** Tags removed: verification-needed ** Tags added: v-done-xenial v-failed-yakkety ** Tags removed: v-failed-yakkety ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2 GA
** Tags removed: verification-done ** Tags added: v-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
Installing xenial build, I am no longer prompted on supported architectures. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2 GA
Xenial package installed and working as expected. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
** Changed in: juju-core (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: juju-core (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
** Description changed: The current juju packaging specifies all for architecture, but juju itself only officially supports 64-bit architectures. We should update - juju, conjure-up, charm, and charm-tools to specify to build on only - supported architectures for all ppa and archive versions. We should also - remove existing builds from xenial and yakkety that are for unsupported - architectures. + juju, to build on only supported architectures for all ppa and archive + versions. We should also remove existing builds from xenial that are for + unsupported architectures. + + [SRU Information] + + [Impact] + This change removes 32-bit builds of juju and replaces it with a debconf message instead. See https://lists.ubuntu.com/archives/ubuntu-release/2016-September/003882.html + + [Verification] + First confirm a supported arch install works without issue. No prompting should occur. + + Then, try the same on a 32-bit machine. All existing juju binaries and + files should be removed, and you should be prompted with the debconf + message about an unsupported client. + + [Regression Potential] + For 32-bit users, this is removing a binary package. However, beta15 package of juju2 isn't supported. For the supported arches, the only regression potential is seeing a needless debconf message. ** No longer affects: juju-core-1 (Ubuntu) ** No longer affects: conjure-up (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
Updating to say this works properly in xenial, but not in yakkety. Yakkety is missing the sysctl file; it's not installed. This needs to be corrected in the debian/rules. ** Tags removed: verification-needed ** Tags added: verification-done verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614559] Re: Juju rejects lxd 2.1
I am now able to bootstrap using LXD 2.0.5. juju bootstrap lxd lxd Creating Juju controller "lxd" on lxd/localhost Looking for packaged Juju agent version 2.0.0 for amd64 To configure your system to better support LXD containers, please see: https://github.com/lxc/lxd/blob/master/doc/production-setup.md Launching controller instance(s) on lxd/localhost... - juju-25d61c-0 (arch=amd64) ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614559 Title: Juju rejects lxd 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1614559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629376] Re: Juju should use bundled jujud if not matching agents found in streams
As per http://autopkgtest.ubuntu.com/packages/j/juju-core, the test was skipped and the autopkgtest suite succeeded. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629376 Title: Juju should use bundled jujud if not matching agents found in streams To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1629376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614724] Re: Juju isn't protected from new versions of LXD
Diff shows LXD is added, and we can see from yakkety and zesty the tests are running on new LXD uploads. https://launchpadlibrarian.net/290947340/juju- core_2.0~beta15-0ubuntu2.16.04.1_2.0.0-0ubuntu0.16.04.1.diff.gz ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614724 Title: Juju isn't protected from new versions of LXD To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614559] Re: Juju rejects lxd 2.1
** Description changed: Juju errors with: invalid config: lxd version 2.1, juju needs at least 2.0.0 As seen here: http://reports.vapour.ws/releases/issue/57b5c506749a567eabd11a4a Full log not given here because it contains certs. See above link for full logs. + + [SRU Information] + + [Impact] + The current juju packages don't allow for a newer lxd version than 2.0.0. This has been corrected instead to check the LXD API version. + + [Verification] + Install the archive version of LXD, and ensure it is LXD 2.1 or greater. You should be able to bootstrap with the local provider. + + juju bootstrap lxd lxd + + [Regression Potential] + As the local provider doesn't work now with LXD, there is no potential for further regressions on local provider specifically. However, there is inherent risk in the update itself that it fails to address the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614559 Title: Juju rejects lxd 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1614559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614724] Re: Juju isn't protected from new versions of LXD
** Description changed: Juju's autopkgtests don't execute when a new version of LXD is uploaded. This means a breaking change uploaded into LXD isn't caught before LXD lands. This is because juju 2.0 doesn't depend on LXD directly, but instead lists it as a recommends. The juju-1 package, juju-local, depends on lxc directly and therefore the autopkgtests run during each new lxc upload. However, we are vulnerable for 2.0. Juju's autopkgtests do cover LXD and would provide protection if they were run. To fix, we could list LXD as a depends on a package juju-core source package creates. This would run our tests and block incompatible LXD changes. Alternatively, we can explore ideas about checking proposed ourselves; however, the upload will not be blocked apart from a failing autopkgtest. + + + [SRU Information] + + [Impact] + The addition of a dependency of LXD ensure juju binaries can only be built on platforms that also can build LXD and publish a package. + + [Verification] + The debian control field lists LXD as a dependency. We should also see new adt runs of juju when LXD is uploaded. + + [Regression Potential] + None. + + [Other] + This should have no impact on end users of the package; the verification can be done by viewing juju-core source upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614724 Title: Juju isn't protected from new versions of LXD To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
** Description changed: In order to increase the number of containers that can be used with the lxd provider we need an /etc/sysctl.d/10-juju.conf file setting: - fs.inotify.max_user_watches = 524288 - fs.inotify.max_user_instances = 256 + fs.inotify.max_user_watches = 524288 + fs.inotify.max_user_instances = 256 This is a partial fix for bug #1602192. + + [SRU Information] + + [Impact] + This represent a partial workaround to the problem of being unable to launch double digit containers via LXD. While upstream work within the kernel and LXD should provide a better solution, this seeks to mitigate the specific case of running a charm bundle locally via LXD. + + [Verification] + Start 13 containers using lxc. Then perform a juju bootstrap and deploy the ubuntu charm. Using the old package, the deploy should never complete. With the changes, you should be able to deploy. NOTE: You will still hit an upper limit depending on your machine of around 20 or so containers. This test is intended to demonstrate you can deploy even with more than 13 running lxc containers. + + As an additional verification, you can attempt to deploy a large bundle + like canonical-kubernetes, hadoop, or another bigdata charm. Be sure to + remove any pre-existing containers before deploying as these bundles + will start more than a dozen on there own. + + [Regression Potential] + As these values are not currently set, there is no potential for regressions. Rather, the risk is on setting the values. + + [Other] + This change tweaks kernel settings that will change the users machine for all running binaries -- not just LXD and juju. These values have been chosen as reasonable defaults and as safe to implement. See the discussion on bug 1602192. ** Description changed: In order to increase the number of containers that can be used with the lxd provider we need an /etc/sysctl.d/10-juju.conf file setting: fs.inotify.max_user_watches = 524288 fs.inotify.max_user_instances = 256 This is a partial fix for bug #1602192. [SRU Information] [Impact] This represent a partial workaround to the problem of being unable to launch double digit containers via LXD. While upstream work within the kernel and LXD should provide a better solution, this seeks to mitigate the specific case of running a charm bundle locally via LXD. [Verification] - Start 13 containers using lxc. Then perform a juju bootstrap and deploy the ubuntu charm. Using the old package, the deploy should never complete. With the changes, you should be able to deploy. NOTE: You will still hit an upper limit depending on your machine of around 20 or so containers. This test is intended to demonstrate you can deploy even with more than 13 running lxc containers. + First confirm the values are now set by checking with + + sysctl -a | grep fs.inotify.max_user_ + + Then, try running a bunch of lxc containers. You should be able to start + around 20 before they fail. + + To test juju, start 13 containers using lxc. Then perform a juju + bootstrap and deploy the ubuntu charm. Using the old package, the deploy + should never complete. With the changes, you should be able to deploy. + NOTE: You will still hit an upper limit depending on your machine of + around 20 or so containers. This test is intended to demonstrate you can + deploy even with more than 13 running lxc containers. As an additional verification, you can attempt to deploy a large bundle like canonical-kubernetes, hadoop, or another bigdata charm. Be sure to remove any pre-existing containers before deploying as these bundles will start more than a dozen on there own. [Regression Potential] As these values are not currently set, there is no potential for regressions. Rather, the risk is on setting the values. [Other] This change tweaks kernel settings that will change the users machine for all running binaries -- not just LXD and juju. These values have been chosen as reasonable defaults and as safe to implement. See the discussion on bug 1602192. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629376] Re: Juju should use bundled jujud if not matching agents found in streams
** Description changed:
Since --upload-tools is now no longer needed, juju needs to fallback to
using bundled jujud in the case where no matching agents are found in
streams. For example,
6:38:07 INFO juju.environs.manual init.go:120 series: zakkety,
characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
16:38:07 INFO cmd cmd.go:129 Looking for packaged Juju agent version
2.0-beta18 for amd64
...
16:38:08 INFO juju.environs.bootstrap tools.go:74 found 15 packaged agent
binaries
..
16:38:08 ERROR cmd supercommand.go:458 failed to bootstrap model: no matching
tools available
16:38:08 DEBUG cmd supercommand.go:459 (error details:
[{github.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap
model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
In this example, beta18 is a released version, and 15 agents are found.
However, none of them match my crazy series. Juju should still use the
bundled agent automatically. Note, passing --build-agent requires me to
rebuild an agent in this case; not something I can/should need to do on
a client machine.
+
+ [SRU Information]
+
+ [Impact]
+ The autopkgtest for future-manual-provider ensuring juju works with the next
release before a juju update will be disabled per the bug.
+
+ [Verification]
+ The autopkgtest future-manual-provider should now be skipped with
+ SKIP: Juju won't bootstrap unknown without published agent (LP:1629376)
** Description changed:
Since --upload-tools is now no longer needed, juju needs to fallback to
using bundled jujud in the case where no matching agents are found in
streams. For example,
6:38:07 INFO juju.environs.manual init.go:120 series: zakkety,
characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
16:38:07 INFO cmd cmd.go:129 Looking for packaged Juju agent version
2.0-beta18 for amd64
...
16:38:08 INFO juju.environs.bootstrap tools.go:74 found 15 packaged agent
binaries
..
16:38:08 ERROR cmd supercommand.go:458 failed to bootstrap model: no matching
tools available
16:38:08 DEBUG cmd supercommand.go:459 (error details:
[{github.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap
model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
In this example, beta18 is a released version, and 15 agents are found.
However, none of them match my crazy series. Juju should still use the
bundled agent automatically. Note, passing --build-agent requires me to
rebuild an agent in this case; not something I can/should need to do on
a client machine.
[SRU Information]
[Impact]
The autopkgtest for future-manual-provider ensuring juju works with the next
release before a juju update will be disabled per the bug.
[Verification]
The autopkgtest future-manual-provider should now be skipped with
SKIP: Juju won't bootstrap unknown without published agent (LP:1629376)
+
+ [Regression Potential]
+ None. The package won't make it out of proposed, as the test will currently
fail as-is.
+
+ [Other]
+ This should have no impact on end users of the package; the verification can
be done by viewing the test results under
http://autopkgtest.ubuntu.com/packages/j/juju-core/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629376
Title:
Juju should use bundled jujud if not matching agents found in streams
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1629376/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614724] Re: Juju isn't protected from new versions of LXD
** Changed in: juju-core (Ubuntu Yakkety) Status: In Progress => Fix Released ** Changed in: juju-core (Ubuntu Yakkety) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) ** Changed in: juju-core (Ubuntu Xenial) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614724 Title: Juju isn't protected from new versions of LXD To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614559] Re: Juju rejects lxd 2.1
** Changed in: juju-core (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: juju-core (Ubuntu Xenial) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614559 Title: Juju rejects lxd 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1614559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631038] Re: Need /etc/sysctl.d/10-juju.conf
** Changed in: juju-core (Ubuntu Zesty) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) ** Changed in: juju-core (Ubuntu Yakkety) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) ** Changed in: juju-core (Ubuntu Xenial) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629376] Re: Juju should use bundled jujud if not matching agents found in streams
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Status: New => In Progress ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629376 Title: Juju should use bundled jujud if not matching agents found in streams To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1629376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2 GA
** Summary changed: - [SRU] Juju 2-rc3 for Xenial + [SRU] Juju 2 GA ** Description changed: - Juju 2.0 is not quite final, as per the risks and timeline outlined in - the FFe for Xenial, bug 1545913. As such, we intend to release SRU's - post-xenial release. This updates juju to an upgradeable RC which is - usable for production deployments. + Juju 2.0 is now final! This upgrades juju to the GA release. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This update fixes the LXD regression affecting juju in xenial: bug 1614559. - It also removes 32-bit packages and provides a debconf notice upon installation or upgrade. See https://lists.ubuntu.com/archives/ubuntu-release/2016-September/003882.html . + It also removes 32-bit packages and provides a debconf notice upon installation or upgrade. See https://lists.ubuntu.com/archives/ubuntu-release/2016-September/003882.html. Finally it adds a sysctl config to help the lxd provider: bug 1631038. In addition, numerous bug fixes have occurred bringing juju up to - production readiness. This release can be upgraded to 2.0 GA which will - release shortly. + production readiness. A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/2.0/2.0-beta16 https://launchpad.net/juju/2.0/2.0-beta17 https://launchpad.net/juju/2.0/2.0-beta18 https://launchpad.net/juju/2.0/2.0-rc1 https://launchpad.net/juju/2.0/2.0-rc2 https://launchpad.net/juju/2.0/2.0-rc3 + https://launchpad.net/juju/2.0/2.0.0 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. - http://reports.vapour.ws/releases/4456 + http://reports.vapour.ws/releases/4486 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. - Specific to this package, the current test suite passes within our test - infrastructure, as well as within yakkety. - Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2-rc3 for Xenial
** Description changed: Juju 2.0 is not quite final, as per the risks and timeline outlined in the FFe for Xenial, bug 1545913. As such, we intend to release SRU's - post-xenial release. This updates juju to the lastest 2.0 milestone - version. + post-xenial release. This updates juju to an upgradeable RC which is + usable for production deployments. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] - This update brings many critical fixes and enhancements in comparison to the current beta15 release. + This update fixes the LXD regression affecting juju in xenial: bug 1614559. + It also removes 32-bit packages and provides a debconf notice upon installation or upgrade. See https://lists.ubuntu.com/archives/ubuntu-release/2016-September/003882.html . + + In addition, numerous bug fixes have occurred bringing juju up to + production readiness. This release can be upgraded to 2.0 GA which will + release shortly. A full list of targeted bugs can be seen against the milestone, and the intervening milestones: - https://launchpad.net/juju-core/+milestone/2.0-beta16 - https://launchpad.net/juju-core/+milestone/2.0-beta17 - - Most importantly, the LXD regression affecting juju in xenial is fixed: - bug 1614559 + https://launchpad.net/juju/2.0/2.0-beta16 + https://launchpad.net/juju/2.0/2.0-beta17 + https://launchpad.net/juju/2.0/2.0-beta18 + https://launchpad.net/juju/2.0/2.0-rc1 + https://launchpad.net/juju/2.0/2.0-rc2 + https://launchpad.net/juju/2.0/2.0-rc3 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. - http://reports.vapour.ws/releases/4338 + http://reports.vapour.ws/releases/4456 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. + Specific to this package, the current test suite passes within our test + infrastructure, as well as within yakkety. + Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2-rc3 for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2-rc3 for Xenial
** Summary changed: - [SRU] Juju 2 beta 17 for Xenial + [SRU] Juju 2-rc3 for Xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2-rc3 for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613845] Re: Juju snap can no longer interact with LXD in devmode
1.0.41 was backported which has the fix. This should be released. ** Changed in: snap-confine (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613845 Title: Juju snap can no longer interact with LXD in devmode To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1613845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614724] Re: Juju isn't protected from new versions of LXD
** Changed in: juju-release-tools Status: In Progress => Fix Released ** Changed in: juju-core (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614724 Title: Juju isn't protected from new versions of LXD To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629412] [NEW] Please merge debian version of golang-golang-x-crypto-dev
Public bug reported: The current ubuntu (xenial / yakkety) packages are missing needed updates. Specifically, juju needs golang.org/x/crypto/acme/autocert. I can note that sid contains these updated packages, but yakkety is still missing them. See https://packages.debian.org/sid/all/golang- golang-x-crypto-dev/filelist. ** Affects: golang-go.crypto (Ubuntu) Importance: Undecided Status: New ** Tags: needs-debian-merge ** Tags added: needs-debian-merge ** Summary changed: - golang-golang-x-crypto-dev missing acme/autocert + Please merge debian version of golang-golang-x-crypto-dev ** Description changed: - The current xenial package is missing needed updates. I can note that - sid contains these updated packages, but yakkety is still missing them. - See https://packages.debian.org/sid/all/golang-golang-x-crypto- - dev/filelist. + The current ubuntu (xenial / yakkety) packages are missing needed + updates. Specifically, juju needs golang.org/x/crypto/acme/autocert. - We need golang.org/x/crypto/acme/autocert. + I can note that sid contains these updated packages, but yakkety is + still missing them. See https://packages.debian.org/sid/all/golang- + golang-x-crypto-dev/filelist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629412 Title: Please merge debian version of golang-golang-x-crypto-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-go.crypto/+bug/1629412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617433] Re: [FFe] juju 2.0
** Description changed: The juju team is requesting an FFE for juju. Juju-2 represents API changes and new features and bugfixes for juju. This FFE is intended to cover the acceptance of the updated juju package. Timeline - We have released 16 betas of juju-2 so far over the xenial and now yakkety release cycles. We anticipate releasing an RC in September, with the final to follow closely after. We expect it to be ready before yakkety would release. + We have released 18 betas and 2 rc's of juju-2 so far over the xenial and now yakkety release cycles. We anticipate the final version to release on the same day as yakkety. We plan to do a soon after release SRU to bring the final version in. These RC versions are upgradable to 2.0 final, and can be considered usable for production deployments. Upgrades Users coming from xenial have the same style packaging in place for juju-1 and juju-2. Juju 2 owns /usr/bin/juju, but juju-1 may divert this via the juju-1-default package. Risks - - Should more features be deemed necessary before 2.0 releases, or if critical bugs are found it's possible juju-2.0 may not be final before yakkety releases. + Juju 2.0 plans to release it's final version the same day as yakkety. We will need to SRU this into yakkety. Quality / Testing - - We've continued our testing and bugfixing all throughout yakkety cycle. Juju itself practices continous integration and testing of the juju source tree. All voting tests must pass for ubuntu before our final release. See http://reports.vapour.ws/releases/. + We've continued our testing and bugfixing all throughout yakkety cycle. Juju itself practices continuous integration and testing of the juju source tree. All voting tests must pass for ubuntu before our final release. See http://reports.vapour.ws/releases/4438 for the CI test run that corresponds to rc2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617433 Title: [FFe] juju 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1617433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612116] Re: please remove juju-core-1 and juju-mongodb packages from yakkety
Given juju2 is now RC and has promises of being upgradeable, I think this is safe to move forward on. For folks who have to have it, it will be in the stable juju ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612116 Title: please remove juju-core-1 and juju-mongodb packages from yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core-1/+bug/1612116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578550] Re: ftbfs on yakkety
** Changed in: juju-core (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578550 Title: ftbfs on yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1578550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605976] Re: [2.0] bump mongod to 3.2.9
@mwhudson, I utilized the tool locally and everything seemed fine. For now, bug 1564500 prevents a full CI run until it lands in xenial proper. I think we should discuss a set of autopkgtests to help bridge the gap in the interim. That said, given 3.2.9 is in yakkety we've not seen any issues in the CI runs that occur within yakkety which I consider a useful datapoint in this case. It's been running for a couple weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605976 Title: [2.0] bump mongod to 3.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605976] Re: [2.0] bump mongod to 3.2.9
Looks good. /usr/lib/juju/mongo3.2/bin/mongo MongoDB shell version: 3.2.9 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605976 Title: [2.0] bump mongod to 3.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484132] Re: [FFe] juju-core 1.25
** Changed in: juju-core (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484132 Title: [FFe] juju-core 1.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1484132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
** No longer affects: charm-tools (Ubuntu) ** No longer affects: charm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614559] Re: Juju rejects lxd 2.1
Martin, the edge channel in the snap store has replaced the daily ppa. This ppa is where we release betas: https://launchpad.net/~juju/+archive/ubuntu/devel Now as to landing this fix, we've pushed packages to proposed as you've seen, but encountered various failures with beta16 and now beta17. The blocker for beta17 landing is yet another iteration on juju failing to build on 32-bit arches. We don't support them and don't build them. IMHO, they never should have been built and uploaded to the archive. We worked around the issue for beta16, but can no longer do so for beta17. As it stands we must resolve bug 1614969. In short, we want to remove all 32-bit builds of the juju package from the archives. They are unsupported and prevent us from landing updates as desired. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614559 Title: Juju rejects lxd 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1614559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] Re: [SRU] Juju 2 beta 17 for Xenial
** Summary changed: - [SRU] Juju 2 beta 16 for Xenial + [SRU] Juju 2 beta 17 for Xenial ** Description changed: Juju 2.0 is not quite final, as per the risks and timeline outlined in the FFe for Xenial, bug 1545913. As such, we intend to release SRU's post-xenial release. This updates juju to the lastest 2.0 milestone version. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This update brings many critical fixes and enhancements in comparison to the current beta15 release. A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju-core/+milestone/2.0-beta16 + https://launchpad.net/juju-core/+milestone/2.0-beta17 Most importantly, the LXD regression affecting juju in xenial is fixed: bug 1614559 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. - http://reports.vapour.ws/releases/4304 + http://reports.vapour.ws/releases/4338 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2 beta 17 for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617440] [NEW] [SRU] Juju 2 beta 16 for Xenial
Public bug reported: Juju 2.0 is not quite final, as per the risks and timeline outlined in the FFe for Xenial, bug 1545913. As such, we intend to release SRU's post-xenial release. This updates juju to the lastest 2.0 milestone version. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This update brings many critical fixes and enhancements in comparison to the current beta15 release. A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju-core/+milestone/2.0-beta16 Most importantly, the LXD regression affecting juju in xenial is fixed: bug 1614559 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/4304 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617440 Title: [SRU] Juju 2 beta 16 for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1617440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614724] Re: Juju isn't protected from new versions of LXD
** Changed in: juju-release-tools Status: Triaged => In Progress ** Changed in: juju-core (Ubuntu) Status: New => In Progress ** Changed in: juju-release-tools Assignee: (unassigned) => Nicholas Skaggs (nskaggs) ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) => Nicholas Skaggs (nskaggs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614724 Title: Juju isn't protected from new versions of LXD To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617433] [NEW] [FFe] juju 2.0
Public bug reported: The juju team is requesting an FFE for juju. Juju-2 represents API changes and new features and bugfixes for juju. This FFE is intended to cover the acceptance of the updated juju package. Timeline We have released 16 betas of juju-2 so far over the xenial and now yakkety release cycles. We anticipate releasing an RC in September, with the final to follow closely after. We expect it to be ready before yakkety would release. Upgrades Users coming from xenial have the same style packaging in place for juju-1 and juju-2. Juju 2 owns /usr/bin/juju, but juju-1 may divert this via the juju-1-default package. Risks - Should more features be deemed necessary before 2.0 releases, or if critical bugs are found it's possible juju-2.0 may not be final before yakkety releases. Quality / Testing - We've continued our testing and bugfixing all throughout yakkety cycle. Juju itself practices continous integration and testing of the juju source tree. All voting tests must pass for ubuntu before our final release. See http://reports.vapour.ws/releases/. ** Affects: juju (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617433 Title: [FFe] juju 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1617433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605976] Re: [2.0] bump mongod to 3.2.8
@mwhudson, once mongo3.2.8 is in the proposed queue for xenial, we can ensure a CI test run or two before landing. Let us know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605976 Title: [2.0] bump mongod to 3.2.8 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
