some autopkgtests, like 'snapd' and 'docker.io', rely on snaps in their autopkgtests. Recently, something happened and those autopkgtests now do not have the 'core' snap installed - or, it's installed, but 'broken'.
Specifically, there is no /snap/core/ so no snaps can run, since they rely on the core snap for their interpreter (/snap/core/current/lib64/ld-linux-x86-64.so.2).
[impact]
some autopkgtests, like 'snapd' and 'docker.io', rely on snaps in their autopkgtests. Recently, something happened and those autopkgtests now do not have the 'core' snap installed - or, it's installed, but 'broken'.
Specifically, there is no /snap/core/ so no snaps can run, since they rely on the core snap for their interpreter (/snap/ core/current/ lib64/ld- linux-x86- 64.so.2) .
[test case]
look at any of the recent snapd autopkgtests, e.g.: /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- cosmic/ cosmic/ amd64/s/ snapd/20190410_ 125933_ 3cfed@/ log.gz
https:/
+ /snap/bin/go get -u github. com/snapcore/ spread/ cmd/spread 3540/gowrapper: line 3: /snap/go/ 3540/bin/ go: No such file or directory
/snap/go/
[regression potential]
TBD; fix unknown
[other info]
this might only be happening on cosmic, although the bionic tests are failing as well, but slightly differently, e.g.:
https:/ /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- bionic/ bionic/ amd64/s/ snapd/20190409_ 154344_ 0e7ed@/ log.gz
+ snap list
core 6673 stable canonical* broken
+ exit 1