nova-compute in down state (servicegroup_driver=mc)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Description
===========
Nova services such as:
nova-
nova-conductor
nova-consoleauth
nova-metadata-api
nova-novncproxy
nova-scheduler
> Running on controller nodes (api's) on python3
nova-compute running on python2 on hypervisors hosts (qemu-kvm based)
IF servicegroup_
nova service-list see nova-compute nodes in down state
BUT
IF servicegroup_
nova service-list see nova-compute nodes in up state
ALSO
IF servicegroup_
nova service-list see nova-compute nodes in up state
Steps to reproduce
==================
1.Run
nova-
nova-conductor
nova-consoleauth
nova-metadata-api
nova-novncproxy
nova-scheduler on python3
Run nova-compute on python2
2. Set servicegroup_
3. Execute nova service-list
Expected result
===============
All nova services in actual up state
Actual result
=============
nova-compute in down state
Environment
===========
nova-manage --version
19.3.2
Logs & Configs
==============
nova-compute -> rabbitmq (there is no connection errors, rabbit available from hosts)
___
nova-conductor logs:
Apr 13 08:59:08 api2 nova-conductor[
___
nova-api:
e27454b47c0b360
__
So, I'm a little confused, because there is no Rabbit connection problems (one of possible reason with this behaviour)
I guess problem connected with:
nova-api - memcached - nova-compute
I'll appreciate any help with debug.
AFAIK we don't really test the memcache driver on the ServiceGroup API, are you able to see the nova-compute correctly reporting to memcache its status ?