Project

General

Profile

Bug #7376

jobsub_client ups product

Added by Christopher Backhouse over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
11/24/2014
Due date:
% Done:

0%

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

Description

I maintain NOvA software at an offsite location (Caltech). We recently started setting up jobsub_client as part of our setup script.

So, I install jobsub_client:

upd install jobsub_client v1_0

and now when I setup I get:

ERROR: Product 'pycurl' (with qualifiers ''), has no current chain (or may not exist)
ERROR: Product 'pycurl' (with qualifiers ''), has no current chain (or may not exist)

Looking in /grid/fermiapp/products/common/db/pycurl/ I see the two versions that are installed, so I do:

upd install pycurl v7_15_5 -H Linux64bit+2.6-2.5
upd install pycurl v7_16_4 -H Linux64bit+2.6-2.12

Now I can explicitly "setup pycurl v7_15_5", but "setup jobsub_client" still gives the same errors. I get the same on both SL5 and SL6 nodes.

I don't understand much about ups, but is this a packaging problem with the jobsub_client product? It kind of seems like it's not specifying a specific version of pycurl. Is that right? Should that default to the latest available? Why isn't it?

History

#1 Updated by Christopher Backhouse over 4 years ago

My goal here isn't to submit jobs from offsite, I just want to shut our setup scripts up without having to hack anything. Although, do offsite submissions work? Presumably I can access the web service (even if I have to tunnel), and I have a kerberos ticket.

#2 Updated by Christopher Backhouse over 4 years ago

The magic incantation appears to be:

upd install -G "-c" pycurl v7_15_5 -H Linux64bit+2.6-2.5
upd install -G "-c" pycurl v7_16_4 -H Linux64bit+2.6-2.12

I copied this from elsewhere, I have no idea what these flags actually do.

#3 Updated by Parag Mhashilkar over 4 years ago

  • Assignee set to Dennis Box
  • Target version set to v1.1

#4 Updated by Dennis Box over 4 years ago

  • Status changed from New to Assigned

Sorry Chris this is maddening. I did not see this ticket 25 days ago, I just saw it when Parag assigned it to me.

I will have to ask our resident UPD expert about this one. I can update the documentation in the mean time.
Dennis

#5 Updated by Dennis Box over 4 years ago

  • Status changed from Assigned to Resolved

#6 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF