Public bug reported:
Seeing libvirt error while trying to deploy instances in OpenStack
deployment:
"error: internal error: Unable to find 'cpuacct' cgroups controller mount".
This is recreatable for kilo and liberty.
The cloud version for kilo is root@lambert:~# dpkg -l|grep virt
ii
I hit similar issue in trusty. The following error is repeated multiple
times in server.log:
2015-11-11 20:20:40.238 9354 TRACE neutron File
"/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 436, in
do_execute
2015-11-11 20:20:40.238 9354 TRACE neutron
Attaching /var/log/neutron/server.log
** Attachment added: "server.log.gz"
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1429739/+attachment/4517291/+files/server.log.gz
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
I was able to recreate. The errors are same on the retry.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1429739
Title:
neutron-server does not start: OperationalError:
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1463046
Title:
installation of multipath-tools-boot can break boot
To manage notifications about this bug
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1370249
Title:
'ascii' codec can't decode byte 0xc3 in position
I verified this for trusty deployment with maas
1.7.0+bzr3299-0ubuntu3~trusty1 and curtin version was
0.1.0~bzr195-0ubuntu1~14.04.1~ppa0.
The steps to test this was to edit the root-tgz after uncompressing and
extracting it, doing a chroot. I then did a sudo apt-get install deja-
dup-backend-gvfs
This was the test case:
1) Update trusty daily root-tgz image with a copy of dcap and cap properties.
2) Sync image to cache
3) Deploy a node with trusty
4) Access deployed node
5) Ensure that cap properties for the new file are preserved on deployed system.
This test passed.
Here are test
