Marking as invalid for juju-core as it is reproducible outside of juju
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: In Progress => Invalid
** Changed in: juju-core
Milestone: 2.0-beta12 => None
--
You received this bug no
** Changed in: juju-core
Milestone: 2.0-beta12 => 2.0-beta13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570651
Title:
Manpages for juju aliases drop version
To manage notifications about th
** Changed in: juju-core
Milestone: 2.0-beta12 => 2.0-beta13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage n
** Changed in: juju-core
Milestone: 2.0-beta12 => 2.0-beta13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657
Title:
Bash completion needed for versioned juju commands
To manage notificati
** Changed in: juju-core
Status: Triaged => Fix Committed
** Changed in: juju-core
Milestone: 2.0.0 => 2.0-beta11
** Changed in: juju-core
Assignee: (unassigned) => JuanJo Ciarlante (jjo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Moving juju-core to "Won't Fix" as well since later discussions show
this is a not a problem in juju.
** Changed in: juju-core
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: juju-core
Milestone: 2.0-beta8 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570660
Title:
Plugins not included in juju manpages
To manage notifications about this bu
** Changed in: juju-core
Milestone: 2.0-beta8 => 2.0-beta9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage not
PR: https://github.com/juju/juju/pull/5389
** Changed in: juju-core
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/1581284
Title:
--sslPEMKeyPassword para
** Tags added: usability
--
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
To manage notifications about this bug go to:
h
** Tags added: juju-release-support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576318
Title:
juju register not clear that you're creating a new password
To manage notifications about this bug g
** Changed in: juju-core
Milestone: 2.0-beta4 => 2.0-rc1
--
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 dist upgrade Juju 1.X should still be the default
To manage notificat
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => Critical
** Changed in: juju-core
Milestone: None => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
@jjo - are you still seeing this issue?
** Changed in: juju-core
Milestone: 2.0-beta4 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with re
*** This bug is a duplicate of bug 1548078 ***
https://bugs.launchpad.net/bugs/1548078
I'm going to dup this to bug #1548078 as that one is also about
unhelpful errors when credentials.yaml syntax fails to live up to
expectations.
** This bug has been marked a duplicate of bug 1548078
when
In your example, "balloons" isn't the name of the environment, but
rather the name of that set of credentials.
I know there was discussion last week about using resource tags in the
config. Did that suit your needs?
** Changed in: juju-core
Status: New => Invalid
** Changed in: juju-core
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => Medium
--
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
** Changed in: juju-core
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306315
Title:
juju-mongodb process hangs around after package removal
To manage notifica
** Tags added: 2.0-count
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527020
Title:
cannot build trusty ppc64el juju without forcing GOARCH
To manage notifications about this bug go to:
https://b
** Changed in: juju-core
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Triaged
** Changed in: juju-core/1.25
Importance: Undecided => Critical
** Changed in: juju-core/1.25
Assignee: (unassigned) => Anastasia (anastasia-macmood)
*
Looks like we need to backport tych0's PR which changes the container
detection code:
https://github.com/juju/juju/commit/24fef1aeb33bd31a247be5e1f67b70ed734b9369
IIRC, that introduced some CI failures which were fixed in later
commits, so it's not a straightforward cherry-pick.
** Changed in: ju
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
--
You received this bug notification because
** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To manage notifications abo
** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage no
** 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 w
Public bug reported:
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 we need to
r
** Changed in: juju-core
Milestone: 2.0-alpha2 => 2.0-alpha3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To manage notifications ab
** Changed in: juju-core
Milestone: 2.0-alpha2 => 2.0-alpha3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage n
The script to address this bug is here:
http://paste.ubuntu.com/14474251/
Steps to resolve this issue:
- On the state server, install mongodb-clients (installs the mongo tool to
allow us to manually modify the database)
- Run the insert-statuses.sh script on the state server (machine 0):
./inser
Not fixing in 2.0, as users will be required to upgrade to 1.25.2 before
upgrading to 2.0
** Changed in: juju-core
Status: In Progress => Invalid
** Changed in: juju-core
Status: Invalid => Won't Fix
** Changed in: juju-core
Status: Won't Fix => Invalid
--
You received thi
** Changed in: juju-core
Milestone: 1.26-beta1 => 2.0-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To manage notifications ab
** Changed in: juju-core
Milestone: 1.26-beta1 => 2.0-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage n
** Changed in: juju-core
Milestone: 1.26-alpha3 => 2.0-alpha1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
http
Just a note to those using the script to insert the workload status -
you'll see a bogus time in the "since" field: 31 Dec 1969
18:00:00-06:00
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Ti
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Fix Committed
** Changed in: juju-core/1.25
Importance: Undecided => Critical
** Changed in: juju-core/1.25
Assignee: (unassigned) => Jesse Meek (waigani)
** C
The fix for this is underway, and should be included in 1.25.2.
William kindly put together a script to directly modify mongo to add in
the missing statuses to work around this problem in the meantime. You
can contact me directly to get the script until I figure out where to
put it.
I have verif
I haven't been able to reproduce this again, so marking as invalid.
Thanks for all your help previously, Martin.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: juju-core
Status: Confirmed => Invalid
--
You received this bug notification because you ar
** Changed in: juju-core
Assignee: Cheryl Jennings (cherylj) => Jesse Meek (waigani)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notificati
fwereade is working on a script to repair an environment after this is
hit in an upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications ab
I agree that we cannot move juju 1.25.1 out of proposed until the issue
is resolved. Discussions between dimitern and mpontillo indicate that
this is a maas 1.9beta2+ regression which changes in juju 1.25.1
exposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Changed in: juju-core
Milestone: 1.26-alpha2 => 1.26-beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To manage notifications a
** Changed in: juju-core
Milestone: 1.26-alpha2 => 1.26-beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
Juju will issue a systemctl link to link the unit files, then run
systemctl enable. I cannot recreate this issue on wily, either as a
host, or a wily container running on a wily host (with or without KVM
enabled).
Martin - what information could Adam gather to help debug the issue?
--
You recei
Opening up a systemd record so that team can take a look.
** Also affects: systemd (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/1492088
Title:
Bug #1515463 reveals that this change broke Juju. Marking as
verification failed.
** Tags removed: verification-needed
** Tags added: 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
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Triaged
** Changed in: juju-core/1.25
Importance: Undecided => High
** Changed in: juju-core
Milestone: 1.25.1 => 1.26-alpha1
** Changed in: juju-core/1.25
** Tags removed: bug-squad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failures on wily, juju-template-restart.service race
condition
To manage notifications abo
I was working on implementing your suggested changes yesterday, but
could not get a recreate on ec2 without the changes as a baseline. I
tried multiple instance types, thinking that would help trigger the
hang, but to no avail :(
I hit this a lot using canonistack and will try to recreate there a
** Changed in: juju-core
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failures on wily, juju-template-restart.service race
conditio
** Changed in: juju-core
Assignee: (unassigned) => Cheryl Jennings (cherylj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failures on wily, juju-templ
Thanks for digging into this so much, Martin!
1 - Yes, I will try the runcmd you mention and see if it works.
2 - However, I thought adding in After=cloud-config.target would ensure
that it wouldn't start until after cloud-init completes?
3 - The recreate steps for this are:
- Bootstrap local en
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510619
Title:
Wil
Is there anything else needed from the container? I'm going to mark
this back to new as I've uploaded the requested information.
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
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/1496972
Title:
juju bootstrap fails to
** Changed in: juju-core
Milestone: 1.24.8 => 1.25.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
when deploy
** Attachment added: "update-utmp.trace"
https://bugs.launchpad.net/juju-core/+bug/1509747/+attachment/4505694/+files/update-utmp.trace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
root@juju-wily-lxc-template:/# systemctl daemon-reload
root@juju-wily-lxc-template:/# systemctl restart systemd-update-utmp-runlevel
Job for systemd-update-utmp-runlevel.service failed because the control process
exited with error code. See "systemctl status
systemd-update-utmp-runlevel.service"
** Attachment added: "user-data.txt"
https://bugs.launchpad.net/juju-core/+bug/1509747/+attachment/4505640/+files/user-data.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Inter
** Attachment added: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1509747/+attachment/4505077/+files/journalctl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
I see many failures in journalctl of this type:
systemd[1]: Failed to reset devices.list on /lxc/juju-wily-lxc-
template/system.slice/systemd-update-utmp.service: Permission denied
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
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/1509747
Title:
Int
Serge - your changes from comment #22 will break juju with lxc. juju
will need to be modified to call systemctl add-wants multi-user.target
lxc.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
Verified that Juju can start lxc containers with the proposed changes.
The containers came up and were able to communicate with the state
server, even when on a separate machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Kicked off instances for testing with Juju. Will update with results
once my testing is complete.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image prod
This appears to be a regression in systemd. I extracted the unit file
we're trying to link and manually linked it through systemctl and it
succeeded with 222-2ubuntu1, but failed with 223-1ubuntu1:
ubuntu@cherylj-wily4:~$ apt-cache policy systemd
systemd:
Installed: 222-2ubuntu1
Candidate: 22
66 matches
Mail list logo
