Public bug reported:
16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
Error when enabling Pacemaker service
# sudo systemctl enable pacemaker
Synchronizing state of pacemaker.service with SysV init with
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-
Any progress with regards to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341
Title:
fails in lxd container
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Newell,
I worked with mpontillo today, and figured out that I had completed a
task in the 'wrong order of events' when setting up a node in MAAS.
Apparently you cannot power on a node, after commisioning it and in
"Ready" state. You have to deploy first.
Once adding my ssh key, I was successfully
Update
Hardware Tested : Intel NUC Model:NUC5i5MYHE with VPro extension running AMT
Version: 10.0.45
MAAS Version : 1.8.3+bzr4053-0ubuntu1 (trusty1)
Unit properly can be commissioned in MAAS and is in ready state, however
"power on" function does not work.
--
You received this bug notificat
Tested with: Intel NUC Model:NUC5i5MYHE with VPro extension running AMT
Version: 10.0.45
To get this working properly with MAAS Version 1.8.3+bzr4053-0ubuntu1
(trusty1) , I had to also install the wsmancli package, which MAAS
appears to now take advantage of to properly control the device. This
Public bug reported:
Maas hands out 2 ips to the same mac address when juju-bootstrapping.
This causes further issues when juju charms are deployed which get confused by
two ips being present.
This is present in the latest 14.04LTS with juju 1.18.1 and Maas
Bug is similar to bug:
https://bu
