Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1527389 - [3.6] Nodes becomes NotReady, when status update connection is dropped/severed to master, causing node to wait on 15min default net/http timeout before trying again.
[3.6] Nodes becomes NotReady, when status update connection is dropped/severe...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master (Show other bugs)
3.6.1
Unspecified Unspecified
unspecified Severity urgent
: ---
: 3.6.z
Assigned To: Maciej Szulik
Wang Haoran
: Reopened
: 1543086 (view as bug list)
Depends On: 1464653
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-19 05:37 EST by Nicolas Nosenzo
Modified: 2018-04-12 02:00 EDT (History)
19 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Rate limiting is causing some connection to master from node to be dropped. Consequence: Node status is not updated properly. Fix: Use a separate (non-limited) client for node status. Result: The node status should be properly saved in the master.
Story Points: ---
Clone Of: 1464653
Environment:
Last Closed: 2018-04-12 01:59:59 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1106 None None None 2018-04-12 02:00 EDT

  None (edit)
Comment 11 Maciej Szulik 2018-03-08 05:15:02 EST
*** Bug 1543086 has been marked as a duplicate of this bug. ***
Comment 14 errata-xmlrpc 2018-04-12 01:59:59 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/RHBA-2018:1106

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