The cvmfs mount was originally needed because the image did not have condition data access and the dbs were not on eospublic as they are now (/eos/opendata/cms/conddb/selection-for-containers/).
When running on 2011 files in November 2022, the cvmfs was unstable made the workflow fail so the db cp was updated to copy from eospublic. Now the access is mixed, i.e. the original base is taken from cvmfs but the database copy is from eospublic.
Clean this up. In principle, a cvmfs mount is not needed, but the cvmfs access has the advantage of not being restricted to OD condition data.
The cvmfs mount was originally needed because the image did not have condition data access and the dbs were not on eospublic as they are now (/eos/opendata/cms/conddb/selection-for-containers/).
When running on 2011 files in November 2022, the cvmfs was unstable made the workflow fail so the db cp was updated to copy from eospublic. Now the access is mixed, i.e. the original base is taken from cvmfs but the database copy is from eospublic.
Clean this up. In principle, a cvmfs mount is not needed, but the cvmfs access has the advantage of not being restricted to OD condition data.