CI builds for first-ansible-playbook example are failing in GitHub Actions

I see:

```
TASK [Ensure chrony is running.] ***********************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service chronyd: Job for chronyd.service failed because the control process exited with error code. See \"systemctl status chronyd.service\" and \"journalctl -xe\" for details.\n"}
```

If I run the example locally (e.g. `playbook=first-ansible-playbook.yml distro=centos7 tests/test.sh`), then I see no errors, and idempotence works too.

I wonder if something else is conflicting with Chronyd inside GitHub Actions' environment?

Start with first-ansible-playbook.yml and run the command shown in tests/test.sh, comparing the local CentOS 7 result with the GitHub Actions environment. Inspect the chronyd service failure and its systemctl or journalctl output; done means the example passes in GitHub Actions and retains idempotence.

Written by the indexing model from the issue text.