Bugzilla – Full Text Bug Listing
|Summary:||Container in livelock state for an incorrectly mapped DN|
|Product:||GRAM||Reporter:||Abhishek Gaurav <email@example.com>|
|Component:||wsrf managed execution job service||Assignee:||Stuart Martin <firstname.lastname@example.org>|
|Severity:||normal||CC:||email@example.com, firstname.lastname@example.org, email@example.com|
The globus container gets into a livelock state if the requesting DN is mapped to a user that isn't in the passwords file for the situations when the credentials are delegated from the client. If the credential isn't delegated, it works fine. We have noted this problem with 'globusrun-ws' command with -J option. Without the -J option, the container appropriately returns an error. The exact command used was: globusrun-ws -submit -streaming -J -F https://<host-name>:8443/wsrf/services/ManagedJobFactoryService -job-command /bin/hostname This problem has been noted both in 4.0.1 and 4.0.3 versions and on 32 bit and 64 bit systems. Apologies if this isn't a bug. Thanks, Abhishek.
I'm assuming this is a GRAM issue that occurs when the service attempts to write the delegated credential to the user's job directory, so I'll reassign to the GRAM team.
Doing some bugzilla cleanup... Resolving old GRAM3 and GRAM4 issues that are no longer relevant since we've moved on to GRAM5. Also, we're now tracking issue in jira. Any new issues should be added here: http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363