Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1337647 - QCIOOO 1.2 Install loses IP address during first DHCP renew event (dhclient)
Summary: QCIOOO 1.2 Install loses IP address during first DHCP renew event (dhclient)
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: ISO Installer
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ga
: 1.0
Assignee: Jason Montleon
QA Contact: Dave Johnson
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-19 18:01 UTC by Landon LaSmith
Modified: 2016-08-05 14:54 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-08-05 14:54:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1093803 0 high CLOSED dhclient fails to renew IP address lease after system time changes 2023-09-07 18:38:04 UTC

Internal Links: 1093803

Description Landon LaSmith 2016-05-19 18:01:29 UTC
Description of problem: After install of the QCIOOO 1.2 iso, dhclient will lose its dhcp address during the first attempt to renew the IP address.  This problem seems to be related to the fact that a time sync occurs after the dhcp address is acquired.  QCI 1.2 server, doesn't have the same issue where its time synchronized prior to the dhcp lease on the same network.

Issue reoccurs after every reboot. eth0 is attached to public network and eth1 will be used for OSP provisioning on the undercloud

ISO Version: QCIOOO-8.0-RHEL-7-20160518.t.0

How reproducible: 100%

Steps to Reproduce:
1. Install QCI OOO using a 1.2 iso or reboot existing install on a network running an ntp service
2. Wait for first dhcp renew to occur

Actual results: eth0 will lose its IP address and any existing sessions will be dropped.

Expected results: eth0 dhcp renews it IP address even if a large offest time sync occurs after renewal

Additional info:

Comment 1 Landon LaSmith 2016-05-19 19:22:08 UTC
Right now, I can only only reproduce this on our lab network when the type is sync'd backwards after the dhcp lease and probably when that offset is >dhclient dhcp-lease-time.

On our lab network, the lease time began around 18:57, dhclient dhcp-lease-time 600 and dhclient expire time is 23:07. The time was sync'd backwards to 14:57 and the dhcp address was dropped 600 seconds later at 13:07.

Comment 9 Jason Montleon 2016-08-05 14:54:56 UTC
Looking at the kickstarts for the two I saw:
QCI: timezone --utc America/New_York
QCI OOO: timezone US/Eastern

I changes them both to:
timezone --utc America/New_York
so we are consistent.

Other than that the only other difference that stands out are the difference in packages installed.

I suppose if the system clock is set for utc and we were setting US/Eastern time that could be why you're seeing the change only on that ISO. If that's not the case I'd hazard a guess that something is being installed and running as a dependency of the tripleo packages and we can't do anything about it.

Please give the compose being created now a run and see if it works better. If not and we can get more information on what's different we can take another stab at it, otherwise we'll have to rely on progress for the RHEL bug 1093803.

Note You need to log in before you can comment on or make changes to this bug.