Bug 1404351

Summary: OCP fails at 5.0%: "[E] ====== Launch OSE Worker 1 VM FAILED! ====== (RuntimeError)"
Product: Red Hat Quickstart Cloud Installer Reporter: Antonin Pagac <apagac>
Component: Installation - OpenShiftAssignee: Dylan Murray <dymurray>
Status: CLOSED ERRATA QA Contact: James Olin Oden <joden>
Severity: unspecified Docs Contact: Derek <dcadzow>
Priority: unspecified    
Version: 1.1CC: arubin, bthurber, dymurray, jmatthew, joden, qci-bugzillas
Target Milestone: ---Keywords: Triaged
Target Release: 1.1   
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-02-28 01:42:16 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:
Attachments:
Description Flags
relevant part of production.log none

Description Antonin Pagac 2016-12-13 16:12:33 UTC
Created attachment 1231272 [details]
relevant part of production.log

Description of problem:
Deployment:
RHV self-hosted with two hypervisors
OCP 1 Master 1 Node

OCP failed at 5%. See attachment for relevant part of production.log.

"
2016-12-13 10:33:02 [app] [W] nil
2016-12-13 10:33:02 [app] [E] VMLauncher: Launch VM for 'rhv-ocp-ose-node1' FAILED
2016-12-13 10:33:02 [app] [E] #
2016-12-13 10:33:02 [foreman-tasks/action] [E] ====== Launch OSE Worker 1 VM FAILED! ====== (RuntimeError)
"

Version-Release number of selected component (if applicable):
QCI-1.1-RHEL-7-20161212.t.2

How reproducible:
Happened to me once

Steps to Reproduce:
1. Start a deployment described above
2. At 5.0% of OCP the deployment fails
3.

Actual results:
Deployment fails

Expected results:
Deployment continues and finishes successfully

Additional info:

Comment 2 Antonin Pagac 2016-12-14 13:48:55 UTC
Failed to reproduce with the same set of HW machines and ISO version. This is not 100% reproducible.

Comment 3 Antonin Pagac 2016-12-15 14:22:54 UTC
Haven't seen this issue with QCI-1.1-RHEL-7-20161214.t.0. I think it was most probably caused by some temporary network issue on my setup, since I can't reproduce it... maybe notabug?

Comment 4 Antonin Pagac 2016-12-19 10:15:57 UTC
Haven't seen this issue with QCI-1.1-RHEL-7-20161215.t.0.

Comment 5 Dylan Murray 2017-01-06 21:49:51 UTC
Have been unable to reproduce as well as of 1/6/17.

Comment 6 John Matthews 2017-01-11 16:30:31 UTC
Moving this to ON_QA since we haven't been able to reproduce.
Please help define reproducer steps or close if no longer applicable

Comment 7 James Olin Oden 2017-01-12 21:56:23 UTC
We haven't seen this in a while.   We are closing it now as verified but if it should show up again we will re-open the bug and enter any new information we find.

Compose: QCI-1.1-RHEL-7-20170111.t.8

Comment 10 errata-xmlrpc 2017-02-28 01:42:16 UTC
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/RHEA-2017:0335