Open Stack

> We are trying to do the same to update from Train to Xena, but now
> there is a problem because nova services on the controller node refuse
> to start since they find too old compute nodes (this is indeed a new
> feature, properly documented in the release notes).  As a workaround
> we had to manually modify the "version" field of the compute nodes in
> the nova.services table.
>
> Is it ok, or is there a cleaner way to manage the issue ?

I think this is an unintended consequence of the new check. Can you file
a bug against nova and report the number here? We probably need to do
something here...

Thanks!

--Dan