Todor Ivanov

hi @amaltaro > In the ENTRYPOINT script: we might have to trap signals At the current stage it is fairly easy for us to trap those signals ... our entry...

Thanks for the hint [Stefano](@belforte), indeed that is something we can do for `WMAgent` as well. I'll give it a try in parallel to an idea or two that also...

As we discussed yesterday during the WMCore meeting, based on my previous experience with this containerization effort, I can point which are the most crucial and with highest priority issues...

hi @amaltaro > I inclined to say that the CI/Jenkins pipeline (issue https://github.com/dmwm/WMCore/issues/11568) should be updated accordingly and before we actually implement this new model in production, otherwise I fear...

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...

ok, Thanks @amaltaro

While working on this solution, I also noticed the cronjobs are even missing within the current containers: ``` (WMAgent-2.3.3) [cmst1@vocms0260:current]$ crontab -l no crontab for cmst1 ``` And I think...

Ok, for the last comment I was partially correct, and partially wrong. The reason for the missing cronjobs is indeed the not exported `$WMA_USER` environment variable.... But actually we now...

@amaltaro We do not change the length of the proxy. It stays 168 hours. What we change here is the time window at which we deem the proxy close it...

hi @amaltaro , but is `AgentStatusWatcher` updating the proxy if expired or it is just throwing an alarm? What I did with my latest commit: https://github.com/dmwm/CMSKubernetes/pull/1476/commits/01aade3e560e68c0a0841fd0706ed4709604fb15 is: * Setting the...