Feature #23073

Single user factory: check that the migration script has been run before startup

Added by Marco Mascheroni about 1 month ago. Updated about 13 hours ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Starting from 3.5 glideins owner will be the gfactory user, and not the frontend related users. To deal with already running pilots, we have a script that converts the ownership of those running pilots to gfactory. We need to make sure the script run before starting the factory.


#1 Updated by Marco Mascheroni about 1 month ago

  • Target version changed from v3_4_6 to v3_5_1

#2 Updated by Marco Mascheroni 23 days ago

  • Assignee changed from Marco Mascheroni to Marco Mambelli
  • Status changed from New to Feedback

#3 Updated by Marco Mascheroni 23 days ago

Changes are in v35/23073
Marco, feel free to redirect the ticket to somebody else for the review.

#4 Updated by Marco Mambelli 22 days ago

  • Assignee changed from Marco Mambelli to Marco Mascheroni

Our main platform is SL7, but SL6 is still supported. I merged the current version with a small change (exit code 150, outside the LSB reserved range). The SL6 init template should be edited as well, then the new commits will be merged.

#5 Updated by Marco Mambelli 21 days ago

  • Status changed from Feedback to Resolved

I changed the initd template for SL6 and merged

#6 Updated by Marco Mascheroni 15 days ago

For testing (for a fresh 3.5 factory, not upgraded from 3.4):
1) Check that the factory starts correctly
2) Submit a jobs using a user different than gfactory and then verify that the factory does not start correctly (the script checks that all the jobs are owned by gfactory)
3) Modify the ownership of one of the log directories (e.g.: /var/log/gwms-factory/client/user_frontend) and verify the factory does not start if it not owned by gfactory

#7 Updated by Marco Mambelli about 13 hours ago

  • Tracker changed from Bug to Feature

Also available in: Atom PDF