remediation and verification for systemd services

[rjschwei]

Share the context

With cd7b4ab logrotate remediation and check was switched to rely on systemd in SLE. Meaning remediation runs systemctl enable and systemctl start and then the verification step runs systemd status. The rules for firewalld follow the same concept.

This creates a problem when applying remediation in a construct when systemd is not running. For example the building of cloud images in an offline fashion. While the remediation step works, i.e. systemctl enable will succeed the starting systemctl start and verification systemctl status will fail.

Of course in a system that is running and where a user runs remediation we want to have the service started and then checked that it is really running. Preferably we'd have things set up to satisfy both environments

Description of problem:

remediation fails partially and verification fails outright. The result is that we need to remove rules that we would like to have pre-applied in the images that we build.

Proposed change:

Have a change for rules that use systemd in a way that checks first if systemd is running could be simply pidof systemd if this returns something, i.e. systemd is running proceed with systemctl start during the remediation and then systemctl status during the verification step. If systemd is not running skip systemctl start during remediation and in the verification check that the proper symlinks were created.

References: