remote: Andrew (TRIUMF), Borja (monitoring), David Cameron (ATLAS + ARC), David M (FNAL), Doug (BNL), Gianfranco (Bern), Giuseppe (CMS), Julia (WLCG), Maarten (ALICE + WLCG), Mark (LHCb + Birmingham), Matt (Lancaster), Ofer (BNL), Panos (WLCG), Pepe (PIC), Stephan (CMS), Tigran (dCache)
No impact on central services since IAM VOMS was working but unfortunately coincided with an ATLAS tutorial and caused problems for registering new users
Discussion
Maarten:
a big issue was discovered by accident when we tried to understand why one user account kept getting disabled in IAM
VOMS-Admin was hammering the VOMS DB with failing connections
as a protective measure, the DB then banned the VOMS hosts
we needed to keep VOMS-Admin switched off to prevent the more critical VOMS services from being impacted
a quick fix finally became available by Tue late evening
it got implemented and deployed on Wed morning
a proper fix was implemented in the days that followed
CMS
June was rather quiet, few issues at CMS
accidental SAM and HammerCloud dataset deletion at sites, restored quickly
running smoothly with 375k cores
usual production/analysis split of 75% and 25%
significant contribution from HPCs 20k to 70k
main production activity Run 2 ultra-legacy Monte Carlo
impact of Russian invasion/sanctions significant for CMS Tier-1
tape data relocation ongoing
deletion of unused datasets and tape space recovery