specified, but you could try specifying it explicitly to
> see if that causes cloud-init to process the user data.
>
> From: ckonstan...@pippiandcarlos.com
> Subject: Re: [Openstack-operators] [openstack-operators] [nova] cloud.cfg not
> applied
>
> It does look funny at first.
sure if it will try to
process the file using a default mechanism if none is specified, but you could
try specifying it explicitly to see if that causes cloud-init to process the
user data.
From: ckonstan...@pippiandcarlos.com
Subject: Re: [Openstack-operators] [openstack-operators] [nova] clo
It does look funny at first. But that's actually two separate
users. This cloud.cfg has been verified in an enterprise cloud. Apart
from the passwd stuff (which I will remove) I am certain it should
work. It specifies that the default user should be created as normal,
and it adds a second ckonstans
The only thing I can think of is that the default user should just be
"default", not qualified with "name". Perhaps that is clobbering your next
entry or just creating a syntax error.
On Wed, Apr 12, 2017 at 11:34 AM, Carlos Konstanski <
ckonstan...@pippiandcarlos.com> wrote:
> I cannot get a sim
I cannot get a simple cloud.cfg to be applied to a newly created
instance. This is the cloud.cfg: (sensitive info removed)
users:
- name: default
- name: ckonstanski
groups: sudo
shell: /bin/bash
sudo: ['ALL=(ALL) NOPASSWD:ALL']
passwd:
lock_passwd: False
ssh-authorize
