There is currently no way to fingerprint the storage role as it does not outright "own" any config files.

This proposes to write the fingerprint # system_role:storage to /etc/fstab every time the storage role is run, if it is not already present.

Pros:

• /etc/fstab is already collected by sosreports et. al. so it would 'Just Work'
• system role already writes /etc/fstab in many cases

Cons:

• if the fingerprint does not already exist, and the system role doesn't otherwise make any changes to the system, the change to /etc/fstab will be reported as a change - this may be ok - but we can suppress this if necessary - it should be a rare case

Acceptance Criteria

• storage role has a task to write fingerprint to /etc/fstab
• storage role has an automated test to check for fingerprint in /etc/fstab - can add task to existing test e.g. tests_default.yml, or create new test - see https://github.com/linux-system-roles/template/blob/main/tests/tests_default.yml#L9 for how to check - probably want to skip Ansible Managed checking

rhn-support-briasmit spetros@redhat.com rhn-engineering-nkinder dlehman@redhat.com vtrefny@redhat.com japokorn@redhat.com