Bug 1432941 - Anaconda's GATEWAY_PING_TIMEOUT value is not supported by NetworkManager
Summary: Anaconda's GATEWAY_PING_TIMEOUT value is not supported by NetworkManager
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-16 12:46 UTC by Andrei Stepanov
Modified: 2017-10-26 21:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-26 21:11:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/tmp/syslog (69.97 KB, text/plain)
2017-03-16 12:50 UTC, Andrei Stepanov
no flags Details
/tmp/ifcfg.log (2.14 KB, text/plain)
2017-03-16 12:51 UTC, Andrei Stepanov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 979163 1 None None None 2021-01-20 06:05:38 UTC

Description Andrei Stepanov 2017-03-16 12:46:14 UTC
This bug is about NetworkManager and Anaconda.

Anaconda has boot option: method=http://x.x.x.x/composes/some_rhel6/compose/Workstation/x86_64/os

Anacoda logs has next entry:
1:45:54,391 WARNING NetworkManager: ifcfg-rh:     warning: invalid GATEWAY_PING_TIMEOUT time '60'

Above message is very confusing. 

GATEWAY_PING_TIMEOUT variable should have correct value.

There is more information above message at: https://bugzilla.redhat.com/show_bug.cgi?id=979163#c30

RHEL6.9 compose from 20170316.

How reproducible: always.

Comment 2 Andrei Stepanov 2017-03-16 12:50:08 UTC
Created attachment 1263680 [details]
/tmp/syslog

Search for GATEWAY_PING_TIMEOUT

Comment 3 Andrei Stepanov 2017-03-16 12:51:01 UTC
Created attachment 1263681 [details]
/tmp/ifcfg.log

"grep" for GATEWAY_PING_TIMEOUT

Comment 4 Thomas Haller 2017-10-18 16:16:51 UTC
btw, bug 1128581 [1] changed the timeout to 600 seconds, on RHEL7.

[1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e86f8354a7aa5f8ba95b319f54f70e3e8aa9dbb7


Indeed, the message warning is not very descriptive, but on RHEL6 the range is limited to 0 - 30 seconds.

Comment 5 sushil kulkarni 2017-10-26 21:11:20 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the
Production 3 Phase, Critical impact Security Advisories (RHSAs) and
selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as
they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3
Phase and will be marked as CLOSED/WONTFIX. If this remains a critical
requirement, please contact Red Hat Customer Support to request a
re-evaluation of the issue, citing a clear business justification. Note
that a strong business justification will be required for re-evaluation.


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