Removing cta frontend and xrootd logs from stdout of the pod as kubectl logs is broken and only displays partial logs. xrootd logs are now going in /var/log/cta-frontend-xrootd.log to be collected later in the varlog archive as artifacts.

Compiles without XRDSSI_DEBUG and removes --json option from scripts

So we can see how bash shell strings are being escaped and what actually
appears in the protocol buffer.

Sets retrieve workflow in eos_wfe_scripts back to the old cta command
for now. Try to get simple test to work first.

Copying SSS of taped to the official location (temporary fix, should be created here on the flyx by default)

The installation in the buildtree environment is not useful as all is pre-installed in the image.

condition.

This commit should fail in system tests with a core dump on the
frontend.

avoid file metadata resolution on eos side.

when SSI is not used.

We now automatically find all binaries to symlink into /usr/bin of containers.

Generating backtrace automatically when ctafrontend dies, collect it for artifacts and display it when the namespace gets deleted so that it appears on the Pipeline.

and 1 hour by default.
Previously when cta frontend coredumped, all the files appeared to have
been successfully deleted when it was not the case.
I am now making sure cta client returned with no error to correctly
detect failures.

This is necessary after a system restart if the api server's IP address changed.

sqplus is needed to clean up the database.

preprod workflows