yahoo-eng-team team mailing list archive

[Ron <2007149@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi,

I'm using the latest AlmaLinux 9 GenericCloud image. This has cloud-init
22.1-5.el9.alma and works with OpenNebula. Booting is very slow on
OpenNebula because of a 120 seconds timeout.

systemd-analyze blame give me: 
2min 3.083s cloud-init-local.service

In de cloud-init.log I see:

<snip> 
2023-02-10 15:02:06,140 - util.py[DEBUG]: Reading from /run/cloud-init/tmp/tmp9vaos175/context.sh (quiet=False)
2023-02-10 15:02:06,140 - util.py[DEBUG]: Read 3580 bytes from /run/cloud-init/tmp/tmp9vaos175/context.sh
2023-02-10 15:02:06,141 - subp.py[DEBUG]: Running command ['sudo', '-u', 'nobody', 'bash', '-e'] with allowed return codes [0] (shell=False, capture=True)
2023-02-10 15:04:06,448 - util.py[DEBUG]: Reading from /sys/class/net/eth0/addr_assign_type (quiet=False)
2023-02-10 15:04:06,448 - util.py[DEBUG]: Read 2 bytes from /sys/class/net/eth0/addr_assign_type
2023-02-10 15:04:06,448 - util.py[DEBUG]: Reading from /sys/class/net/eth0/uevent (quiet=False)
<snip>

See the two minute timeout after subp.py command.

When running the cloud-init-local.service manually when the machine is
started I get the same logging but without the 120 seconds timeout.

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Attachment added: "cloud-init.tar.gz"
   https://bugs.launchpad.net/bugs/2007149/+attachment/5646807/+files/cloud-init.tar.gz

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2007149

Title:
  120 seconds timeout on OpenNebula running subp.py

Status in cloud-init:
  New

Bug description:
  Hi,

  I'm using the latest AlmaLinux 9 GenericCloud image. This has cloud-
  init 22.1-5.el9.alma and works with OpenNebula. Booting is very slow
  on OpenNebula because of a 120 seconds timeout.

  systemd-analyze blame give me: 
  2min 3.083s cloud-init-local.service

  In de cloud-init.log I see:

  <snip> 
  2023-02-10 15:02:06,140 - util.py[DEBUG]: Reading from /run/cloud-init/tmp/tmp9vaos175/context.sh (quiet=False)
  2023-02-10 15:02:06,140 - util.py[DEBUG]: Read 3580 bytes from /run/cloud-init/tmp/tmp9vaos175/context.sh
  2023-02-10 15:02:06,141 - subp.py[DEBUG]: Running command ['sudo', '-u', 'nobody', 'bash', '-e'] with allowed return codes [0] (shell=False, capture=True)
  2023-02-10 15:04:06,448 - util.py[DEBUG]: Reading from /sys/class/net/eth0/addr_assign_type (quiet=False)
  2023-02-10 15:04:06,448 - util.py[DEBUG]: Read 2 bytes from /sys/class/net/eth0/addr_assign_type
  2023-02-10 15:04:06,448 - util.py[DEBUG]: Reading from /sys/class/net/eth0/uevent (quiet=False)
  <snip>

  See the two minute timeout after subp.py command.

  When running the cloud-init-local.service manually when the machine is
  started I get the same logging but without the 120 seconds timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2007149/+subscriptions