OpenStack Compute (nova)

  1. Bug #1431201
  2. Comment #1

Comment 1 for bug 1431201

Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote : Re: kilo controller cann't conduct juno compute nodes

So, there are 2 problems :
 - old Juno RT is using the conductor API instead of using Objects, so that's directly proxying on top of DB API. Instead of reverting https://github.com/openstack/nova/commit/83b64ceb871b1553b1bb1e0bb9270816db892552 I'm in favor of adding a logic in the conductor manager method which would check if the compute_node field is present, and if not re-add it. That way, it would allow to go on and keep removed the nested compute_node field for Kilo nodes while Juno nodes would still work

 - the second stack is a little bit weird for me, could you please give me a better stacktrace so I could understand what's wrong with the second commit you mentioned ?