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.

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

For cta-taped.conf and cta-frontend.conf use the same parameter
ObjectStore BackendPath .......

Preparing eos instance and eos workflows for preprod and SSI, so that we can test both SSI and non SSI workflows on the same cta instance, just in 2 different EOS folders.

Adding cta-ci-ceph-luminous repository to avoid breaking all the branches with no versionlock on ceph or preprod that would automatically upgrade to luminous with distrosync otherwise.
I need a new repo until everyone catches up.
Then this repo can be removed and its packages moved to the ceph cache repo.

repository (resolution order is protected > priority > versionlock).
Adding versionlock on xrootd and others in the build process to make
sure we have the same version in build_rpm and ci runs

- CTA core dumps for CTA are now available as artifacts

We can now get data from a different source (/dev/zero or a file). This helps test where mhvtl space is tight
(so compression can be efficient).