New Question

Revision history [back]

click to hide/show revision 1
initial version


cloud-config userdata behaves very similar to another instance of cloud-init (or cloudbase-init), and mixing metadata information and cloud-config information that applies to the same feature can lead to unwanted behaviours like the ones you have in this case. is being run after the cloud-config Administrator user / password configuration from the cloud-config data, leading to a password reset.

I suggest in this case to remove the and cloudbaseinit.plugins.common.setuserpassword.SetUserPasswordPlugin from the enabled plugins, so that cloud-config data gets applied.

As an overall suggestion, I suggest to use the cloud-config to only specialize the instance with features that the base metadata does not have. If you choose this recomended route, cloud-config should only create the Boris user, and the Administrator creation/password and the hostname configuration to be moved in the metadata.

Thank you,
Adrian Vladu