*** This bug is a duplicate of bug 1124384 ***
https://bugs.launchpad.net/bugs/1124384
With juju 1.24 this bug appears to be hit on state servers started with
'juju ensure-availability' during cloud-init upgrade, unless enable-os-
refresh-update and enable-os-upgrade are set to false.
--
*** This bug is a duplicate of bug 1296459 ***
https://bugs.launchpad.net/bugs/1296459
I seem to be seeing this issue as well. I'm not sure if its the
duplicate issue.
The profile config file name is lxc-default-with-mounting yet the
actual profile name appears to be changed to
running into the same error with juju -v bootstrap:
$ juju -v bootstrap
verbose is deprecated with the current meaning, use show-log
2013-11-13 05:07:24 INFO juju.environs open.go:156 environment info already
exists; using New not Prepare
2013-11-13 05:07:25 INFO juju.environs.tools tools.go:181
Public bug reported:
1. Description of the problem:
The maas dhcpd.conf.template only adds ignore-client-uids if using
raring or later. Packages in the cloud-tools archive should work on
precise and require this option for dhcpd. I have verified that dhcpd
starts after adding ignore-client-uids
I see for precise-proposed, the patch is to add a 30 second lease for
pxe agents. This is resulting the lease during pxe being added to the
leases file with a 30 second expiration as expected, but the expiration
is not being honored.
We are seeing machines given the ip from the 30 second lease
verified that this resolved the 400 BAD REQUEST, during bootstrap
--
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/1204507
Title:
MAAS rejects empty files
To manage notifications about
