[R 2.20] Some VMs stuck in error state when nova-conductor connection to RabbitMQ gets torn down intermittently
Bug #1463070 reported by
amit surana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Won't Fix
|
Medium
|
Ranjeet R | ||
R2.20 |
Won't Fix
|
Medium
|
Ranjeet R | ||
R3.0 |
Won't Fix
|
Medium
|
Ranjeet R | ||
R3.1 |
Won't Fix
|
Medium
|
Ranjeet R | ||
Trunk |
Won't Fix
|
Medium
|
Ranjeet R |
Bug Description
3-5 out of 32 VMs get stuck in error state when launched simultaneously. Seems like nova-compute (on one of those compute nodes) to conductor communication is broken. Ranjeeth has looked at the setup.
Version 2.20 build 34.
Logs are here:
10.84.5.
description: | updated |
tags: | added: snat |
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
To post a comment you must log in.
I see there are RabbitMQ reconnects and because of which some of the VM spawns fail at different places. One way to solve this to retry VM spawns when it fails which would allow the SNAT testing to go through.