Project

General

Profile

Bug #16560

ups gets confused by cross-O.S. containers

Added by Dave Dykstra over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
05/16/2017
Due date:
01/01/2018
% Done:

100%

Estimated time:
Duration: 231

Description

I noticed that running jobs at UNL where they run EL6 docker containers on EL7 hosts that ups gets confused by the newer kernel. The ups flavor in that case because Linux64bit+3.10-2.12, but the packages are created on real EL6 systems so they're created with Linux64bit+2.6-2.12. This problem is going to become quite a bit more common in the future as everybody switches to using singularity, freeing sites to upgrade their worker nodes to EL7. Currently, experiments that want to run in this environment have to set 'UPS_OVERRIDE=-H Linux64bit+2.6-2.12' when they detect this situation. This is unsustainable.

I discussed it with Marc Mengel and he thinks the time has come to change ups to ignore the kernel portion of the flavor on Linux, the part after the plus. I would also like to encourage dropping the kernel from the flavor on newly created packages, either by using Linux64bit-2.12 or Linux64bit+-2.12. The former would look nicer but Marc said the latter is probably easier to implement.

History

#1 Updated by Marc Mengel over 2 years ago

Notes:
So it looks like if we stub the strcmp in upsmat.c:1304 and maybe 696 with a smarter compare routine, we could make this work...

#2 Updated by Tanya Levshina about 2 years ago

  • Target version set to FIFE Roadmap for FY18

#3 Updated by Dave Dykstra about 2 years ago

Isn't this urgent now that FermiGrid is using an EL7 kernel with an EL6 docker container?

#4 Updated by Marc Mengel about 2 years ago

This is fixed in the ups v6_0_2 release. This is currently in the products/larsoft product areas (in /grid/fermiapp and /cvmfs/fermi.opensciencegrid.org/) , and I'll be getting it into the products/common area tomorrow. Usually we put out an ITIL Change to make it current in the common products areas...

#5 Updated by Tanya Levshina over 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#6 Updated by Tanya Levshina over 1 year ago

  • Status changed from Resolved to Closed

#7 Updated by Tanya Levshina over 1 year ago

  • Due date set to 01/01/2018


Also available in: Atom PDF