Bug 1449296 – Connectivity checking timeout=0 does not disable connectivity checking

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1449296 - Connectivity checking timeout=0 does not disable connectivity checking

Summary:	Connectivity checking timeout=0 does not disable connectivity checking

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	NetworkManager (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Lubomir Rintel
QA Contact:	Desktop QE
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-05-09 10:37 EDT by Lubomir Rintel
Modified:	2017-08-01 05:28 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	NetworkManager-1.8.0-1.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-01 05:28:57 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Proposed patch (901 bytes, text/plain) 2017-05-09 10:37 EDT, Lubomir Rintel	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:2299	normal	SHIPPED_LIVE	Moderate: NetworkManager and libnl3 security, bug fix and enhancement update	2017-08-01 08:40:28 EDT

Groups: None (edit)

Description Lubomir Rintel 2017-05-09 10:37:51 EDT

Created attachment 1277394 [details]
Proposed patch

on the contrary, it checks connectivity continuously.

This is a regression from RHEL 7.3.

Comment 1 Thomas Haller 2017-05-10 06:15:20 EDT

lgtm

Comment 2 Francesco Giudici 2017-05-10 07:44:34 EDT

lgtm

Comment 4 errata-xmlrpc 2017-08-01 05:28:57 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2299

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