Takuya ASADA

> CI state **`FAILURE`** - https://jenkins.scylladb.com/job/releng/job/Scylla-CI/1967/ Actual error message is: ``` 19:01:11 [224/2946] tar -C build -xvpf /opt/scylladb/dependencies/node_exporter-1.4.0-rc.0.linux-amd64.tar.gz --no-same-owner && rm -rfv build/node_exporter && mv -v build/node_exporter-1.4.0-rc.0.linux-amd64 build/node_exporter 19:01:11 FAILED:...

> Is node_exporter actually vulnerable? It says something about PEM data, which is TLS related. Is it doing anything in that area? Well I haven't checked vulnerable code is used...

@avikivity @yaronkaikov updated to officially released node_exporter 1.4.0.

CI failed because of frozen toolchain is not updated to 1.4.0 yet.

Looks like recent commit #11399 introduce the error, but the change was for generating more user friendly error message, and the target device (/dev/disk/by-uuid/10802a22-9562-4a01-b84f-6722eb44d300) should exists at this point, since...

On #11399, I was thinking `udevadm settle` after `mkfs.xfs` gurantee UUID device file existance (since the command should block the creation finishes), but the SCT result it isn't, at least...

I guess this is enough to avoid this error and also `'systemctl start var-lib-scylla.mount' returned non-zero exit status 1` error on #11359. But if we still get `'systemctl start var-lib-scylla.mount'...

I sent a PR https://github.com/scylladb/scylladb/pull/11666 to fix the issue and waiting for merge

@avikivity ping

@avikivity ping