** Changed in: juju-mongodb3.2 (Ubuntu)
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/1596095
Title:
[needs packaging] 3.2.4-0ubuntu4 available in xenial or
** 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/1612713
Title:
Please merge debian version of golang-juju-loggo-dev
To manage
Tested 2.0~beta15-0ubuntu2.16.04.1. Works 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/1613718
Title:
[SRU] Juju
** Changed in: juju-release-tools
Status: New => Triaged
** Changed in: juju-release-tools
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/1614969
Title:
Juju
** Changed in: juju-release-tools
Status: New => Triaged
** Changed in: juju-release-tools
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/1614724
Title:
Juju
I cannot reproduce this myself, on our CI servers, nor could lazypower
who I asked to try on his machine.
See an upgrade: http://paste.ubuntu.com/23070808/.
My only thought is perhaps you manually mucked with /usr/bin/juju and
somehow that's causing you issues now.
** Changed in:
** Also affects: conjure-up
Importance: Undecided
Status: New
** Also affects: charm-tools
Importance: Undecided
Status: New
** Also affects: charm (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: conjure-up
** No longer affects: charm-tools
**
** Also affects: juju-core-1 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: juju-core-1 (Ubuntu)
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: juju-core
--
You received this bug notification because you are a
$ dpkg-divert --list | grep juju
diversion of /usr/bin/juju to /usr/bin/juju.default by juju-1-default
** Attachment added: "dpkg-divert --list | grep juju"
https://bugs.launchpad.net/juju-release-tools/+bug/1614959/+attachment/4724019/+files/divert
--
You received this bug notification
Expected output should look something like this:
$ ls -al /usr/bin/juju*
lrwxrwxrwx 1 root root 6 Aug 16 16:04 /usr/bin/juju -> juju-1
lrwxrwxrwx 1 root root 9 Aug 16 16:04 /usr/bin/juju-1 -> juju-1.25
-rwxr-xr-x 1 root root 68 Aug 16 16:04 /usr/bin/juju-1.25
-rwxr-xr-x 1 root root 67 Jul 28
** Attachment added: "ls -al /usr/bin/juju*"
https://bugs.launchpad.net/ubuntu/+source/juju-core-1/+bug/1614959/+attachment/4723996/+files/ls%20usr%20binjuju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "juju-xenial-upgrade-log"
https://bugs.launchpad.net/ubuntu/+source/juju-core-1/+bug/1614959/+attachment/4723998/+files/juju-xenial-upgrade-log
** Also affects: juju-release-tools
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
After upgrading from 1.25.5 on xenial to 1.25.6-0ubuntu1.16.04.1,
/usr/bin/juju has disappeared. Attached are the upgrade logs, as well as
an ls of /usr/bin/juju* after the upgrade showing the diversion, but
missing /usr/bin/juju.
** Affects: juju-release-tools
** 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/1611855
Title:
[SRU] Juju 1.25.6
To manage notifications about this bug go to:
Tested on xenial. Deploys, tearsdown, installs and removes cleanly, and
works with juju-1-default as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju 1.25.6
To
** Description changed:
The current package in ubuntu is old and the maintainer is no longer
able to maintain the package. I'd like to request we replace this
package with the debian version which is newer and has a maintainer.
+
+ NOTE: juju-core in xenial would like to depend on this
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@mwhudson, a new version of juju-core-1, 1.25.6, is being uploaded into
yakkety. I agree with the package removal, but given the extended
timeline for juju 2.0, it's possible yakkety retains juju-core-1. Let's
revisit this before FF. I definitely agree with not including it in Z.
--
You received
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
I've restored the debhelper script to version 7 as released. The
juju-1-default.links file was present in my version, heh, but not added
and thus not in the repository. This too has been corrected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
The current package in ubuntu is old and the maintainer is no longer
able to maintain the package. I'd like to request we replace this
package with the debian version which is newer and has a maintainer.
** Affects: golang-juju-loggo (Ubuntu)
Importance: Undecided
** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
** Description changed:
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
*** This bug is a duplicate of bug 1611855 ***
https://bugs.launchpad.net/bugs/1611855
Public bug reported:
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
** Summary changed:
- [SRU] Juju 1.25.6
+ [SRU] Juju 1.25.6 for trusty
** Branch unlinked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
** Branch linked: lp:~juju-qa/ubuntu/trusty/juju/juju-1.25.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju
Public bug reported:
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
Verified I can bootstrap, the gui is pulling the correct version, lxd
and aws all work. Looks good.
** 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.
** Changed in: juju-core (Ubuntu)
Status: Fix Released => 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/1604137
Title:
[SRU] Juju 2.0 beta12 for Xenial
To manage notifications
Binary is present
$ ls /usr/lib/juju/mongo3.2/bin
mongo mongod mongoperf mongos mongosniff
I could invoke the binary
$ /usr/lib/juju/mongo3.2/bin/mongo
MongoDB shell version: 3.2.4
apt-cache show juju-mongodb3.2
Package: juju-mongodb3.2
Priority: optional
Section: universe/database
** Description changed:
- Admins and developers are unable to access to the juju mongodb instance
- to investigation issues.
+ [Impact]
+ 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
It should be noted we were forced to disable one test as it fails on
some architectures due to https://bugs.launchpad.net/juju-
core/+bug/1605313. As we've released the final tarball for beta12, we'd
like to land this SRU and continue working on squashing that bug
completely in the future.
--
It sounds like the "fix" for this lies outside of LXD. Can we add the
affected packages and involve the right upstreams for this? Are we going
to pursue this purely upstream with systemd / kernel or are we going to
attempt a distro-patch of some sort?
--
You received this bug notification
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508122
Title:
please transition to shared libraries
To manage notifications about
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
Marking invalid due to presence of beta12 which will go into yakkety /
xenial.
** Changed in: juju-core (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking invalid due to presence of beta12 which will go into yakkety /
xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596920
Title:
Juju 2.0-beta10 in ubuntu
To manage notifications about
** Also affects: trusty-backports
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/1583740
Title:
mongo client is missing
To manage notifications about
** Changed in: golang-golang-x-oauth2 (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568165
Title:
[MIR] golang-golang-x-oauth2
To manage
** Changed in: golang-gopkg-mgo.v2 (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568162
Title:
[MIR] golang-gopkg-mgo.v2
To manage notifications
** Changed in: golang-github-natefinch-lumberjack (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568168
Title:
[MIR] golang-github-natefinch-lumberjack
** Changed in: golang-google-api (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568163
Title:
[MIR] golang-google-api
To manage notifications about
So src/github.com/juju/juju/etc/bash_completion.d/juju2 is indeed the
cause of the failure. It's not clear why the file was renamed, but I've
added a packaging rule to swap the name so it installs into /usr/share
/bash-completion/completions/juju-core. We should fix upstream if
possible.
In my
** Also affects: grub2 (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/1532935
Title:
Nodes stuck at grub menu when attempting to deploy
To
I have installed the proposed package on trusty and verified its
functionality.
** 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.
** 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
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
@Timo, ahh! Hence the fascination with unetbootin. Makes sense now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530530
Title:
Installer doesn't show up on some Chromebook
To manage
Timo, this only affects newer releases. 14.04 works with the workaround
mentioned. The issue is indeed the resolution and 3:2 scaling I'd guess.
There's no graceful fallback either and you have to workaround it or
patch even after installed.
--
You received this bug notification because you are
Public bug reported:
See
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
Since we want to support multi-release from the same branch, let's make
sure we adopt using the release name in strings as well.
** Affects: juju-core (Ubuntu)
Importance: Undecided
** 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 post-
- xenial release. This updates juju to the lastest 2.0 milestone version,
- beta5.
-
+ xenial release. This updates juju to
** Summary changed:
- [SRU] Juju 2.0 beta5 for Xenial
+ [SRU] Juju 2.0 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/1573176
Title:
[SRU] Juju 2.0 for Xenial
To manage notifications
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 post-
xenial release. This updates juju to the lastest 2.0 milestone version,
beta5.
[SRU Information]
juju-core has a stable release
Public bug reported:
We should have a vcs:bzr entry in debian/control
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We fixed bug 1564622, along with creating a juju-1-default package in
xenial to alleviate this issue. Juju 2.0 is the default /usr/bin/juju
and will remain as such in Xenial, regardless of the installation path.
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in:
Packaging has been updated and tested with all packages in main. Juju in
xenial should depend on the packages in main listed above with the next
upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
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.
- Currently we need to
mterry, the ubuntu server team should be the team bug subscriber. I
added canonical-juju-qa as we are helping package this, and thus it
makes it easier for us to also keep track during this process. Sorry for
the confusion.
On the test front, mongodb has had some packaging work done during
xenial
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package
@vorlon, yes you are correct, nothing is changing on that front. I've
simply added the juju-qa team as well so we can also keep an eye on
things during this process.
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package
** Description changed:
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
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913 for the
FFe.
This bug will track our dependencies to
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be
For juju, we still need to ensure our MIR's are reviewed and land into
main, and that our packaging utilizes all possible dependencies that are
already in the archive. This work is targeted before release and is
being tracked in bug 1568148.
--
You received this bug notification because you are
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be
Public bug reported:
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
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913 for the
FFe.
This bug will track our dependencies to ensure we meet this
** Changed in: juju-core
Milestone: None => 2.0.0
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Tags added: docteam juju-release-support
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: juju-core
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/1564165
Title:
Credentials file displays unhelpful message for syntax errors
To
** Also affects: juju-core
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/1564157
Title:
juju list-credentials fails to display
To manage notifications
** 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/1561633
Title:
help should work properly with alternatives
To manage notifications
** Also affects: juju-core
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/1564168
Title:
juju list-credentials --show-secrets does not display passwords
** Also affects: juju-core
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/1564670
Title:
After upgrade Juju 1.X should still be the default
To manage
** Also affects: juju-core
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/1564163
Title:
environment name in credentials file is not a tag
To manage
Here's the ppa with the packages:
https://launchpad.net/~nskaggs/+archive/ubuntu/juju/+packages
And here's the status for each dependency mentioned.
http://paste.ubuntu.com/15569917/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's the ppa with the packages:
https://launchpad.net/~nskaggs/+archive/ubuntu/juju/+packages
And here's the status for each dependency mentioned.
http://paste.ubuntu.com/15569917/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Jamie, the additional packages are:
golang-github-altoros-gosigma
golang-github-dustin-go-humanize
golang-github-gabriel-samfira-sys
golang-github-gosuri-uitable
golang-github-joyent-gocommon
golang-github-joyent-gomanta
golang-github-joyent-gosdc
golang-github-joyent-gosign
Jamie, the additional packages are:
golang-github-altoros-gosigma
golang-github-dustin-go-humanize
golang-github-gabriel-samfira-sys
golang-github-gosuri-uitable
golang-github-joyent-gocommon
golang-github-joyent-gomanta
golang-github-joyent-gosdc
golang-github-joyent-gosign
Adam has built the initial version desired for upload:
https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
Adam has built the initial version desired for upload:
https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[FFe] juju-core 2.0
Public bug reported:
juju list-credentials --show-secrets does not display password data,
unless used with --format yaml.
The following commands all fail to show additonal information using
--show-secrets
juju list-credentials --show-secrets
juju list-credentials --format json --show-secrets
Public bug reported:
juju list-credentials --show-secrets does not display password data,
unless used with --format yaml.
The following commands all fail to show additonal information using
--show-secrets
juju list-credentials --show-secrets
juju list-credentials --format json --show-secrets
Public bug reported:
If credentials.yaml contains invalid syntax, the error is
ERROR credentials.blarhg.google.credentials: expected string, got map
which does not accurately convey 'blarhg' is not valid syntax.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
If credentials.yaml contains invalid syntax, the error is
ERROR credentials.blarhg.google.credentials: expected string, got map
which does not accurately convey 'blarhg' is not valid syntax.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
It would be nice to include a tag of the environment name from my
credentials file.
aws:
default-credential: balloons
balloons:
auth-type: access-key
access-key: XXXxxx
secret-key: xxx
Given those credentials, I expect
Public bug reported:
It would be nice to include a tag of the environment name from my
credentials file.
aws:
default-credential: balloons
balloons:
auth-type: access-key
access-key: XXXxxx
secret-key: xxx
Given those credentials, I expect
Public bug reported:
When a cloud is not found in your credentials file, the credentials are
not listed. In addition, the credentials error given is confusing, and
non-consistent.
nskaggs@pixel:~$ juju list-credentials
ERROR removing secrets from credentials for cloud maas18: cloud maas18 not
Public bug reported:
When a cloud is not found in your credentials file, the credentials are
not listed. In addition, the credentials error given is confusing, and
non-consistent.
nskaggs@pixel:~$ juju list-credentials
ERROR removing secrets from credentials for cloud maas18: cloud maas18 not
This package is sitting in the xenial upload queue, ready for review.
The upload has been blocked upon juju2 landing into xenial, and thus
should be considered for an exception to missing the upload window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This package is sitting in the xenial upload queue, ready for review.
The upload has been blocked upon juju2 landing into xenial, and thus
should be considered for an exception to missing the upload window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- The Juju team is preparing for a 2.0-beta1 release in time for the
- xenial feature freeze date (18-Feb), but not all features required for
- 2.0 will be ready by that date. We believe we will have a complete and
- stable Juju 2.0 by the time of the xenial release, but
** Description changed:
- The Juju team is preparing for a 2.0-beta1 release in time for the
- xenial feature freeze date (18-Feb), but not all features required for
- 2.0 will be ready by that date. We believe we will have a complete and
- stable Juju 2.0 by the time of the xenial release, but
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561210
Title:
juju-core should depend on python3
To manage notifications about this bug go to:
Public bug reported:
When calling help using juju2 directly, it refers to using the commands
as 'juju', rather than juju2. The help should be dynamic as well with
the alternatives packaging so when juju2 help is called directly, it
also specifies the use of juju2.
** Affects: juju-core (Ubuntu)
Public bug reported:
When calling help using juju2 directly, it refers to using the commands
as 'juju', rather than juju2. The help should be dynamic as well with
the alternatives packaging so when juju2 help is called directly, it
also specifies the use of juju2.
** Affects: juju-core (Ubuntu)
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1561210
Title:
juju-core should depend on python3
To manage notifications about this bug go to:
101 - 200 of 751 matches
Mail list logo
