Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-16394

cloud-init start takes about 50s on EC2 images

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • rhel-9.2.0
    • cloud-init
    • None
    • None
    • None
    • 6
    • rhel-sst-virtualization-cloud
    • ssg_virtualization
    • 1
    • QE ack
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • RHELOPC Sprint 3, RHELOPC Sprint 4, RHELOPC Sprint 5, RHELOPC Sprint 6, RHELOPC Sprint 7, RHELOPC Sprint 8
    • None
    • None
    • None

      This is similar to BZ  https://bugzilla.redhat.com/show_bug.cgi?id=1994804

      When starting any of the EC2 RHEL images the boot time is taking about an additional 50second while waiting on cloud-init.

      For example, using `ami-0bcd5ad72ba648be1` we could see:

       

      $ systemd-analyze
      Startup finished in 2.221s (kernel) + 5.104s (initrd) + 1min 6.840s (userspace) = 1min 14.166s
      multi-user.target reached after 1min 4.690s in userspace
      $ systemd-anaylze blame
      57.384s cloud-init-local.service
      5.514s initrd-switch-root.service
      2.166s kdump.service
      1.507s cloud-init.service
      1.269s cloud-final.service
      1.000s tuned.service
      910ms cloud-config.service
      866ms auditd.service
      675ms dev-mqueue.mount
      672ms systemd-remount-fs.service
      659ms sys-kernel-debug.mount
      647ms nis-domainname.service
      510ms unbound-anchor.service
      496ms sysroot.mount
      484ms dev-hugepages.mount
      445ms systemd-udevd.service
      402ms dracut-initqueue.service
      360ms polkit.service
      339ms import-state.service
      329ms systemd-logind.service
      297ms chronyd.service
      285ms systemd-journald.service
      253ms NetworkManager-wait-online.service
      
      $ cloud-init analyze blame
      -- Boot Record 01 --
      51.11400s (init-local/search-Ec2Local)
      00.21600s (init-network/config-ssh)
      00.20500s (modules-final/config-keys-to-console)
      00.14100s (init-network/config-growpart)

       

      The workaround has been to create its own AMI image, but first clearing /etc/resolve.conf we will not see the above issue. 

       

              cavery@redhat.com Cathy Avery
              rhn-support-schandle Samuel Chandler
              virt-maint virt-maint
              Amy Chen Amy Chen
              Votes:
              0 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: