Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I believe you are right. see below /etc/rc.d/rc5.d/

lrwxrwxrwx. 1 root root 26 Mar 4 21:15 S50cloud-init-local -> ../init.d/cloud-init-local lrwxrwxrwx. 1 root root 20 Mar 4 21:15 S51cloud-init -> ../init.d/cloud-init lrwxrwxrwx. 1 root root 22 Mar 4 21:15 S52cloud-config -> ../init.d/cloud-config lrwxrwxrwx. 1 root root 21 Mar 4 21:15 S53cloud-final -> ../init.d/cloud-final

The cloud-init process is at 50-53 step in the boot sequence.

I believe you are right. see below /etc/rc.d/rc5.d/

lrwxrwxrwx. 1 root root 26 Mar  4 21:15 S50cloud-init-local -> ../init.d/cloud-init-local
lrwxrwxrwx. 1 root root 20 Mar  4 21:15 S51cloud-init -> ../init.d/cloud-init
lrwxrwxrwx. 1 root root 22 Mar  4 21:15 S52cloud-config -> ../init.d/cloud-config
lrwxrwxrwx. 1 root root 21 Mar  4 21:15 S53cloud-final -> ../init.d/cloud-final

../init.d/cloud-final

The cloud-init process is at 50-53 step in the boot sequence.

I believe you are right. see below /etc/rc.d/rc5.d/

lrwxrwxrwx. 1 root root 26 Mar  4 21:15 S50cloud-init-local -> ../init.d/cloud-init-local
lrwxrwxrwx. 1 root root 20 Mar  4 21:15 S51cloud-init -> ../init.d/cloud-init
lrwxrwxrwx. 1 root root 22 Mar  4 21:15 S52cloud-config -> ../init.d/cloud-config
lrwxrwxrwx. 1 root root 21 Mar  4 21:15 S53cloud-final -> ../init.d/cloud-final

The cloud-init process is at 50-53 step in the boot sequence.

And one workaround for this case is to manually create user before other content in the user-data

I believe you are right. see below /etc/rc.d/rc5.d/

lrwxrwxrwx. 1 root root 26 Mar  4 21:15 S50cloud-init-local -> ../init.d/cloud-init-local
lrwxrwxrwx. 1 root root 20 Mar  4 21:15 S51cloud-init -> ../init.d/cloud-init
lrwxrwxrwx. 1 root root 22 Mar  4 21:15 S52cloud-config -> ../init.d/cloud-config
lrwxrwxrwx. 1 root root 21 Mar  4 21:15 S53cloud-final -> ../init.d/cloud-final
lrwxrwxrwx. 1 root root 14 Feb 25 12:00 S55sshd -> ../init.d/sshd

The cloud-init process is at 50-53 step in the boot sequence.

And one workaround for this case is to manually create user before other content in the user-data