parameters of starting cloud init
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/
tiemout=30s
/lib/systemd/
TimeoutStartS
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/
tiemout=3s
/lib/systemd/
TimeoutStartS
it
finally , after I have tried serval times , the os succeeds to start cloud init in reasonable time with the following parameters:
/etc/dhcp/
tiemout=10s
/lib/systemd/
TimeoutStartS
In a word, I suggest that different timeout of dhclient or networking.service in different os merits attention.
description: | updated |
Changed in diskimage-builder: | |
status: | New → Confirmed |
assignee: | nobody → magnate (magnate) |