(Focal) Failure enabling systemd-timesyncd: "service is masked"

[rocodes]

Description

Installing SecureDrop 1.8.0-rc1 on Focal on hardware (NUC7s), I'm consistently encountering an error during the Ensure systemd-timesyncd service is enabled task:

Unable to enable service systemd-timesyncd: Failed to enable unit: Unit file /etc/systemd/system/systemd-timesyncd.service is masked.

Steps to Reproduce

• Install Focal on hardware
• Fresh clone of SD repo, (reuse tor_v3_keys.json)
• Checkout 1.8.0-rc1 and modify install-fpf-repo/...main.yml to use apt-test repo and apt-test key as per QA procedures
• Complete pre-install steps then install from scratch using ./securedrop-admin --force install.

Expected Behavior

1.8.0-rc1 installed on servers

Actual Behavior

On both app and mon:
Unable to enable service systemd-timesyncd: Failed to enable unit: Unit file /etc/systemd/system/systemd-timesyncd.service is masked.

[zenmonkeykstop]

FWIW I did not observe this during my most recent install, and the service is up and running on my boxen.

[rmol]

I am so far unable to reproduce the error; my test run had no problem with Ensure systemd-timesyncd service is enabled.

[conorsch]

I haven't seen this, either. However, it might be worthwhile explicitly setting masked: no on the relevant task: https://github.com/freedomofpress/securedrop/pull/5806/files#diff-ae5be923cdf2cac58831b9ea69297001a39085628927b7c6a55e4a994f41803fR76-R81

[rocodes]

I'm going to reinstall Focal and see if even I can repro. (My reference to "consistently" was on repeated install attempts, but I'll try wiping now)

[rocodes]

I wiped and reinstalled Focal and 1.8.0-rc1 did not reproduce my original issue. Maintainers feel free to close if you wish.

[rmol]

@conorsch I added #5842 to unmask the service. Don't think it's strictly necessary, but wouldn't hurt either, other than the extra review and testing time.