Frontend reports incorrect ReqMaxGlideins to the factory
Until v3_2_12, ReqMaxGlideins in the glideclient classad indicated max running glideins a frontend would need to request. However, with the accounting overhaul in frontend in v3_2_13, the semantics was accidentally changed and this classad attribute started reporting how many running glideins you need. As a result this was always much lower than what it should be. Factory compares this number with already running glideins and concludes that we already have enough glideins and does not submit any more.
#1 Updated by Parag Mhashilkar over 3 years ago
On further investigation with Marco. This only impacts accounting for a site where there is a single static slot created by a glidein.
RemoteHost from a running job following valid formats
- glidein with 1 static N core slot: glidein_XXXXX_XXXXX@fqdn
- glidein with N static M core: slotN@glidein_XXXXX_XXXXX@fqdn
- glidein with N static M core: slotN_X@glidein_XXXXX_XXXXX@fqdn
glidein_id is glidein_XXXXX_XXXXX@fqdn
countRealRunning() in glideFontendLib was not handling the first format correctly where slot* prefix is missing.