** 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
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
Ti
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/175898
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
T
** 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 environment
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'Addresse
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)
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)
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
react
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
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 d
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
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.
--
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
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 notif
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
** 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
** 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 containe
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
19 matches
Mail list logo
