HTTP staging tests with FTS

This ticket will track progress of HTTP REST test with FTS implementation.

Test setup

CTA team provides one kubernetes test instance for FTS team to test HTTP workflows with the following constraints:

• GSI authentication no token
• accessible from standard FTS public instances, usually fts3-devel and fts3-pilot

Initially this box was ctadevfts.cern.ch, but the root FS exploded (see INC3274784), therefore ctadevjulien.cern.ch was used instead.

First test 221019

Using 4.7.12-1 CTA version with EOS4.

100k files have been archived by FTS but staging failed with WFE ERRORs.

After this, we could not manually stage a single file (one at a time) without getting the same WFE error.

Restarting the MGM allowed to stage individual files again.

Second test 221021

@jleduc populate 1M files on eosctafst0011.cern.ch stress test CTA CI machine using cta v4.7.12.

Docker explodes when launching Hostnetwork type pods