yahoo-eng-team team mailing list archive

[Alberto Contreras <2007149@xxxxxxxxxxxxxxxxxx>]

Per the discussion, it looks like it is a cloud misconfiguration and I
am going to mark it as invalid for the time being.

** Changed in: cloud-init
       Status: New => Invalid

-- 
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:
  Invalid

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-09 11:30:10,244 - util.py[DEBUG]: Reading from /run/cloud-init/tmp/tmpac937qy0/context.sh (quiet=False)
  2023-02-09 11:30:10,245 - util.py[DEBUG]: Read 3674 bytes from /run/cloud-init/tmp/tmpac937qy0/context.sh
  2023-02-09 11:30:10,245 - subp.py[DEBUG]: Running command ['sudo', '-u', 'nobody', 'bash', '-e'] with allowed return codes [0] (shell=False, capture=True)
  2023-02-09 11:32:10,667 - util.py[DEBUG]: Reading from /sys/class/net/eth0/addr_assign_type (quiet=False)
  2023-02-09 11:32:10,668 - util.py[DEBUG]: Read 2 bytes from /sys/class/net/eth0/addr_assign_type
  2023-02-09 11:32:10,669 - 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