neutron: use crm_resource restart for restarting neutron-l3-ha-service#2116
Merged
Conversation
Member
|
@dirkmueller the gating job still fails with the same symptomps :o( |
Contributor
By default neutron-ha-tool restart is subscribed as delayed so all restarts are queued, So the actual restart happens after chef is done. So may be changing it to not-delayed should help |
When we restart via systemd, it can happen that the service already crashed and then 'service neutron-l3-ha-service status" will (correctly) report that the service isn't running. And then the restart is not being executed due to: INFO: Ignoring restart action for neutron-l3-ha-service service since not running on this node (d52-54-77-77-01-01) which will then later cause a pacemaker failcount. the pacemaker resource restart hopefully does not have this problem.
dirkmueller
force-pushed
the
neutron_hatool
branch
from
3ecea84 to
3615437
Compare
sjamgade
approved these changes
May 9, 2019
rsalevsky
approved these changes
May 9, 2019
Itxaka
approved these changes
May 9, 2019
This was referenced May 9, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When we restart via systemd, it can happen that the service already
crashed and then 'service neutron-l3-ha-service status" will (correctly)
report that the service isn't running. And then the restart is not being
executed due to:
INFO: Ignoring restart action for neutron-l3-ha-service service since not running on this node (d52-54-77-77-01-01)
which will then later cause a pacemaker failcount. the pacemaker
resource restart hopefully does not have this problem.