5 minute delay when provisioning over IPv6

Bug #1758324 reported by Derek Higgins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
Medium
Unassigned

Bug Description

The overcloud-full image attempts get a IPv4 address stalling the boot process for 5 minutes when non are available (e.g. if using IPv6), this stalls the boot process for 5 minutes until a timeout is hit

Mar 23 12:30:48 localhost.localdomain network[699]: Bringing up loopback interface: [ OK ]
Mar 23 12:30:48 localhost.localdomain network[699]: Bringing up interface eth0:
Mar 23 12:30:48 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0x5eff4a5b)
Mar 23 12:30:54 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x5eff4a5b)
Mar 23 12:31:02 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x5eff4a5b)
Mar 23 12:31:14 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x5eff4a5b)
Mar 23 12:31:25 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x5eff4a5b)
Mar 23 12:31:41 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x5eff4a5b)
Mar 23 12:31:49 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x5eff4a5b)
Mar 23 12:31:58 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0x5eff4a5b)
Mar 23 12:32:17 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 (xid=0x5eff4a5b)
Mar 23 12:32:35 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=0x5eff4a5b)
Mar 23 12:32:52 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0x5eff4a5b)
Mar 23 12:33:11 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0x5eff4a5b)
Mar 23 12:33:26 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x5eff4a5b)
Mar 23 12:33:37 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x5eff4a5b)
Mar 23 12:33:45 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 (xid=0x5eff4a5b)
Mar 23 12:33:58 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0x5eff4a5b)
Mar 23 12:34:17 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 (xid=0x5eff4a5b)
Mar 23 12:34:35 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x5eff4a5b)
Mar 23 12:34:45 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x5eff4a5b)
Mar 23 12:34:55 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=0x5eff4a5b)
Mar 23 12:35:12 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 (xid=0x5eff4a5b)
Mar 23 12:35:33 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 (xid=0x5eff4a5b)
Mar 23 12:35:46 localhost.localdomain dhclient[868]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x5eff4a5b)
Mar 23 12:35:48 localhost.localdomain systemd[1]: network.service start operation timed out. Terminating.
Mar 23 12:35:48 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.

the boot process then continues and can be reached over its SLAAC address

Revision history for this message
Derek Higgins (derekh) wrote :

The default dhclient timeout is 60, centos have changed it in the cloud image to 300 here
https://bugs.centos.org/view.php?id=6866

This was to deal with a amazon specific issue, I'd like to undo this in our images to atleast reduces the impact of this from 5 minutes to 1 minute (the dhclient default)

Changed in tripleo:
status: Confirmed → Triaged
milestone: none → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Incomplete
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
milestone: victoria-1 → victoria-3
Changed in tripleo:
milestone: victoria-3 → wallaby-1
Changed in tripleo:
milestone: wallaby-1 → wallaby-2
Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Revision history for this message
Marios Andreou (marios-b) wrote :

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo

Changed in tripleo:
milestone: wallaby-3 → none
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.