Public bug reported: When the placement service is supposed to restart in grenade (pike to master) it doesn't actually restart:
http://logs.openstack.org/93/385693/84/check/legacy-grenade-dsvm- neutron-multinode-live- migration/9fa93e0/logs/grenade.sh.txt.gz#_2017-12-05_00_08_01_111 This leads to issues with new microversions not being available: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Unacceptable%20version%20header%3A%201.14%5C%22 This is a latent bug that was revealed, at least in part, by efried's (correct) changes in https://review.openstack.org/#/c/524263/ 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. ** Affects: devstack Importance: Undecided Status: New ** Affects: grenade Importance: Undecided Status: New ** Affects: nova Importance: Undecided Status: New ** Also affects: grenade Importance: Undecided Status: New ** Also affects: devstack Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1736385 Title: placement is not being properly restarted in grenade (pike to master) Status in devstack: New Status in grenade: New Status in OpenStack Compute (nova): New Bug description: When the placement service is supposed to restart in grenade (pike to master) it doesn't actually restart: http://logs.openstack.org/93/385693/84/check/legacy-grenade-dsvm- neutron-multinode-live- migration/9fa93e0/logs/grenade.sh.txt.gz#_2017-12-05_00_08_01_111 This leads to issues with new microversions not being available: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Unacceptable%20version%20header%3A%201.14%5C%22 This is a latent bug that was revealed, at least in part, by efried's (correct) changes in https://review.openstack.org/#/c/524263/ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1736385/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
