Service must always be restarted during an upgrade

The service is unconditionally stopped during the upgrade
prep tasks. There are several conditions that will notify
the handler to restart the service, such as updating the
config file or installing a new version of the rabbitmq
package. It is possible that none of these things happen
resulting in the service not being restarted during an upgrade.
This patch ensures that the service is always restarted
during an upgrade by notifying the restart handler when
the service is sucessfully stopped in the upgrade prep tasks.
Change-Id: I9fbe7806b3531921b90ac91c17b6a07deca2a4d2
(cherry picked from commit b09ac39cbc)
This commit is contained in:
Jonathan Rosser
2024年12月19日 11:53:10 +00:00
committed by Dmitriy Rabotyagov
parent 1afc2a503b
commit 1677a5e19b

View File

@@ -35,3 +35,5 @@
service:
name:rabbitmq-server
state:stopped
notify:
- RabbitMQ start
Reference in New Issue
openstack/openstack-ansible-rabbitmq_server
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.

The note is not visible to the blocked user.