Set CALIB_RCT_UPDATER to 0 if disabled

[davidrohr]

No description provided.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2022-pp-apass4
async-2023-pbpb-apass
async-2023-pp-apass1
async-data
async-mc
async-2022-pp-apass6-2023-PbPb-apass2

[chiarazampolli]

Hello @davidrohr ,
In async, we now have:

/cvmfs/alice.cern.ch/el9-x86_64/Packages/O2DPG/daily-20240409-0200-1/DATA/common/setenv_calib.sh: line 253: CALIB_RCT_UPDATER: unbound variable

Does this PR fix it? Yesterday I did not see it in my tests, it must have been something that sneaked in after I updated to dev in the morning.
Chiara

[davidrohr]

@chiarazampolli : Yes, it should fix it. A fix for a problem at P2 which was commited yesterday was incomplete.

[chiarazampolli]

Ok, then I need to wait for a new build for async...
I merged my PR since with my dev (from yesterday morning) all was good. Was this not spotted in any CI?

[shahor02]

What was the problem at P2? Adding RCT_UPDATER passed fullCI.

[davidrohr]

SYNCMODE=1 was not set in production.desc, which let to different barrel TF calib datatype spects in calib-workflow.sh and aggregator-workflow.sh.
In some cases, e.g. TPC only, this could lead to one thinking the RCT_UPDATER is present, the other not, and an output proxy was created without an input proxy.
It was not seen in FullCI, since the FullCI actually runs the calib parts, but in the same workflow, and without the proxies.