[Bug 1013782] [NEW] Stop/start a KVM instance with volumes attached produces an error state

Public bug reported: When a running instance with an attached volume is stopped and then started, the instance refuses to boot and goes into an error state. This appears to be caused by nova-compute incorrectly building the libvirt.xml file. 2012-06-15 03:54:14 TRACE nova.compute.manager [instanc

[Bug 1013782] Re: Stop/start a KVM instance with volumes attached produces an error state

** Attachment added: "Start log" https://bugs.launchpad.net/bugs/1013782/+attachment/3191059/+files/instance-3095.log -- 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/1013782 Title

[Bug 1013782] Re: Stop/start a KVM instance with volumes attached produces an error state

** Attachment added: "Generated libvirt.xml" https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1013782/+attachment/3191060/+files/instance-3095-libvirt.xml -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https:

[Bug 1015369] Re: "IOError: [Errno 32] Broken pipe" on start when many lists are present

I should note this was found on a lucid system, but was reproduced on precise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1015369 Title: "IOError: [Errno 32] Broken pipe" on sta

[Bug 1015369] Re: "IOError: [Errno 32] Broken pipe" on start when many lists are present

-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1015369 Title: "IOError: [Errno 32] Broken pipe" on start when many lists are present To manage notifications about this bug go to: ht

[Bug 1015369] [NEW] "IOError: [Errno 32] Broken pipe" on start when many lists are present

Public bug reported: When running "/etc/init.d/mailman start, I get: # /etc/init.d/mailman stop * Stopping Mailman master qrunner mailmanctl [ OK ] root@chlorine:~# /etc/init.d/mailman start Traceback (most recent call last): File "/var/lib/mailman/bin/list_lists", line 122, in main()

[Bug 1015369] Re: "IOError: [Errno 32] Broken pipe" on start when many lists are present

** Description changed: When running "/etc/init.d/mailman start, I get: # /etc/init.d/mailman stop - * Stopping Mailman master qrunner mailmanctl [ OK ] - root@chlorine:~# /etc/init.d/mailman start +  * Stopping Mailman master qrunner mailmanctl [ OK ] + # /etc/init.d/mailman start Trac

[Bug 1015369] Re: "IOError: [Errno 32] Broken pipe" on start when many lists are present

I'm not too concerned with seeing it fixed; the fact that this LP bug exists at all will probably be sufficient warning to anyone who happens to come across the same problem. (I had just completed a list rename which involves a lot of voodoo, and was concerned the error was indicative of a larger

[Bug 1060900] [NEW] HTTP proxy config being created in /etc/apt/apt.conf on nodes

Public bug reported: When deploying a node, /etc/apt/apt.conf is being created with, for example: Acquire::http::Proxy "http://10.55.65.6:8000/";; Please instead deploy this in, say, /etc/apt/apt.conf.d/90maas. Version: precise 0.1+bzr482+dfsg-0ubuntu1 ** Affects: maas (Ubuntu) Importance

[Bug 1061064] [NEW] ubuntu-cloud.archive: swift3 is no longer in swift-proxy

Public bug reported: Swift 1.7.0 has dropped support for swift3, and there is no packaged replacement in cloud archive. Likely many people upgrading from precise to cloud archive will be relying on S3 emulation, so this could be a concern. The (small c) canonical egg appears to be https://github

[Bug 978127] Re: incorrect time on node causes failed oauth

I just encountered this in precise MAAS, on brand new metal nodes which had dates sometime in 2011. Adding the NTP hack to the ephemeral image helped get around it. (Thanks for the recipe, Jeff! FYI, a public NTP server can work just as well, ntp.ubuntu.com in my case.) Scott Moser: "Basically,

[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise

** Also affects: juju (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1068566 Title: Juju 0.6 incompatible with MAAS in precise To

[Bug 1060900] Re: HTTP proxy config being created in /etc/apt/apt.conf on nodes

Ahh, if it is d-i doing it directly, so be it. The reason it should be separated out into a .d entry is basically, splitting out into .d entries are generally more manageable than using a main config file, especially if you want to undo this functionality change. (Remove the .d file rather than g

[Bug 1095775] [NEW] maas 0.1+bzr482 (precise) incompatible with python-django 1.4 (cloud-archive)

Public bug reported: We have a MAAS server on precise which we added cloud-archive precise- updates/folsom to, which upgraded python-django to 1.4.1-2ubuntu0.2~cloud0. After that, MAAS began failing: [Thu Jan 03 17:56:34 2013] [error] [client 10.33.0.3] mod_wsgi (pid=31732): Exception occurred

[Bug 1167073] [NEW] nova-network should increase nf_conntrack_max

Public bug reported: We ran into trouble when net.netfilter.nf_conntrack_count was exhausted by the system default of net.netfilter.nf_conntrack_max (65536). As the typical use scenario for Nova can easily exhaust that, nova-network should probably set a more reasonable default, like 2097152. Ve

[Bug 1208600] [NEW] "charm proof" does not report a lack of categories

Public bug reported: As categories are a prerequisite for submission to the charm store, (see Bug #1202442), "charm proof" should check for a lack of categories. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: charm-tools 0.3+151-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8

[Bug 1501959] [NEW] "System error" on chfn / su with lxc-start --share-net

Public bug reported: When running `lxc-start --share net 1` on a trusty host with a trusty container, chfn / su (and presumably other utilities which use PAM) fail. Test case: lxc-create -t ubuntu -n test1 cat >/var/lib/lxc/test1/rootfs/config

[Bug 1501959] Re: "System error" on chfn / su with lxc-start --share-net

** Description changed: When running `lxc-start --share net 1` on a trusty host with a trusty container, chfn / su (and presumably other utilities which use PAM) fail. Test case: lxc-create -t ubuntu -n test1 cat >/var/lib/lxc/test1/rootfs/config

[Bug 1307230] [NEW] 3.1.0 daemon infinite loop when no matched user in secrets

Public bug reported: When a client connects to a (trusty 3.1.0) daemon and requests a module which protected by "secrets file", and provides a username which doesn't exist, the daemon process goes into an infinite loop, chewing CPU time. Details are in the upstream bug. ProblemType: Bug DistroRe

[Bug 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration

I can confirm that 29c7787075c92ca8af353acd5301481e6f37082f applies cleanly again the latest trusty tree (3.13.0-27.50), and does indeed fix the vsftpd problem without apparent side effects. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 1323814] Re: sshd: Default is PermitRootLogin without-password

** No longer affects: openssh (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1323814 Title: sshd: Default is PermitRootLogin without-password To manage notifications about