placement is not being properly restarted in grenade (pike to master)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Undecided
|
Unassigned | ||
devstack |
Invalid
|
Undecided
|
Chris Dent | ||
grenade |
Fix Released
|
Undecided
|
Chris Dent |
Bug Description
When the placement service is supposed to restart in grenade (pike to master) it doesn't actually restart:
This leads to issues with new microversions not being available:
This is a latent bug that was revealed, at least in part, by efried's (correct) changes in https:/
It looks like a bad assumption is being made somewhere in the handling of the systemd unit files: a 'start' when it is already started is success, but does not restart (thus new code is not loaded).
We can probably fix this by using the 'restart' command instead of 'start':
restart PATTERN...
Restart one or more units specified on the command line. If the units are not running yet, they will be started.
Adding grenade and devstack as relate projects as the fix is presumably in devstack itself.
Fix proposed to branch: master /review. openstack. org/525533
Review: https:/