[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1766415 Title: [SRU] Juju 2.3.7 Status in juju-core package in Ubuntu: Fix Released Status in juju-core source package in Xenial: Fix Released Bug description: 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] 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 [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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1766415/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Invalid Status in OPNFV: Fix Committed Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 Status in juju-core package in Ubuntu: In Progress Status in nplan package in Ubuntu: In Progress Status in juju-core source package in Xenial: In Progress Status in nplan source package in Xenial: In Progress Status in juju-core source package in Artful: Invalid Status in nplan source package in Artful: In Progress Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 Status in juju-core package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in juju-core source package in Xenial: Fix Released Status in nplan source package in Xenial: In Progress Status in juju-core source package in Artful: Invalid Status in nplan source package in Artful: In Progress Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1583740] Re: mongo client is missing
** Also affects: trusty-backports Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1583740 Title: mongo client is missing Status in trusty-backports: New Status in juju-mongodb3.2 package in Ubuntu: Fix Released Status in juju-mongodb3.2 source package in Xenial: New Bug description: Admins and developers are unable to access to the juju mongodb instance to investigation issues. The mongo client is built, but not included in the juju-mongodb3.2 package. Juju doesn't need it. Users who need to investigate db issues need to locate and install a third-party binary. This issue affects both yakkety an xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1583740/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1611855] Re: [SRU] Juju 1.25.6
** Changed in: juju-core-1 (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: juju-core (Ubuntu) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1611855 Title: [SRU] Juju 1.25.6 Status in juju-core package in Ubuntu: Fix Committed Status in juju-core-1 package in Ubuntu: Fix Committed Status in juju-core source package in Trusty: Fix Committed Status in juju-core-1 source package in Trusty: Invalid Status in juju-core source package in Xenial: Invalid Status in juju-core-1 source package in Xenial: Fix Committed Bug description: Juju 1.25.6 is a stable update containing critical bug fixes, including MAAS compatibility, 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.5 release. A full list of targeted bugs can be seen against the milestone: https://launchpad.net/juju-core/+milestone/1.25.6 [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/4134 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1611855/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.9 Status in juju-core package in Ubuntu: Invalid Status in juju-core-1 package in Ubuntu: Invalid Status in juju-core source package in Trusty: Invalid Status in juju-core-1 source package in Trusty: Invalid Status in juju-core source package in Xenial: Invalid Status in juju-core-1 source package in Xenial: Invalid Status in juju-core source package in Yakkety: Invalid Status in juju-core-1 source package in Yakkety: Invalid Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures Status in juju-release-tools: Fix Released Status in juju-core package in Ubuntu: Fix Committed Status in conjure-up source package in Xenial: Fix Released Status in juju-core source package in Xenial: Fix Released Status in juju-core-1 source package in Xenial: Fix Released Bug description: The current juju packaging specifies all for architecture, but juju itself only officially supports 64-bit architectures. We should update 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. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures Status in juju-release-tools: Fix Released Status in juju-core package in Ubuntu: Fix Released Status in conjure-up source package in Xenial: Fix Released Status in juju-core source package in Xenial: Fix Released Status in juju-core-1 source package in Xenial: Fix Released Bug description: The current juju packaging specifies all for architecture, but juju itself only officially supports 64-bit architectures. We should update 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. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1613845 Title: Juju snap can no longer interact with LXD in devmode Status in Snappy Launcher: Fix Released Status in snap-confine package in Ubuntu: Fix Released Status in snap-confine source package in Xenial: Fix Released Bug description: [Impact] Snaps running in devmode cannot interact with LXD installed in the classic distribution. This happens because the chroot in which all snaps execute there is no /var/lib/lxd directory (it is not a part of the core snap). That directory doesn't exist so it cannot be bind-mounted from the classic distribution. Without access to this directory there's no way to access the lxd socket located inside. This bug is fixed by adding a quirk system where snap-confine can mount tmpfs over /var/lib and populate that tmpfs with a forest of bind mounts to the contents of /var/lib in the core snap. This leaves us with a tmpfs, not a read only squashfs so /var/lib/lxd can be now created and bind mounted on demand. For more information about the execution environment, please see this article http://www.zygoon.pl/2016/08/snap-execution-environment.html [Test Case] The test case can be found here: https://github.com/snapcore/snap-confine/blob/master/spread- tests/regression/lp-1613845/task.yaml The test case is ran automatically for each pull request and for each final release. It can be reproduced manually by executing the shell commands listed in the prepare/execute/restore phases manually. The commands there assume that snapd and snap-confine are installed. No other additional setup is necessary. [Regression Potential] * Regression potential is small but the code change is more invasive so careful review and testing is recommended. The way this feature operates may interact with the namespace sharing feature that is introduced in 1.0.41. As a known limitation (namespace sharing is not yet finalised and will be extended to support live mutation in subsequent releases) if the /var/lib/lxd directory does *not* exist on the classic distribution before a snap that wishes to use it is first started it will not be able to see the directory until the machine is re-started. In subsequent releases of snap-confine, snapd and snap-confine will collaborate to modify existing namespaces in reaction to changes in the mount configuration profile. At that time we can also investigate if quirks need to be adjusted in response to changes in the system. * The fix was tested on Ubuntu via spread. [Other Info] * This bug is a part of a major SRU that brings snap-confine in Ubuntu 16.04 in line with the current upstream release 1.0.41. * snap-confine is technically an integral part of snapd which has an SRU exception and is allowed to introduce new features and take advantage of accelerated procedure. For more information see https://wiki.ubuntu.com/SnapdUpdates == # Pre-SRU bug description follows # == The juju snap package can no longer use LXD as a substrate, presumably because of changes to bind mounts. To replicate, assuming you have LXD installed and configured: snap install juju --beta --devmode /snap/bin/juju bootstrap lxd lxd This command should complete successfully and did work until recently. Now, instead you get; ERROR invalid config: can't connect to the local LXD server: LXD socket not found; is LXD installed & running? Please install LXD by running: $ sudo apt-get install lxd and then configure it with: $ newgrp lxd $ lxd init To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1613845/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614724 Title: Juju isn't protected from new versions of LXD Status in juju-release-tools: Fix Released Status in juju-core package in Ubuntu: Fix Released Status in juju-core source package in Xenial: In Progress Status in juju-core source package in Yakkety: Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614724/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures Status in juju-release-tools: Fix Released Status in juju-core package in Ubuntu: New Status in conjure-up source package in Xenial: New Status in juju-core source package in Xenial: New Status in juju-core-1 source package in Xenial: New Bug description: The current juju packaging specifies all for architecture, but juju itself only officially supports 64-bit architectures. We should update 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. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1631038 Title: Need /etc/sysctl.d/10-juju.conf Status in juju-release-tools: Fix Released Status in juju-core package in Ubuntu: Fix Released Status in juju-core source package in Xenial: Fix Released Status in juju-core source package in Yakkety: Fix Released Status in juju-core source package in Zesty: Fix Released Bug description: 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] 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. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1631038/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1646913 Title: [SRU] Juju 1.25.9 Status in juju-core package in Ubuntu: In Progress Status in juju-core-1 package in Ubuntu: In Progress Status in juju-core source package in Trusty: New Status in juju-core-1 source package in Trusty: Invalid Status in juju-core source package in Xenial: Invalid Status in juju-core-1 source package in Xenial: New Status in juju-core source package in Yakkety: Invalid Status in juju-core-1 source package in Yakkety: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1646913/+subscriptions ___
[Group.of.nepali.translators] [Bug 1568148] Re: Juju packaging for xenial must depend on everything in the archive
** Changed in: juju-core (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: juju-core (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1568148 Title: Juju packaging for xenial must depend on everything in the archive Status in juju-core package in Ubuntu: Fix Released Status in juju-core source package in Xenial: Fix Released Bug description: As part of acceptance into main for juju2, we need to ensure our package depends on everything we can that is already in the archive. See bug 1545913 for the FFe. This bug will track our dependencies to ensure we meet this requirement. In archive: golang-github-azure-azure-sdk-for-go-dev golang-github-bmizerany-pat-dev golang-github-coreos-go-systemd-dev golang-go-dbus-dev golang-websocket-dev golang-github-julienschmidt-httprouter-dev golang-github-lxc-lxd-dev golang-golang-x-crypto-dev golang-golang-x-net-dev golang-golang-x-oauth2-dev golang-google-api-dev golang-github-adroll-goamz-dev golang-check.v1-dev golang-gopkg-ini.v1-dev golang-gopkg-mgo.v2-dev golang-github-natefinch-lumberjack-dev golang-goyaml-dev golang-yaml.v2-dev golang-gopkg-lxc-go-lxc.v2 golang-gopkg-tomb.v2-dev golang-juju-loggo-dev Packages in Main: golang-github-bmizerany-pat-dev golang-github-coreos-go-systemd-dev golang-go-dbus-dev golang-websocket-dev golang-github-lxc-lxd-dev golang-golang-x-crypto-dev golang-golang-x-net-dev golang-check.v1-dev golang-yaml.v2-dev golang-gopkg-lxc-go-lxc.v2 golang-gopkg-tomb.v2-dev golang-juju-loggo-dev MIRs: golang-github-azure-azure-sdk-for-go-dev bug 1568164 golang-github-julienschmidt-httprouter-dev golang-golang-x-oauth2-dev bug 1568165 golang-google-api-dev bug 1568163 golang-github-adroll-goamz-dev golang-gopkg-ini.v1-dev golang-gopkg-mgo.v2-dev bug 1568162 golang-github-natefinch-lumberjack-dev bug 1568168 golang-goyaml-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1568148/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
Status in juju:
Fix Released
Status in distro-info-data package in Ubuntu:
Won't Fix
Status in juju-core package in Ubuntu:
Invalid
Status in distro-info-data source package in Trusty:
Won't Fix
Status in juju-core source package in Trusty:
Invalid
Status in distro-info-data source package in Xenial:
In Progress
Status in juju-core source package in Xenial:
In Progress
Status in distro-info-data source package in Zesty:
In Progress
Status in juju-core source package in Zesty:
In Progress
Status in distro-info-data source package in Artful:
Won't Fix
Status in juju-core source package in Artful:
Invalid
Bug description:
This is with 2.2.5 on xenial, with x86 hosts:
I'm hitting this everytime I try to bootstrap:
14:01:42 DEBUG juju.cmd.juju.commands bootstrap.go:497 (error details:
[{github.com/juju/juju/cmd/juju/commands/bootstrap.go:588: failed to
bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching
agent binaries available}])
Full error:
http://paste.ubuntu.com/25817026/
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
