Created attachment 949503 [details]
Log of command output after problem manifests

Description of problem:

When the date of a system is adjusted back by more then the length of a DHCP lease the IP address is lost from the interface.

We see this problem installing with anaconda during the post-install-script stage.

Version-Release number of selected component (if applicable):

NetworkManager-0.9.9.0-90.38.git20131003.fc20.x86_64
dhclient-4.2.7-2.fc20.x86_64

How reproducible:

100%

Steps to Reproduce:
1. set up DHCP to offer leases with 900s lifetime
2. set the BIOS date and time 6 hours in the future
3. install fedora 20 from a kickstart that uses a post install script that:
 3.1 uses ntpdate to set the correct time
 3.2 prompts for input
 3.3 uses the network
4. At the prompt (3.2) wait 1000s (until after the 900s life time expires)
5. input to continue to step (3.3). It will fail as the network is down

This should also repro on a desktop system with (untest):

1. set up DHCP to offer leases with 900s lifetime
2. set the time 6 hours into the future
3. reboot
4. use ntpdate to fix the time
5. wait 1000s
6. At this point you have lost hour ip address

Actual results:

interface loses its ip address.

"ip addr" shows the address is gone.
"nmcli device show" shows that the expiry is in the future (by about 6 hours)

see attachment for log of command output.

Expected results:

ip address coninues to be renewed and remains set of the interface

Additional info:

Kernel seems to use monotonic time.
NetworkManager seems to use wall clock time that is changing.