What I use to Provision my personal Desktops with Ansible. The goal is to create playbooks and related roles (in other repos) to quickly provision both Fedora and PopOS distributions for my general usage.
On Fedora, when running the snap installs it is possible, especially with a fresh provision on fresh install the snapd service is not up since snapd was just installed. If the service is not up by the time snaps install happens in the playbook you will get an error:
error: too early for operation, device not yet seeded or device model not acknowledged
The work around is to re-run the playbook, by that point snapd will be up.
billwheatley
commented
1 year ago
On Fedora, when running the snap installs it is possible, especially with a fresh provision on fresh install the snapd service is not up since snapd was just installed. If the service is not up by the time snaps install happens in the playbook you will get an error:
The work around is to re-run the playbook, by that point snapd will be up.
True fixes may involve polling the service to see if it up before attempting install, here are some ideas on how to do that https://www.unixcloudfusion.in/2022/07/solved-too-early-for-operation-device.html https://martincarstenbach.wordpress.com/2019/07/23/ansible-tipsntricks-checking-if-a-systemd-service-is-running/
Hack fix would be to separate the snapd install far enough that you be unlikely to see the issue
Related to: Issue #74 and Issue #33