virtlockd service should be restarted/reloaded when virtlockd.conf is changed

Bug #1979894 reported by Takashi Kajinami
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-nova
Fix Released
Medium
Takashi Kajinami

Bug Description

The virtlockd service is not restarted after virtlockd.conf is updated.
We should restart/reload the service so that the change in config file is picked up by it.

Changed in puppet-nova:
importance: Undecided → Medium
assignee: nobody → Takashi Kajinami (kajinamit)
Changed in puppet-nova:
status: New → In Progress
Revision history for this message
Takashi Kajinami (kajinamit) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-nova (master)

Reviewed: https://review.opendev.org/c/openstack/puppet-nova/+/847645
Committed: https://opendev.org/openstack/puppet-nova/commit/aaf5bcf23ad467096637c7a99fd9ca772c6fb57b
Submitter: "Zuul (22348)"
Branch: master

commit aaf5bcf23ad467096637c7a99fd9ca772c6fb57b
Author: Takashi Kajinami <email address hidden>
Date: Sun Jun 26 07:12:47 2022 +0900

    Ensure virtlockd is restarted when virtlockd.conf is modified

    ... so that change in virtlockd.conf is picked up by the service.

    Closes-Bug: #1979894
    Change-Id: I490ab541bc0f0e27280eaeb72c198efa7b9ffdea

Changed in puppet-nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-nova 21.0.0

This issue was fixed in the openstack/puppet-nova 21.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.