Cloud-init difference on 20.04

[Jerry Geis]

I have two differences on cloud-init log

First one:
-- Boot Record 01 --
     06.85600s (init-network/config-ssh)
     00.38800s (modules-config/config-set-passwords)
     00.18100s (modules-final/config-keys-to-console)
     00.14500s (init-local/search-NoCloud)
     00.11600s (init-network/config-users-groups)
     00.04300s (modules-final/config-final-message)
     00.01500s (modules-final/config-ssh-authkey-fingerprints)
     00.01500s (init-network/consume-user-data)
     00.01300s (init-network/check-cache)
     00.00900s (modules-final/config-phone-home)
     00.00800s (modules-config/config-timezone)
     00.00700s (modules-final/config-scripts-per-once)
     00.00700s (modules-config/config-runcmd)
     00.00600s (modules-final/config-scripts-user)
     00.00600s (modules-config/config-ssh-import-id)
     00.00600s (init-network/activate-datasource)
     00.00500s (init-network/config-write-files)
     00.00400s (init-network/config-rsyslog)
     00.00400s (init-network/config-ca-certs)
     00.00200s (modules-config/config-disable-ec2-metadata)
     00.00200s (init-network/config-bootcmd)
     00.00100s (init-network/setup-datasource)
     00.00100s (init-network/consume-vendor-data)
     00.00100s (init-local/check-cache)



Second one:
-- Boot Record 01 --
     10.51100s (init-network/search-NoCloudNet)
     00.21200s (init-network/config-ssh)
     00.05400s (modules-config/config-set-passwords)
     00.03200s (modules-final/config-keys-to-console)
     00.02900s (init-local/search-NoCloud)
     00.02800s (init-network/config-users-groups)
     00.02100s (init-network/consume-user-data)
     00.00200s (modules-final/config-ssh-authkey-fingerprints)
     00.00200s (modules-final/config-final-message)
     00.00100s (modules-config/config-timezone)
     00.00100s (modules-config/config-ssh-import-id)
     00.00100s (init-network/setup-datasource)
     00.00100s (init-network/config-rsyslog)
     00.00100s (init-network/activate-datasource)
     00.00000s (modules-final/config-scripts-user)
     00.00000s (modules-final/config-scripts-per-once)
     00.00000s (modules-final/config-phone-home)
     00.00000s (modules-config/config-runcmd)
     00.00000s (modules-config/config-disable-ec2-metadata)
     00.00000s (init-network/consume-vendor-data)
     00.00000s (init-network/config-write-files)
     00.00000s (init-network/config-ca-certs)
     00.00000s (init-network/config-bootcmd)
     00.00000s (init-network/check-cache)
     00.00000s (init-local/check-cache)


both of these outputs are from the command:
cloud-init analyze blame -i cloud-init.log

The FIRST one is from a machine that is "NOT" starting the autoinstall -
the second one is from an install that "DOES" start the autoinstall.

Clearly in #2 you can see the first thing cloud-init does is:
10.51100s (init-network/search-NoCloudNet)

What is cloud-init "NOT" finding in #1 that is not doing the autoinstall.
Or better question-  HOW do  I find what its missing ???

I have a premade ISO - so I use the same ISO on #2 that worked as I am on
#1.

When I look at the clou-init.log I see no FAIL no error - no missing
user-data file type information. The files are TOO large to include - I
have tried that and it gets blocked. I even tried parts and my email was
still too big.  This cloud-init analyze summary  sure captures the
difference though.

Thanks for any suggestions.

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20210828/736d4305/attachment.html>