Project

General

Profile

Bug #13881

scripts in frontend/tools do not work correctly in case of rpms

Added by Parag Mhashilkar about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
09/19/2016
Due date:
% Done:

0%

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

Description

This was reported by Shreyas while he was trying to remove idle glideins from the frontend side. Script he used in particular is remove_requested_glides. Looks like moving from tarball to rpms, we never checked that paths were corectly created in case of some of the scripts. We should go over all the tools in the frontend dir and make sure all the scripts work correctly in case of rpms as well.

[root@fife-gwmsfrontend-dev01 ~]# remove_requested_glideins
.
Done
/usr/bin/python: can't open file '/usr/bin/../glideinFrontend.py': [Errno 2] No such file or directory

History

#1 Updated by Parag Mhashilkar about 4 years ago

  • Target version changed from v3_2_16 to v3_2_17

#2 Updated by HyunWoo Kim about 4 years ago

  • Status changed from New to Feedback
  • Assignee changed from HyunWoo Kim to Parag Mhashilkar

Here are actions that were taken for those tools in /usr/lib/python2.6/site-packages/glideinwms/frontend/tools/
(or /usr/bin)

1. remove_requested_glideins:
- a modification was necessary to launch glideinFrontend.py from a correct path
- made sure the command runs ok after this change

   /usr/bin/remove_requested_glideins -d /var/lib/gwms-frontend/vofrontend/

2. frontend_match_list:
- I had to explicitly import getGlideinCpusNum
- made sure the command runs ok after this change

cd /usr/lib/python2.6/site-packages/glideinwms/frontend/tools/
./frontend_match_list  /var/lib/gwms-frontend/vofrontend/ main

3. frontend_match_ana:
- I had to explicitly import getGlideinCpusNum
- from elementDescript.merged_data['FactoryMatchAttrs']: to elementDescript.frontend_data['FactoryMatchAttrs']:
- made sure the command runs ok after this change

cd /usr/lib/python2.6/site-packages/glideinwms/frontend/tools/
./frontend_match_ana  /var/lib/gwms-frontend/vofrontend/ main 107.0

4. glidein_off:
- no change necessary
- made sure the command runs ok as-is

cd /usr/lib/python2.6/site-packages/glideinwms/frontend/tools/
./glidein_off -g main -d /var/lib/gwms-frontend/vofrontend/ glidein_29345_10308915@fermicloud025.fnal.gov

5. fetch_glidein_log
- no change necessary
- made sure the command runs ok as-is

cd /usr/lib/python2.6/site-packages/glideinwms/frontend/tools/
./fetch_glidein_log  -g main -d /var/lib/gwms-frontend/vofrontend/ glidein_11499_207891156@fermicloud025.fnal.gov

6. enter_frontend_env
- no change necessary
- made sure the command runs ok as-is

cd /usr/lib/python2.6/site-packages/glideinwms/frontend/tools/
 ./enter_frontend_env  -g main -d /var/lib/gwms-frontend/vofrontend/

7. convert_frontend_2to3.sh
I did not look into this one.

I also took a quick look at those scripts in Factory directory:
- analyze_entries
- analyze_frontends
- analyze_queues
- entry_ls
- entry_q
These seem to work fine.
For the rest of Factory tools, I need to open a separate ticket

#3 Updated by Shreyas Bhat about 4 years ago

Thanks very much - I'll run some tests next week to make sure our group knows how to properly use these tools.

#4 Updated by Shreyas Bhat about 4 years ago

Was this change made on the production FE or preprod/dev as well?

#5 Updated by Parag Mhashilkar about 4 years ago

  • Assignee changed from Parag Mhashilkar to HyunWoo Kim

sent feedback separately.

Did you also check following tools?
  • fetch_glidein_log
  • glidein_off
  • enter_frontend_env

#6 Updated by HyunWoo Kim about 4 years ago

merged into branch_v3_2

#7 Updated by HyunWoo Kim about 4 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF