@Timo: something needs to pin sssd in main. So either seeding it in
the supported seed or installed by default. It seems you want the first
one, right?
Just waiting on djing-libs to be fixed/acked and if you agree with
seeding that one to the support seed, I'll promote/do it.
--
You received
Public bug reported:
After non-clean shutdown /var/lib/mongodb/mongodb.lock avoid mongodb to
start properly. Adding next line to /etc/init/mongodb.conf (anywhere in
the script section before launching the daemon) fixes the problem:
ps -eo %u | grep -q ^mongodb$ || rm -f
Another logentry points to the dynamic-profiles
[868559.234898] type=1400 audit(1384528406.841:246): apparmor=DENIED
operation=open parent=1 profile=libvirt-
7aa8a408-8ca0-46b3-8ab8-e89b334082d2
name=/var/lib/nova/instances/snapshots/tmpflKt2v/9f52ec7cb15d458488df1a1efad52d9c.delta
pid=7957
Hello, we have the same problem. I found logentries in syslog.
for example:
kernel: [866752.543340] type=1400 audit(1384526598.408:216):
apparmor=DENIED operation=open parent=28895
profile=/usr/lib/libvirt/virt-aa-helper
Public bug reported:
(UBUNTU) Ubuntu 12.04.3 LTS [updatetd just now]
(byobu) Version: 5.17-0ubuntu1
*** (different source in byobu trunk!)
Using 'screen' (tmux NOT TESTED) seemingly holds the last
status string from function __raid in file /usr/lib/byobu/raid forever,
while the RAID rebuild
Disabling apparmor didn't help in our case. Did you try disabling it?
--
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/1244694
Title:
Creating snapshot fails due to nonexistent
Thanks for reporting this issue, I will investigate and promptly issue
an update.
** Changed in: libcommons-fileupload-java (Ubuntu)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I have located the problem. An update is building now and will be
release within the hour.
I apologize for the inconvenience.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcommons-fileupload-java in
Ubuntu.
This bug was fixed in the package libcommons-fileupload-java -
1.2.2-1ubuntu0.12.04.2
---
libcommons-fileupload-java (1.2.2-1ubuntu0.12.04.2) precise-security;
urgency=low
* SECURITY REGRESSION: missing jar file (LP: #1251340)
- debian/libcommons-fileupload-java.poms:
I set the dynamic profile
aa-complain libvirt-7aa8a408-8ca0-46b3-8ab8-e89b334082d2
and shut-off and start the instance. After that i get an snapshot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I added the following line to abstractions/libvirt-qemu:
/var/lib/nova/instances/snapshots/*/*.delta rw,
This is not very secure but at the moment it work. Keep in mind, i have
to restart the kvm-process to apply the new/reloaded profile.
--
You received this bug notification because you are a
Ok. I can reproduce the problem. If i enforce the profile and restart
the machine. The snapshot fails. The profile seems to be ok:
Before snapshot:
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
/var/log/libvirt/**/instance-001e.log w,
** Branch linked: lp:~rogpeppe/juju-core/454-1.16-maas-changes
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1229275
Title:
[maas] juju destroy-environment also destroys nodes that
** Branch linked: lp:~rogpeppe/juju-core/454-1.16-maas-changes
** Branch linked: lp:~rogpeppe/juju-core/453-maas-instance-uuid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Tags added: upgrade-software-version
--
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/1250419
Title:
juju-core should be updated to 0.16.3
To manage notifications about this
Thanks for the quick fix! Unfortunately, something else broke when I
pulled that package from the trusty repository. The lxc instance is
started but nothing runs. Starting it manually vs on boot produces the
same behavior and I only see these two lines when I start manually:
4init: console-setup
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/lxc/trusty
--
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/1251352
Title:
lxc fails to start on boot but succeeds with a manual boot
This bugs represents a severe regression on upgrade from Ubuntu 10.04 LTS to
Ubuntu 12.04 LTS.
The package is rather unusable since it eats up 100% CPU on production
mailservers after upgrade to current LTS.
Would you please include the fix http://bugs.debian.org/cgi-
[Expired for openvpn (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openvpn (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
19 matches
Mail list logo
