error: connecting to /run/bootupd.sock

[goshansp]

On Fedora IoT (unmodified) and Silverblue (own spin) I get error: connecting to /run/bootupd.sock: ENOENT: No such file or directory when executing sudo bootupctl status. I don't update IoT automaticallly, Silverblue is supposed to compose daily.

NOK: Silverblue https://pagure.io/fork/goshansp/workstation-ostree-config

[hp@green ~]$ sudo bootupctl status
error: connecting to /run/bootupd.sock: ENOENT: No such file or directory
[hp@green ~]$ rpm -qa bootupd
bootupd-0.2.8-3.fc37.x86_64
[hp@green ~]$ rpm-ostree status
State: idle
Deployments:
● goshansp:fedora/37/x86_64/silverblue
                  Version: goshansp-37.20230327.1 (2023-03-27T14:21:50Z)
                   Commit: 67fefc484b8a3732e809881108060a4ee3a9cccc99eefc4eb6afb7c9f6cf08ac

NOK: IoT

[hp@rpi01 ~]$ sudo bootupctl status
error: connecting to /run/bootupd.sock: ENOENT: No such file or directory
[hp@rpi01 ~]$ rpm -qa bootupd
bootupd-0.2.8-3.fc37.aarch64
[hp@rpi01 ~]$ rpm-ostree status
State: idle
Deployments:
● fedora-iot:fedora/stable/aarch64/iot
                  Version: 37.20230330.0 (2023-03-30T13:39:02Z)
               BaseCommit: 6a3886990fb729818409d884e083f6581a311627d208f00e9dfe9664bad9c1ee
             GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
          LayeredPackages: bootupd git python-pip python3-libgpiod

OK: On the FCOS fedora:fedora/x86_64/coreos/next 38.20230322.1.0 with bootupd-0.2.9-1.fc38.x86_64 it is working fine.

I currently assume that the issue is present on stable / 0.2.8 and has been fixed in next / 0.2.9.

[goshansp]

Manual starting of bootupd.socket seems to solve the issue for bootupd-0.2.8-3.fc37.x86_64 but not for bootupd-0.2.8-3.fc37.aarch64:

hp@rpi02 ~]$ sudo systemctl enable bootupd.socket; sudo systemctl start bootupd.socket 
[hp@rpi02 ~]$ sudo bootupctl status
error: internal error: Failed to find ESP device

I'll wait for 0.2.9 - also rewriting grub.cfg can workaround the issue i which brought me here.

[goshansp]

after upgrade to f38 / 0.2.9 the issue is gone.