Bug 1368594

Summary:	Unable to create VM's after failing one of the Controllers
Product:	Red Hat OpenStack	Reporter:	Rama <rnishtal>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED NOTABUG	QA Contact:	Prasanth Anbalagan <panbalag>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0 (Liberty)	CC:	aortega, athomas, berrange, dasmith, eglynn, jdonohue, jrist, kchamart, mpryc, rnishtal, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone:	---	Keywords:	ZStream
Target Release:	8.0 (Liberty)	Flags:	eglynn: needinfo? (rnishtal)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-08 21:54:15 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:
Bug Depends On:
Bug Blocks:	1194008, 1295530

Description Rama 2016-08-19 21:18:04 UTC

Description of problem:
After powering off ( removing one of the UCS blades ) one controller out of three, the cluster shows unclean, but recovers after 2 mts.

However could not create VM's upto 10 mts. Able to login to dashboard, 

[stack@osp8-director scripts]$ ./create.sh 
Not enough l3 agents available to ensure HA. Minimum required 2, available 0.
Unable to find router with name 'tenant311'
Unable to find router with name 'tenant311'
Unable to establish connection to http://173.36.215.16:5000/v2.0/tokens

However, the system recovers after 12 mts and vm creation goes fine.
Is this expected to have a 10 minutes of downtime for creating VM's?


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Jason E. Rist 2016-09-21 14:59:52 UTC

Moving to Compute DFG

Comment 5 Eoghan Glynn 2016-11-09 12:22:59 UTC

To analyze this we need full sos-reports, your create.sh script, and more information on the failure mode observed on VM creation.

Comment 6 Kashyap Chamarthy 2018-01-08 21:54:15 UTC

The NEEDINFO from comment#5, hasn't been answered for more than 13 months.  I assume the reporter doesn't see this bug anymore.

If the issue persists, please try it with the latest stable RHOS release, and provide full sosreports from all relevant nodes.