parameters of starting cloud init

Bug #1859577 reported by magnate
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
diskimage-builder
Confirmed
Undecided
magnate

Bug Description

firstly, when I use kylin os ironic qcow2 image, the os takes long time to start with the following parameters:
 /etc/dhcp/dhclient.conf dhclient
  tiemout=30s
 /lib/systemd/system/networking.service
  TimeoutStartSec=10 min
I use systemd-analyze blame to analyze the consuming time of different services,and find the networking.service takes too much time。so,I try the next way。

sencondly, when I use kylin os ironic qcow2 image, but the os fails to start cloud init to fetch metadata with the following parameters:
 /etc/dhcp/dhclient.conf dhclient
  tiemout=3s
 /lib/systemd/system/networking.service
  TimeoutStartSec=3min
it

finally , after I have tried serval times , the os succeeds to start cloud init in reasonable time with the following parameters:
 /etc/dhcp/dhclient.conf dhclient
  tiemout=10s
 /lib/systemd/system/networking.service
  TimeoutStartSec=5min

In a word, I suggest that different timeout of dhclient or networking.service in different os merits attention.

magnate (magnate)
description: updated
magnate (magnate)
Changed in diskimage-builder:
status: New → Confirmed
assignee: nobody → magnate (magnate)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.