Bug 1572492 - 3.9 Installation or scaleup fails on task restart dnsmasq with timeout error
Summary: 3.9 Installation or scaleup fails on task restart dnsmasq with timeout error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.9.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-27 07:08 UTC by Priyanka Kanthale
Modified: 2018-05-16 08:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-16 08:03:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Priyanka Kanthale 2018-04-27 07:08:58 UTC
Description of problem:

During the installation or doing a scaleup, the teamd processes of the node after the task restart NetworkManager are stopped. As the teaming is configured as loadbalancer, causes the communication really slow and the task will be failed because of timeout.

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
RUNNING HANDLER [openshift_node : restart dnsmasq] ******************************************************************************************************************************************************************************************
changed: [in03.example.com]
fatal: [in04.example.com]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}
fatal: [in01.example.com]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}
fatal: [master03.example.com]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: \r\n"}
changed: [master02.example.com]
changed: [master01.example.com]

Expected results:

Additional info:


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