Open todor-ivanov opened 6 months ago
The latest checks of the logs of MSUnmerged
related to T2_CH_CERN
turned out to show negative results:
2024-05-13 11:18:30,679:DEBUG:MSUnmerged: RSE: T2_CH_CERN, Dir: /store/unmerged/Run3Summer23NanoAODv12/TTto4Q-2Jets_TuneCP5_13p6TeV_amcatnloFXFX-pythia8/NANOAODSIM/130X_mcRun3_2023_realistic_v14-v3, delResult: [GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
GError('DavPosix::unlink HTTP 403 : Permission refused ', 1),
I am now setting up yet another manual cleanup in order to figure out if it is a certificate or a proxy issue (meaning if it is the DN of the cert that is not allowed access or it is a missing role in the proxy itself involved here.
@todor-ivanov as discussed in today's WMCore meeting - and now with Andrea/Dario - we think we can come back to this item in October (unless Ops reach out to us asking for a urgent cleanup). So I am moving this back to ToDo for now. Thanks
ok, Thanks @amaltaro
Impact of the new feature MSUnmerged for T2_CH_CERN
Is your feature request related to a problem? Please describe. This was a long discussion and several wrong paths taken in order to fix those Access issues at T2_CH_CERN. The full details are in the following Jira: CMSVOC-491 and SNOW: RQF2634963 tickets
Now after those are finally solved thanks to the effort of many people involved into those two tickets above (Thanks to all of them btw) we are to test the access and re-enable the MSUnmerged Service for T2_CH_CERN.
Describe the solution you'd like Enable T2_CH_CERN in the list of RSE cleaned by MSUnmerged
Describe alternatives you've considered None
Additional context None