alpine and arch sometimes use sha512, main snapd fail to start

Bug #1850914 reported by Zygmunt Krynicki on 2019-11-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
High
Maciej Borzecki

Bug Description

As seen in this Arch Linux AUR thread: https://aur.archlinux.org/packages/snapd/#comment-714427

In some cases, the toolchain uses she-512 based build IDs, making snapd fail to identify snap-seccomp version. It is unclear why this happens. Maciej separately conveyed that a similar issue affected Alpine as well.

The user reported seeing this problem in the logs:

$ sudo journalctl -u snapd.service
...
cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: invalid format of version-info: "6f33567a6d5533534e6273424138556e5a7757582f654153436e383650336a61346537544b673975482f565059786473696e77496b3275724a39755f6d6d2f48314d544863384d51344c417a4c387845717976 2.4.1 8c73f36d3de1f71977107bf6687514f16787f639058b4db4c67b28dfdb2fd3af bpf-actlog"]

Similar issue was reported on Alpine in https://forum.snapcraft.io/t/future-release-to-include-alpine-linux-as-snapd-host/13144/7 the user saw this:

2019/09/11 21:26:31.393539 daemon.go:346: started snapd/unknown (series 16; classic; devmode) alpine/3.11_alpha20190809 (amd64) linux/4.19.68-0-vanilla.

cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: invalid format of version-info: “43426b4f715267684c314d423644714f573165442f4a35455a3865567168457735753651676a6e49572f6431794e714e496a73586a4c5564706f4e3555792f56485079374a4768413054336b78795736704843 2.4.1 8c73f36d3de1f71977107bf6687514f16787f639058b4db4c67b28dfdb2fd3af bpf-actlog”]

Changed in snapd:
assignee: nobody → Maciej Borzecki (maciek-borzecki)
status: Confirmed → In Progress

This should be a part of 2.43 release

Changed in snapd:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers