[Bug 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
davewalker - can we get this packaged for precise as well? ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
** Also affects: keystone (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1167421/+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 1021548] [NEW] nova-network does not contain a dependency on iptables
Public bug reported: The nova-network package does not contain a dependency on iptables and on install will throw a python stack trace nova-rootwrap iptables-save fails. tested on 12.04 ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1021548 Title: nova-network does not contain a dependency on iptables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1021548/+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 941968] Re: lockfile-create hangs inside lxc containers
*** This bug is a duplicate of bug 969299 *** https://bugs.launchpad.net/bugs/969299 I also do not believe that this bug is a duplicate and apparmor is only the culprit in that it is finding a potential overflow somewhere in the ntp code -- 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/941968 Title: lockfile-create hangs inside lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/941968/+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 941968] Re: lockfile-create hangs inside lxc containers
*** This bug is a duplicate of bug 969299 *** https://bugs.launchpad.net/bugs/969299 I played around with this a bit and derived that it is due to the length of the hostname (at least in my case). With a hostname of length 40 I can reproduce this error. Setting the hostname to <= 37 produces the correct results. -- 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/941968 Title: lockfile-create hangs inside lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/941968/+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
