after_group in <file> is not supported in the v3.3+ frontends
Steve pointed out
Following works in branch_v3_2 but not in case of v3.3+ frontends. Basic diff on the creation/lib does not reveal anything so need to investigate thoroughly.
<file absfname="/var/lib/gwms-frontend-scripts/IFFE_script.sh" after_entry="True" after_group="False" const="True" executable="True" untar="False" wrapper="False"> <untar_options cond_attr="TRUE"/> </file>
[root@cmssrv279 gwms-frontend]# service gwms-frontend reconfig Using default Frontend config file: /etc/gwms-frontend/frontend.xml Unexpected error occurred loading the configuration file. Unknown parameter frontend.groups.mu2e_google.*.files.after_group Reconfiguring the frontend [FAILED] that was the error once I took out the after_group line it was fine.
#4 Updated by Marco Mambelli over 3 years ago
- Target version changed from v3_3_2 to v3_2_19
I did test this in the current master (upcoming 3.3.2)
I get no error if the after_group is in a <file> in the general <files> section.
I get the error if the after_group is in a <file> in the <files> section inside into a group.
This behavior makes sense to me if the file is in the group you should not ask to put it after all the groups sections.
The same behavior is in 3.2.
Where was the file section mentioned above?
Either the file section was in a group or the problem has been fixed by merging branch_v3_2
I'm making this a documentation ticket to be more clear in http://glideinwms.fnal.gov/doc.prd/factory/custom_scripts.html to mention that after_group can be used only in the frontend configuration and in the general section.
#5 Updated by Steven Timm over 3 years ago
The <file> section in the original ticket submission was in a group at the time, and still is.
This was not a show stopper because by removing the after_group statement, it had been working fine.
I probably just brought the after_group statement along when I copied that from a different frontend.