[Bug 1758980] Re: Enabling LIvePatch fails
The snap with the fix has been released on the edge channel. ** Changed in: canonical-livepatch-client 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/1758980 Title: Enabling LIvePatch fails To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1758980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758980] Re: Enabling LIvePatch fails
https://github.com/CanonicalLtd/livepatch-client/pull/56 ** Changed in: canonical-livepatch-client 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/1758980 Title: Enabling LIvePatch fails To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1758980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758980] Re: Enabling LIvePatch fails
** Changed in: canonical-livepatch-client 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/1758980 Title: Enabling LIvePatch fails To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1758980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560512] [NEW] Please remove juju-quickstart from xenial
Public bug reported: Juju Quickstart is deprecated and replaced by Juju 2.0 automatic credentials gathering and native bundle support. We are no longer actively developing quickstart and therefore we ask for the package to be not included in xenial. Thanks. ** Affects: juju-quickstart (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/1560512 Title: Please remove juju-quickstart from xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1560512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325013] Re: juju-quickstart has no dep8 tests so can break when juju-core changes
Quickstart 2.0 includes functional tests. In order to run them, some pre-requisites must be satisfied. See http://bazaar.launchpad.net/~juju-gui/juju-quickstart/trunk/view/head:/HACKING.rst#L70 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325013 Title: juju-quickstart has no dep8 tests so can break when juju-core changes To manage notifications about this bug go to: https://bugs.launchpad.net/juju-quickstart/+bug/1325013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408280] Re: juju-quickstart fails with SSL verification errors
If I understand this correctly, this seems to be an issue related to a backward incompatible change in the Python websocket client library. Its API changed in version 1.13, trusty has 1.12, vivid updated to 1.18 [1]. Basically they introduced SSL certs validation by default [2]. Quickstart reacted to this change in [3], assuming 1.18 was going to be included in utopic. Note that the Juju stable PPA includes version 1.18 for all supported series [4]. The quickstart update was released as version 1.4.3, and that would explain why you are encountering that failure with 1.4.2 on vivid. That said, I think we need to include a newer Quickstart version in vivid. I am not sure about 1.4.2 working on older Juju versions: if the above is correct this is a client issue not affecting juju-core itself. [1] http://packages.ubuntu.com/search?keywords=python-websocket&searchon=names&suite=all§ion=all [2] https://github.com/liris/websocket-client/pull/56 [3] http://bazaar.launchpad.net/~juju-gui/juju-quickstart/trunk/revision/98 [4] https://launchpad.net/~juju/+archive/ubuntu/stable/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408280 Title: juju-quickstart fails with SSL verification errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1408280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408280] Re: juju-quickstart fails with SSL verification errors
I am marking this bug as invalid, since (if I am correct) newer versions of quickstart already fixed this bug: PPA users have been using python- websocket 1.18 and quickstart for quite a while now. Please feel free to reopen this if I am missing something. ** Changed in: juju-quickstart (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/1408280 Title: juju-quickstart fails with SSL verification errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1408280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359938] Re: [FFE] request to update juju-quickstart to support JUJU env var
I forgot to mention that juju-quickstart is in universe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359938 Title: [FFE] request to update juju-quickstart to support JUJU env var To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1359938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359944] Re: [FFE] Update juju-quickstart to support MAAS as a configurable provider
Please also note that juju-quickstart is in unverse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359944 Title: [FFE] Update juju-quickstart to support MAAS as a configurable provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1359944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359938] Re: [FFE] request to update juju-quickstart to support JUJU env var
The changes has been made and released on PyPI (version 1.4.3): https://pypi.python.org/pypi/juju-quickstart/1.4.3 Quickstart now supports overriding the juju executable being invoked via the JUJU env var. This is only allowed on recent juju versions, not requiring sudo to be called on "juju bootstrap" when using local environments (LXC). This feature helps testing quickstart with development versions of Juju, making releases more reliable and future proof. The 1.4.3 release also bumps the requirements versions up, to align to what we expect to be included in utopic. The feature is properly tested (quickstart still have 100% unit tests coverage). Here is the full changelog: juju-quickstart (1.4.3) trusty; urgency=low * Support for overriding the Juju executable with the JUJU env var. * Add support for Ubuntu 14.10 (utopic). * Base dependencies update. -- Francesco Banconi Thu, 11 Sep 2014 11:57:47 + I am available for any help or clarification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359938 Title: [FFE] request to update juju-quickstart to support JUJU env var To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1359938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359944] Re: [FFE] Update juju-quickstart to support MAAS as a configurable provider
The changes has been made and released on PyPI (version 1.4.4): https://pypi.python.org/pypi/juju-quickstart/1.4.4 Quickstart now supports creating and managing MAAS environments: this allows MAAS users to quickly configure and bootstrap an environment on MAAS, including the Juju GUI deployed on the bootstrap node, with automatic login and bundle deployment support. This completes the quickstart offer in terms of supported providers: we need MAAS to be a first class provider along with ec2, amazon, hp cloud and all the other provider types supported by quickstart. This did not require any change in the list of dependencies. The feature is properly tested (both unit tests and live tests in a real MAAS controller). Here is the changelog since 1.4.2: juju-quickstart (1.4.4) trusty; urgency=low * Support creating and using MAAS (Metal As A Service) environments. -- Francesco Banconi Wed, 01 Oct 2014 15:38:32 + juju-quickstart (1.4.3) trusty; urgency=low * Support for overriding the Juju executable with the JUJU env var. * Add support for Ubuntu 14.10 (utopic). * Base dependencies update. -- Francesco Banconi Thu, 11 Sep 2014 11:57:47 + We opened bug 1359938 in order to handle version 1.4.3. I am available for any help or clarification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359944 Title: [FFE] Update juju-quickstart to support MAAS as a configurable provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1359944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301464] Re: The mega-watcher for machines does not include containers addresses
** Changed in: juju-quickstart (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301464 Title: The mega-watcher for machines does not include containers addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1301464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301464] Re: The mega-watcher for machines does not include containers addresses
** Changed in: juju-quickstart (Ubuntu) Status: Triaged => 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/1301464 Title: The mega-watcher for machines does not include containers addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1301464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301464] Re: The mega-watcher for machines does not include containers addresses
I attached a prototype for a possible fix. It seems to work, containers addresses are now included in the mega-watcher for machines. The only issue, even after applying that patch, is that the NetworkScope for LXC addresses is an empty string, while I expected it to be "public", e.g.: {u'Addresses': [{u'NetworkName': u'', u'NetworkScope': u'', u'Type': u'ipv4', u'Value': u'10.0.3.133'}, {u'NetworkName': u'', u'NetworkScope': u'', u'Type': u'ipv6', u'Value': u'fe80::216:3eff:fece:7fdd'}], ** Attachment added: "diff" https://bugs.launchpad.net/juju-core/+bug/1301464/+attachment/4061109/+files/diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301464 Title: The mega-watcher for machines does not include containers addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1301464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282630] Re: [FFe] Upgrade juju-quickstart to new upstream release 1.3.0
** Summary changed: - [FFe] Upgrade juju-quickstart to new upstream release 1.2.0 + [FFe] Upgrade juju-quickstart to new upstream release 1.3.0 ** Description changed: We just released on PyPi the new 1.2.0 release of quickstart. Juju core 1.17.2 introduced sudo support for local environments, which required changes to how quickstart works: calling sudo is now handled by juju itself, and for this reason quickstart no longer requires to request sudo privileges when bootstrapping the environment. A comprehensive list of changes introduced by the current release follow: - Support for promulgated bundle URLs, e.g. “juju quickstart bundle:mediawiki/single”. - Improved application help and installation instructions. - Updates to the dependency list and to Juju version handling. - Manifest file fixes. - Do not use sudo when bootstrapping a local env if juju version >= 1.17.2. + - Add the distro-only flag: do not use external sources when installing Juju. Dependencies did not change: jujuclient==0.17.5 PyYAML==3.10 urwid==1.1.1 Note: juju-quickstart is in universe, though pending MIR in bug 1273865. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282630 Title: [FFe] Upgrade juju-quickstart to new upstream release 1.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1282630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273865] Re: [MIR] juju-quickstart, python-jujuclient, urwid, websocket-client
We just released quickstart 1.3 implementing the --distro-only flag. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273865 Title: [MIR] juju-quickstart, python-jujuclient, urwid, websocket-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1273865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282630] Re: [FFE] remove sudo support
We just released on PyPi the new 1.2.0 release of quickstart. Juju core 1.17.2 introduced sudo support for local environments, which required changes to how quickstart works: calling sudo is now handled by juju itself, and for this reason quickstart no longer requires to request sudo privileges when bootstrapping the environment. A comprehensive list of changes introduced by the current release follow: - Support for promulgated bundle URLs, e.g. “juju quickstart bundle:mediawiki/single”. - Improved application help and installation instructions. - Updates to the dependency list and to Juju version handling. - Manifest file fixes. - Do not use sudo when bootstrapping a local env if juju version >= 1.17.2. Dependencies did not change: jujuclient==0.17.5 PyYAML==3.10 urwid==1.1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282630 Title: [FFE] remove sudo support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1282630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250007] Re: Bootstrapping azure causes memory to fill
Had the same issue and a debugging session demonstrated that the problem occurs while marshalling the environInfo management-certificate setting. It ended up I was using the wrong path to the certificate (management-certificate-path pointed to the cer file rather than the pem file). I'd suggest to clarify that in the documentation, which seems at least ambiguous: https://juju.ubuntu.com/docs/config-azure.html IMHO we should also improve unexpected values serialization in juju. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250007 Title: Bootstrapping azure causes memory to fill To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1250007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994752] Re: lxc-start-ephemeral's use of dhcp lease table is fragile
Please find attached a diff for fixing the bug. This patch introduces the *lxc-ip* Python script, initially developed in lp:lpsetup, and used to retrieve the ip address of a running container. It also updates *lxc-start-ephemeral* to use lxc-ip and an increased number of connection retries. The diff is against precise-proposed: I hope the diff format is correct. ** Patch added: "bug-994752-lxc-ip.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+attachment/3145695/+files/bug-994752-lxc-ip.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994752 Title: lxc-start-ephemeral's use of dhcp lease table is fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs