** Tags added: cross-team-kanban landscape
--
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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notificat
** Changed in: landscape/cisco-odl
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1490727
Title:
"Invalid IPC credentials" after coros
To clarify, I see the same behavior on bare metal, deploying machines
with MAAS using the fast-path installer, so it's not LXC-specific.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/
The system where we saw this bug uses file system ACLs, with defauls,
and thus the umask is ignored:
ubuntu@juju-machine-0-lxc-5:/var/lib/openstack-dashboard$ getfacl .
# file: .
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::r-x
default:other::r-x
--
I don't think the ordering of the package installs are important. They
run the same command. The problem seem to be that the code that creates
the secret key doesn't create it with the right permissions. The current
code in horizon/utils/secret_key.py does this:
old_umask = os.umask(0o
FWIW, an ugly workaround to this bug is to place a file in /etc/rc0.d
and /etc/rc6.d that removes the line NetworkManager added before
rabbitmq is shut down. I'm attaching the file I'm using to do that.
** Attachment added: "K19remove-nm-from-hosts"
https://bugs.launchpad.net/ubuntu/+source/ra
network that
NetworkManager is connected to. If NM isn't connected to anything,
rabbit-multi status says that rab...@ixia is "not_running" and
rabbitmq-multi stop_all hangs while trying to stop rab...@ixia.
> Björn: do you have anything in shutdown_err by any chance?
No, nothing.
To add further to Thomas' observations, after disconnecting NM, the
beginning of my /etc/hosts file look like this:
192.168.60.104|_ixia|___# Added by NetworkManager
127.0.0.1|__localhost.localdomain|__localhost
::1|ixia|___localhost6.localdomain6|localhost6
127.0.1.1|__ixia
If I
** Attachment added: "shutdown_log"
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/670289/+attachment/1767403/+files/shutdown_log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in ubuntu.
https://bu
Clint, when shutting down, the console doesn't show much. It shows
killing apache, a few other things, and then it stalls when trying to
shut down rabbitmq. I.e, it doesn't get any further, so sendsigs doesn't
get executed.
It's the 'rabbitmq-multi stop_all' that hangs. Seems it's waiting
forever
10 matches
Mail list logo
