Applying metadata segfaults

[saschatimme]

We see segmentation fault when applying metadata from a github action:

{"level":"info","msg":"Applying metadata...","time":"2022-01-10T17:45:01Z"}
21
time="2022-01-10T17:45:02Z" level=fatal msg="error applying metadata \ncannot build actions from project: error parsing metadata \nobject: actions\nfile: actions.yaml\nerror: error in converting sdl to metadata: signal: segmentation fault (core dumped): /github/home/.hasura/cli-ext/v2.0.9/cli-ext-730925829/cli-ext: /usr/lib/libstdc++.so.6: no version information available (required by /github/home/.hasura/cli-ext/v2.0.9/cli-ext-730925829/cli-ext

Digging into the build of the action container I see

2022-01-10T17:44:44.0128890Z Step 9/14 : RUN apk add --no-cache curl bash libstdc++ jq
2022-01-10T17:44:44.0305814Z  ---> Running in f22c095441c3
2022-01-10T17:44:44.3144479Z fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/main/x86_64/APKINDEX.tar.gz
2022-01-10T17:44:44.4449166Z fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/community/x86_64/APKINDEX.tar.gz
2022-01-10T17:44:44.6575350Z (1/12) Installing ncurses-terminfo-base (6.3_p20211120-r0)
2022-01-10T17:44:44.6727502Z (2/12) Installing ncurses-libs (6.3_p20211120-r0)
2022-01-10T17:44:44.6910963Z (3/12) Installing readline (8.1.1-r0)
2022-01-10T17:44:44.7070337Z (4/12) Installing bash (5.1.8-r0)
2022-01-10T17:44:44.7328750Z Executing bash-5.1.8-r0.post-install
2022-01-10T17:44:44.7353334Z (5/12) Installing ca-certificates (20191127-r7)
2022-01-10T17:44:44.7633146Z (6/12) Installing brotli-libs (1.0.9-r5)
2022-01-10T17:44:44.7821824Z (7/12) Installing nghttp2-libs (1.46.0-r0)
2022-01-10T17:44:44.7958302Z (8/12) Installing libcurl (7.80.0-r0)
2022-01-10T17:44:44.8135866Z (9/12) Installing curl (7.80.0-r0)
2022-01-10T17:44:44.8293533Z (10/12) Installing oniguruma (6.9.7.1-r0)
2022-01-10T17:44:44.8505042Z (11/12) Installing jq (1.6-r1)
2022-01-10T17:44:44.8725818Z (12/12) Installing libstdc++ (10.3.1_git20211027-r0)
2022-01-10T17:44:44.9007027Z Executing busybox-1.34.1-r3.trigger
2022-01-10T17:44:44.9043636Z Executing ca-certificates-20191127-r7.trigger
2022-01-10T17:44:44.9411775Z Executing glibc-bin-2.34-r0.trigger

wheres our last successful run had

2022-01-10T07:32:01.0115679Z Step 9/14 : RUN apk add --no-cache curl bash libstdc++ jq
2022-01-10T07:32:01.0374367Z  ---> Running in 83ba1d8d1007
2022-01-10T07:32:01.3500892Z fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/main/x86_64/APKINDEX.tar.gz
2022-01-10T07:32:01.4700518Z fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/community/x86_64/APKINDEX.tar.gz
022-01-10T07:32:01.7084359Z (1/12) Installing ncurses-terminfo-base (6.3_p20211120-r0)
2022-01-10T07:32:01.7207163Z (2/12) Installing ncurses-libs (6.3_p20211120-r0)
2022-01-10T07:32:01.7355017Z (3/12) Installing readline (8.1.1-r0)
2022-01-10T07:32:01.7554953Z (4/12) Installing bash (5.1.8-r0)
2022-01-10T07:32:01.7791060Z Executing bash-5.1.8-r0.post-install
2022-01-10T07:32:01.7811632Z (5/12) Installing ca-certificates (20191127-r7)
2022-01-10T07:32:01.8028805Z (6/12) Installing brotli-libs (1.0.9-r5)
2022-01-10T07:32:01.8201841Z (7/12) Installing nghttp2-libs (1.46.0-r0)
2022-01-10T07:32:01.8374849Z (8/12) Installing libcurl (7.80.0-r0)
2022-01-10T07:32:01.8523015Z (9/12) Installing curl (7.80.0-r0)
2022-01-10T07:32:01.8646382Z (10/12) Installing oniguruma (6.9.7.1-r0)
2022-01-10T07:32:01.8799539Z (11/12) Installing jq (1.6-r1)
2022-01-10T07:32:01.9002994Z (12/12) Installing libstdc++ (10.3.1_git20211027-r0)
2022-01-10T07:32:01.9819847Z Executing busybox-1.34.1-r3.trigger
2022-01-10T07:32:01.9859895Z Executing ca-certificates-20191127-r7.trigger
2022-01-10T07:32:02.0250041Z Executing glibc-bin-2.33-r0.trigger
2022-01-10T07:32:02.0266519Z �/usr/glibc-compat/sbin/ldconfig: /usr/glibc-compat/lib/ld-linux-x86-64.so.2 is not a symbolic link

Full failed log here

So I think the github action environment got updated and broke things.

[andynaguyen]

We are also seeing this error in our github action workflows @tibotiber

[neoplastic]

Yup, saw this issue as well, had to perform metadata changes from my machine to servers to fix issues of downtime... 😅

[Alan-Zhao-908]

Yep we see this error as well. Any recommended fixes?

[tibotiber]

Hi all, thanks for reporting this so quickly. I'm quite sure this must be linked to the update 19h ago of the base docker image used. See Docker-Hub-frolvlad/docker-alpine-glibc#54. I've released v2.1 which explicitly use the previous version.

I hope this fixes the issue but i'm not in a position to test, so please provide feedback :).

Also thanks @saschatimme for the great debugging here, really made the fix easier.

[dyersituations]

@tibotiber We targeted the previous Docker image as well in our fork (frolvlad/alpine-glibc:glibc-2.33), and it worked in our pipeline, so you should be good.

[tibotiber]

Thanks for the quick feedback @dyersituations. I'll close this and anyone feel free to reopen if the issue persists.

[neoplastic]

Thanks everyone, this is working now.