Keys enrollment notification despite having done it already

[bitsByB]

Describe the bug

I enrolled UB keys 10 days ago but I'm receiving the same notification today.
https://universal-blue.discourse.group/t/mokutil-list-enrolled-explanation/4266

What did you expect to happen?

I expected to not have this notification again.

Output of rpm-ostree status

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:4869bf3855d1c06e49ce59c7365e970454c6cfbafbc30b199f87770f43001ec7
                  Version: 40.20241006.0 (2024-10-07T05:35:01Z)
                     Diff: 6 upgraded, 5 removed, 5 added

● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:d0432b83a95d9937ad1000cb25247319eb3ccd95b0f34b5922f307d87ba3f8b2
                  Version: 40.20241006.0 (2024-10-06T20:12:05Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:2993741c56df1f6fe00a7d308fd4f53de3dee4b3e9a14599d17c9f5b6f5181fc
                  Version: 40.20241004.0 (2024-10-05T22:56:42Z)

Output of groups

wheel lxd libvirt incus-admin docker

Extra information or context

No response

[bitsByB]

Getting it again today.

[dosubot]

Hi, @bitsByB. I'm Dosu, and I'm helping the bluefin team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• You reported receiving repeated notifications to enroll UB keys despite completing the process 10 days ago.
• System status and group information were provided, but no feedback or resolution has been given.
• You have indicated that the issue persists.

Next Steps:

• Please let us know if this issue is still relevant to the latest version of the bluefin repository by commenting here to keep the discussion open.
• If there is no further activity, this issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!