_determine_version_cap fails with MessagingTimeout when starting nova-compute
Bug #1631918 reported by
John Garbutt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Medium
|
Unassigned |
Bug Description
On a fresh deployment, there are issues when starting up nova-compute, before nova-conductor has started responding to RPC requests.
The first is a MessagingTimeout in the _determine_
This cases the process to exit, but it doesn't seem to quite fully exit the process.
It seems like this happens only when CONF.upgrade_
This was spotted in this OSA change:
https:/
Changed in nova: | |
assignee: | nobody → John Garbutt (johngarbutt) |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
To post a comment you must log in.
Related fix proposed to branch: master /review. openstack. org/384428
Review: https:/