Closed mmascher closed 10 months ago
Describe the bug The CMS factory query expression in the frontend uses an attribute named GLIDEIN_Retire_Time_Spread The attibute is set in the global section of the factory configuration as:
GLIDEIN_Retire_Time_Spread
<attr name="GLIDEIN_Retire_Time_Spread" const="True" glidein_publish="False" job_publish="False" parameter="True" publish="True" type="int" value="7200"/>
and then overridden on a handful of entries. With the 3.10.5 version the attribute was available in the collector:
[mmascher@vocms0207 ~]$ condor_status -any -af GLIDEIN_Retire_Time_Spread -const 'mytype=="glidefactory"'|sort |uniq -c 6 600 227 7200
With the latest version it is not anymore:
[mmascher@vocms0205 glideinwms]$ condor_status -any -af GLIDEIN_Retire_Time_Spread -const 'mytype=="glidefactory"'|sort |uniq -c 6 600 3 7200 234 undefined
It is only published for the entries that defines it in their list of attributes.
To Reproduce Set a global attribute as above and verify it does not get publishes as a glidefactory classad.
Expected behavior The attribute should be published.
Info (please complete the following information):
I think this is caused by #387. I'm not expecting this to happen w/o that patch
You are right Marco, apologies
Describe the bug The CMS factory query expression in the frontend uses an attribute named
GLIDEIN_Retire_Time_Spread
The attibute is set in the global section of the factory configuration as:and then overridden on a handful of entries. With the 3.10.5 version the attribute was available in the collector:
With the latest version it is not anymore:
It is only published for the entries that defines it in their list of attributes.
To Reproduce Set a global attribute as above and verify it does not get publishes as a glidefactory classad.
Expected behavior The attribute should be published.
Info (please complete the following information):