I can reproduce this bug
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents
Public bug reported:
Ubuntu Trusty seems to be affected by the scenario number 1 described in
this post on OpenSSL's bug tracker:
http://rt.openssl.org/Ticket/Attachment/45105/25601/
To summarize, verifying the peer's identifer fails when the peer's DN
contains a component of ASN.1 type
** Branch linked: lp:~ubuntu-branches/debian/experimental/dbconfig-
common/experimental
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/584943
Title:
Problem with a password
** Branch linked: lp:~ubuntu-branches/debian/experimental/dbconfig-
common/experimental
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/520872
Title:
dbconfig-common:
** Branch linked: lp:~ubuntu-branches/debian/experimental/dbconfig-
common/experimental
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/252882
Title:
crash on multiple db
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
After watching it carefully, I found two problems:
1, compute node should set hostname, or ovs process will exit due to below
error log
Stderr: 'sudo: unable to resolve host
juju-precise-machine-11\n2015-01-04T06:41:49Z|1|fatal_signal|WARN|terminating
with signal 14 (Alarm clock)\n'
2,
Seeing the exact same issue here. I also note that the crash seems to be
from starting smbd with the '-D' parameter by samba-ad-dc, however, it
shouldn't even be trying to run this from what I can see. The system is
running a fresh installation of Samba with a vanilla configuration and
as such is