Bug 1368594 - Unable to create VM's after failing one of the Controllers
Summary: Unable to create VM's after failing one of the Controllers
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Eoghan Glynn
QA Contact: Prasanth Anbalagan
URL:
Whiteboard:
Depends On:
Blocks: 1194008 1295530
TreeView+ depends on / blocked
 
Reported: 2016-08-19 21:18 UTC by Rama
Modified: 2023-09-14 03:29 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-08 21:54:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.

Comment 7 Red Hat Bugzilla 2023-09-14 03:29:50 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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