Thanks!
Bugreport here: https://bugs.launchpad.net/cloud-init/+bug/1392921
On 11/14/2014 09:35 PM, Joshua Harlow wrote:
Can u open a bug with cloud-init with logs of what happened
(/var/log/cloud-init.log)
I don't believe this should happen (unless the instance id changed),
There was a bug i
Can u open a bug with cloud-init with logs of what happened
(/var/log/cloud-init.log)
I don't believe this should happen (unless the instance id changed),
There was a bug in an older version of cloud-init that may have caused this so
knowing the cloud-init version would be good to.
Thanks,
Jo
We do not use config drive, only metadata server. I think it somehow
related to non-working (for some time) metadata server and standalone
instances booted without metadata (we reboot them after, but cloud-init
still can mess up...)
On 11/14/2014 04:21 AM, Abel Lopez wrote:
Haven't seen that m
Haven't seen that myself, I wonder if there is a conflict between
cloud-init and libvirt_inject_key. Also curious if you're using the
metadata api or config_drive.
On Thursday, November 13, 2014, George Shuklin
wrote:
> Hello.
>
> We had planned power outage for one of our OS installation (havan
Hello.
We had planned power outage for one of our OS installation (havana).
After everything booted back, we found every instance has change it's
own ssh key (server key ssh-server presents upon connection).
Is this bug or feature? Someone saw that? Is any way to prevent this?
Thanks!
_
