Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1432941

Summary: Anaconda's GATEWAY_PING_TIMEOUT value is not supported by NetworkManager
Product: Red Hat Enterprise Linux 6 Reporter: Andrei Stepanov <astepano>
Component: NetworkManagerAssignee: sushil kulkarni <sukulkar>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9CC: atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-26 21:11:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/tmp/syslog
none
/tmp/ifcfg.log none

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.