Bug 1268911 - DHCP lease time in log is negative
Summary: DHCP lease time in log is negative
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-05 15:20 UTC by Petr Spacek
Modified: 2016-07-19 18:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:06:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Spacek 2015-10-05 15:20:23 UTC
Description of problem:
DHCP lease time in log is negative when DHCP server is giving out leases with long expiration.

Version-Release number of selected component (if applicable):
NetworkManager-1.0.4-0.1.git20160624.f245b49a.fc22.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. Configure DHCP server to use lease time = 2147483648 seconds
2. Let NM to get the address

Actual results:
$ journalctl -u NetworkManager
NetworkManager[6065]: <info>    lease time -2147483648


Expected results:
$ journalctl -u NetworkManager
NetworkManager[6065]: <info>    lease time 2147483648


Additional info:
DHCP lease time is clearly unsigned integer, see http://tools.ietf.org/html/rfc1533#section-9.2 .

Comment 1 Jirka Klimes 2015-12-03 14:33:45 UTC
Fixed upstream
master: d944a0f dhcp: lifetimes are unsigned integers, use %u printf specifier (rh #1268911)
nm-1-0: c66a021 dhcp: lifetimes are unsigned integers, use %u printf specifier (rh #1268911)

Comment 2 Mike McCune 2016-03-28 22:57:02 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 3 Fedora End Of Life 2016-07-19 18:06:51 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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