MSPileup: detect active containers with no wmcore_transferor rules

[amaltaro]

Fixes #11578

Status

not-tested

Description

Adds support to a specific use case in the monitoringTask task of the MSPileup, such that if a container is active but it has no wmcore_transferor rules, we will catch this case and update the pileup document accordingly, such that other tasks can properly act on it instead of leaving it in a stale state.

Is it backward compatible (if not, which system it affects?)

YES

Related PRs

None

External dependencies / deployment changes

None

[cmsdmwmbot]

Jenkins results:

• Python3 Unit tests: succeeded
• Python3 Pylint check: failed
  • 1 warnings and errors that must be fixed
  • 2 warnings
  • 4 comments to review
• Pylint py3k check: succeeded
• Pycodestyle check: succeeded

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-WMCore-PR-test/14240/artifact/artifacts/PullRequestReport.html

[amaltaro]

I knew this situation would come with the new WMCore tagging that we came up with a few months ago, and we did not have an answer back then. Here is the current situation.

1. release 2.2.0.2 was the production/stable version.
2. 2.2.0.2_wmagent branch was branched of 2.2.0.2
3. 2.2.0.2_cmsweb branch was branched of 2.2.0.2
4. CMSWEB release was made with 2.2.0.3 from branch 2.2.0.2_cmsweb
5. WMAgent release was made with 2.2.0.4 from branch 2.2.0.2_wmagent (including the same bug fix from the cmsweb branch)

The best option I can think of now is to:
6) CMSWEB release to be made with 2.2.0.5 from branch 2.2.0.2_cmsweb (but note that it won't have any of the patches from the wmagent branch, i.e., 2.2.0.5 will be cut on top of 2.2.0.3 instead of 2.2.0.4)

Just a FYI about this mess, which we need to give further thought for future cases.