Project

General

Profile

Bug #23261

Factory could start with Globus GT2 entries

Added by Marco Mambelli 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
09/11/2019
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Raconfig and upgrade are failing if there are active Globus GT2 entries, start is not.
After an upgrade a factory could be started w/o running or with failing upgrade/reconfig , it uses the old configuration.
So if it includes Globus GT2 entries this could cause a problem.

History

#1 Updated by Marco Mambelli 2 months ago

  • Assignee changed from Marco Mambelli to Lorena Lobato Pardavila
  • Status changed from New to Feedback
Changes are in v35/23261
Adding the test in fact_chown_check that is launched on start I found and fixed 2 bugs:
  • fact_chown_check was not started automatically on SL6 (systemctl gwms-factory start is not passing the parameter)
  • the test is always failing if there are no condor jobs in the queue

#2 Updated by Lorena Lobato Pardavila 2 months ago

Tests done in sl6 and sl7.

  • sl6
[root@fermicloud332 glideinwms]# service gwms-factory reconfig
Using default factory config file: /etc/gwms-factory/glideinWMS.xml
Shutting down GlideinWMS Factory gfactory_instance@gfactory[  OK  ]:
Reconfiguring the factory The grid type 'gt2' is no longer supported. Review the attributes of the entry TEST_ENTRY
                                                           [FAILED]
.. starting factory with old configuration file
*/sbin/runuser: unrecognized option '--quiet'
Try `/sbin/runuser --help' for more information.*
The Factory is not ready for 3.5. Please run /usr/bin/fact_chown_check for more details.
To disable this check remove the --check_35_ready option from the gwms-factory.service file
and remove GWMS_CHECK_35_READY from /etc/sysconfig/gwms-fac[FAILED]
[root@fermicloud332 glideinwms]# vim /etc/rc.d/init.d/gwms-factory
[root@fermicloud332 glideinwms]# vim /etc/rc.d/init.d/gwms-factory

That message should not appear, as it's coming from --quiet command. If I remove that part, I should see a lot of messages:

'Loading configuration file /etc/gwms-factory/glideinWMS.xml
Checked ownership (gfactory) of client and proxies directories. Passed
Checked Owner of 0 jobs
Found that jobs Owner are:
All the jobs Owner should be gfactory instead
Please, make sure to run the fact_chown script. More details athttps://glideinwms.fnal.gov/doc.dev/factory/configuration.html#single_user
The Factory is not ready for 3.5. Please run /usr/bin/fact_chown_check for more details.
To disable this check remove the --check_35_ready option from the gwms-factory.service file
and remove GWMS_CHECK_35_READY from /etc/sysconfig/gwms-fac[FAILED]
Marco already pushed the changes correcting it and improving the messages .
  • sl7

In this case, it doesn't complain when startup.

root@fermicloud039 ~]# /usr/sbin/gwms-factory reconfig
Using default factory config file: /etc/gwms-factory/glideinWMS.xml
Reconfiguring the factory The grid type 'gt2' is no longer supported. Review the attributes of the entry TEST_ENTRY
                                                           [FAILED]
[root@fermicloud039 ~]# /usr/sbin/gwms-factory reload
MUST SUPPLY A PID WITH THIS ARGUMENT
[root@fermicloud039 ~]# /usr/sbin/gwms-factory
Usage: gwms-factory {start|stop|restart|status|info|reconfig|down|up|infosysdown|statusdown}
    gwms-factory reconfig [NEW_XML_CONFIG_FILE] [-fix_rrd] [update_default_cfg] [{yes|no}] [-comment COMMENT] [-force_delete]
    gwms-factory {down|up} -entry factory|entries|ENTRY_NAME [-delay DELAY] [-frontend SEC_NAME] [-security SEC_CLASS|All] [-comment COMMENT]
    gwms-factory infosysdown [-delay DELAY] [-frontend SEC_NAME] [-security SEC_CLASS|All] [-comment COMMENT]
    gwms-factory statusdown -entry factory|entries|ENTRY_NAME [-delay DELAY]

[root@fermicloud039 ~]# /usr/sbin/gwms-factory start
Starting GlideinWMS Factory gfactory_instance@gfactory_serv[  OK  ]
[root@fermicloud039 ~]#

#3 Updated by Marco Mambelli 2 months ago

Updated w/ feedback.
Fixed the issues
now fact_chown_check --verbose shows also the passed tests (--quiet is the default)
Fixed another problem w/ the script:
  • was not invoked on SL7 when /user/sbin/gwms-factory start was called directly (no serveice). Fixed enabling sysconfig also there.

#4 Updated by Lorena Lobato Pardavila 2 months ago

  • Assignee changed from Lorena Lobato Pardavila to Marco Mambelli
  • Status changed from Feedback to Accepted

Tested last changes and it´s ready to go.

[root@fermicloud039 ~]# /usr/sbin/gwms-factory start
Entries TEST_ENTRY are enabled and use unsupported Globus GT2. Should be disabled.
Please, make sure to run the fact_chown script. More details at https://glideinwms.fnal.gov/doc.v3_5_1/factory/configuration.html#single_user
The Factory is not ready for 3.5. Please run /usr/bin/fact_chown_check for more details
To disable this check remove the --check_35_ready option fr[FAILED]wms-factory.service file

For the record, good job double-checking the GT2 entries when executing single user script. I liked it!

[root@fermicloud039 ~]# sudo -u gfactory /usr/bin/fact_chown_check -v
Loading configuration file /etc/gwms-factory/glideinWMS.xml
Checked ownership (gfactory) of client and proxies directories. Passed
Checked Owner of 0 jobs
No jobs running. Passed
Entries TEST_ENTRY are enabled and use unsupported Globus GT2. Should be disabled.
Please, make sure to run the fact_chown script. More details at https://glideinwms.fnal.gov/doc.v3_5_1/factory/configuration.html#single_user

#5 Updated by Marco Mambelli about 2 months ago

  • Status changed from Accepted to Resolved

#6 Updated by Marco Mambelli about 2 months ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF