Loading...

XML

Word

Printable

Release Note Type:
Bug Fix
Release Note Text:

Hide
.A volume quadlet service name no longer fails

Previously, starting the volume service name produced an error similar to the following one:
"Could not find the requested service NAME.volume: host"
With this update, the volume quadlet service name is changed to `basename-volume.service`. As a result, the volume service starts with no errors.

For more information, see link:https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#volume-units-volume[Volume unit] man page.

Show
.A volume quadlet service name no longer fails Previously, starting the volume service name produced an error similar to the following one: "Could not find the requested service NAME.volume: host" With this update, the volume quadlet service name is changed to `basename-volume.service`. As a result, the volume service starts with no errors. For more information, see link: https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#volume-units-volume [Volume unit] man page.
Release Note Status:
Done

Cause: The code was using a volume quadlet service name of basename.volume.

Consequence: Attempting to start this service name would give an error such
as "Could not find the requested service NAME.volume: host"

Fix: The volume quadlet service name is changed to basename-volume.service

Result: The volume service can be started with no errors.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>

is cloned by

RHEL-21402 fix: name of volume quadlet service should be basename-volume.service

links to

link to github pull

RHBA-2023:124808 rhel-system-roles bug fix and enhancement update

mentioned on

Merge request - system roles update 1.23.0-2.9