[Bug 1602192] Re: deploy 30 nodes on lxd, machines never leave pending
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: deploy 30 nodes on lxd, machines never leave pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** 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 this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588403 Title: Tab completion missing in Juju 2.0 betas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1588403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590689] Re: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-br0 interfaces have the same IP address at the same time
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.launchpad.net/bugs/1590689 Title: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju- br0 interfaces have the same IP address at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1590689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570660] Re: Plugins not included in juju manpages
** 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 bug go to: https://bugs.launchpad.net/juju-core/+bug/1570660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581284] Re: --sslPEMKeyPassword parameter must be passed with = on yakkety
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 parameter must be passed with = on yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1581284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** 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: https://bugs.launchpad.net/juju-core/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576318] Re: juju register not clear that you're creating a new password
** 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 go to: https://bugs.launchpad.net/juju-core/+bug/1576318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564670] Re: After dist upgrade Juju 1.X should still be the default
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1564670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564670] Re: After dist upgrade Juju 1.X should still be the default
** 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://bugs.launchpad.net/bugs/1564670 Title: After dist upgrade Juju 1.X should still be the default To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1564670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
@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 replicas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564165] Re: Credentials file displays unhelpful message for syntax errors
*** 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 adding credentials to the credentials.yaml missing the 'name' level causes undecipherable error -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1564165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564163] Re: environment name in credentials file is not a tag
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 (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/1564163 Title: environment name in credentials file is not a tag To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1564163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** 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 fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306315] Re: juju-mongodb process hangs around after package removal
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527020] Re: cannot build trusty ppc64el juju without forcing GOARCH
** 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://bugs.launchpad.net/juju-core/+bug/1527020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** Changed in: juju-core Status: Triaged => Invalid -- 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/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** 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) ** Changed in: juju-core/1.25 Milestone: None => 1.25.5 ** Changed in: juju-core Milestone: 1.25.5 => None -- 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** 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) ** Changed in: juju-core/1.25 Milestone: None => 1.25.5 ** Changed in: juju-core Milestone: 1.25.5 => None -- 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/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
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: juju-core Milestone: None => 1.25.5 ** Changed in: juju-core Importance: High => Critical -- 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/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
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: juju-core Milestone: None => 1.25.5 ** Changed in: juju-core Importance: High => Critical -- 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** 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 you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** 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 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** Changed in: juju-core Milestone: 2.0-alpha3 => 2.0-beta4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1500981 Title: juju-db segfault while syncing with replicas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-alpha3 => 2.0-beta4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545913] Re: [FFe] juju-core 2.0
** 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 we need to request a feature freeze exception for the following features: - Juju-GUI in Core - Removal of LXC from 2.0 codebase - Model migration - MAAS 2.0 support - Keystone 3 support + - Resources (validation of file extension, notification of resource updates available from the charm store) + - Multi-model backup / restore enhancements + - Additional cloud credentials requirements + - Additional MAAS Spaces support + These features are critical for a final Juju 2.0 release. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545913] Re: [FFe] juju-core 2.0
** 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 we need to request a feature freeze exception for the following features: - Juju-GUI in Core - Removal of LXC from 2.0 codebase - Model migration - MAAS 2.0 support - Keystone 3 support + - Resources (validation of file extension, notification of resource updates available from the charm store) + - Multi-model backup / restore enhancements + - Additional cloud credentials requirements + - Additional MAAS Spaces support + These features are critical for a final Juju 2.0 release. -- 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: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545913] [NEW] [FFe] juju-core 2.0
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 request a feature freeze exception for the following features: - Juju-GUI in Core - Removal of LXC from 2.0 codebase - Model migration - MAAS 2.0 support - Keystone 3 support These features are critical for a final Juju 2.0 release. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545913] [NEW] [FFe] juju-core 2.0
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 request a feature freeze exception for the following features: - Juju-GUI in Core - Removal of LXC from 2.0 codebase - Model migration - MAAS 2.0 support - Keystone 3 support These features are critical for a final Juju 2.0 release. ** Affects: juju-core (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/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** Changed in: juju-core Milestone: 2.0-alpha2 => 2.0-alpha3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1500981 Title: juju-db segfault while syncing with replicas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-alpha2 => 2.0-alpha3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
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): ./insert-statuses.sh 0 (if your state server is not machine 0, change 0 to be the correct machine number) -- 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
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): ./insert-statuses.sh 0 (if your state server is not machine 0, change 0 to be the correct machine number) -- 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: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
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 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: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
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 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
** Changed in: juju-core Milestone: 1.26-alpha3 => 2.0-alpha1 -- 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
** 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: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 1.26-beta1 => 2.0-alpha2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** Changed in: juju-core Milestone: 1.26-beta1 => 2.0-alpha2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1500981 Title: juju-db segfault while syncing with replicas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
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 Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
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 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
** 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) ** Changed in: juju-core/1.25 Milestone: None => 1.25.2 ** Changed in: juju-core Milestone: 1.25.2 => 1.26-alpha3 ** Changed in: juju-core Status: Fix Committed => 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
** 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) ** Changed in: juju-core/1.25 Milestone: None => 1.25.2 ** Changed in: juju-core Milestone: 1.25.2 => 1.26-alpha3 ** Changed in: juju-core Status: Fix Committed => In Progress -- 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516989] Re: juju status broken
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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
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 Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address
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 Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1519527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1519527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
** Changed in: juju-core Assignee: Cheryl Jennings (cherylj) => Jesse Meek (waigani) -- 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition
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 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
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 verified that running the script after an upgrade resolves the unit not found error. -- 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: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
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 verified that running the script after an upgrade resolves the unit not found error. -- 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** Changed in: juju-core Milestone: 1.26-alpha2 => 1.26-beta1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1500981 Title: juju-db segfault while syncing with replicas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1500981] Re: juju-db segfault while syncing with replicas
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1500981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 1.26-alpha2 => 1.26-beta1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492088] Re: juju bootstrap fails inside a wily container
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492088 Title: juju bootstrap fails inside a wily container To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492088] Re: juju bootstrap fails inside a wily container
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: juju bootstrap fails inside a wily container To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1492088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1514623 Title: New upstream bugfix release 1.0.8 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514623/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)
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/1514623 Title: New upstream bugfix release 1.0.8 (LXC MRE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition
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 again. The recreate steps look good. Thanks for adding them, and for your explanation about using the cloud-config target. I've asked around to see if others can recreate on their local wily systems, and it seems I'm the only one who has run into this. I'm going to lower the priority and continue to try and get a recreate. ** Changed in: juju-core Importance: High => Medium -- 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition
** 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** 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 Milestone: None => 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 deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition
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 env on wily (this won't create a container) - Deploy using the command: `juju deploy wily/ubuntu`. It may take some time before you see the container started as juju will download the image before starting the template container. -- 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 about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition
** 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-template-restart.service race condition To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition
** 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 condition To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
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 Ubuntu. https://bugs.launchpad.net/bugs/1509747 Title: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0
** 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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1510619 Title: Wily: add machine fails using kvm and lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0
** 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: Wily: add machine fails using kvm and lxcbr0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** 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 deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496972] Re: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel
** 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 successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1496972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
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" and "journalctl -xe" for details. root@juju-wily-lxc-template:/# systemctl status systemd-update-utmp-runlevel.service ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel Changes Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2015-10-26 14:06:01 UTC; 19s ago Docs: man:systemd-update-utmp.service(8) man:utmp(5) Process: 7043 ExecStart=/usr/bin/strace -fvvs1024 -o /run/update-utmp.trace /lib/systemd/systemd-update-utmp runlevel (code=exited, status=1/FAILURE) Main PID: 7043 (code=exited, status=1/FAILURE) ** Attachment added: "debug-journalctl" https://bugs.launchpad.net/juju-core/+bug/1509747/+attachment/4505642/+files/debug-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: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
** 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: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
** 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: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
** 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: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
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://bugs.launchpad.net/bugs/1509747 Title: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509747] Re: Intermittent lxc failures on wily
** 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: Intermittent lxc failures on wily To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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 produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
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/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480310] Re: dbus link request failed for service FOO: Unit name FOO is not valid.
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: 223-1ubuntu1 Version table: 223-1ubuntu1 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages *** 222-2ubuntu1 0 100 /var/lib/dpkg/status root@cherylj-wily4:~$ sudo systemctl link /var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service Created symlink from /etc/systemd/system/juju-db-ubuntu-local.service to /var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service. ubuntu@cherylj-wily4:~$ sudo systemctl disable /var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service Removed symlink /etc/systemd/system/juju-db-ubuntu-local.service. ubuntu@cherylj-wily4:~$ sudo apt-get upgrade ... ubuntu@cherylj-wily4:~$ apt-cache policy systemd systemd: Installed: 223-1ubuntu1 Candidate: 223-1ubuntu1 Version table: *** 223-1ubuntu1 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ubuntu@cherylj-wily4:~$ sudo systemctl link /var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service Failed to execute operation: Unit name /var/lib/juju/init/juju-db-ubuntu-local/juju-db-ubuntu-local.service is not valid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480310 Title: dbus link request failed for service FOO: Unit name FOO is not valid. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1480310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
