Bug 1572492

Summary: 3.9 Installation or scaleup fails on task restart dnsmasq with timeout error
Product: OpenShift Container Platform Reporter: Priyanka Kanthale <pkanthal>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED NOTABUG QA Contact: Johnny Liu <jialiu>
Severity: low Docs Contact:
Priority: low    
Version: 3.9.0CC: aos-bugs, jokerman, mmccomas, wmeng
Target Milestone: ---   
Target Release: 3.9.z   
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: 2018-05-16 08:03:09 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:

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: