Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UGE configured to dynamically allocate a GID when submitting a job #1303

Closed
sylabskeith-zz opened this issue Feb 14, 2018 · 5 comments
Closed
Assignees

Comments

@sylabskeith-zz
Copy link

sylabskeith-zz commented Feb 14, 2018

Version of Singularity

2.4.2

Expected behavior

Proper allocation of dynamic GID during job submission to UGE

###Actual Behavior

We are getting ENOENT errno on the following line of code:
https://github.com/singularityware/singularity/blob/2.4.2/src/lib/runtime/files/group/group.c#L147

Steps to reproduce behavior

Some reference to UGE:
http://gridengine.eu/grid-engine-internals

@markeganfuller
Copy link
Contributor

Running singularity on our local cluster which uses UGE just results in the following for the UGE job group:

VERBOSE [U=2361,P=12042]   singularity_runtime_files_group()         Skipping GID 20105 as group entry does not exist.

@dtrudg
Copy link
Contributor

dtrudg commented Mar 7, 2018

Looks like ENOENT needs to be handled as a possible 'group not found' see:

man 3 getgrgid

0 or ENOENT or ESRCH or EBADF or EPERM or ...
The given name or gid was not found.

@dtrudg dtrudg self-assigned this Mar 7, 2018
@dtrudg
Copy link
Contributor

dtrudg commented Mar 7, 2018

@sylabskeith - is it possible to test PR #1366? This will handle an ENOENT on the group query, and result in same behaviour that .@markeganfuller was seeing above on his system.

@GodloveD
Copy link
Collaborator

GodloveD commented Mar 9, 2018

^ Also @paulo7777

@dtrudg
Copy link
Contributor

dtrudg commented Apr 28, 2018

Closing this as it is understood fixed with #1366 which has been merged. Please don't hesitate to reopen if any further issue.

@dtrudg dtrudg closed this as completed Apr 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants