Ticket #134 (closed bugs: fixed)

Opened 6 months ago

Last modified 5 months ago

gPlazma returns the same FQAN for the same DN even if the FQAN changes for subsequent requests.

Reported by: patrick Assigned to: patrick
Priority: major Milestone: 1.8.0-15p6
Component: utilities Version: 1.8.0
Keywords: gplazma, DN, FQAN Cc:
Sub Version:

Description (Last modified by patrick)

Reported by Ron and Pic:

Hi Ted,

I am still having difficulty with with the caching of the mapping by the srm.

When I do:

voms-proxy-init -voms dteam

and I do a srm-reserve-space I see in the gPlazma log:

05/21 08:15:07,083 GPLAZMALiteVORoleAuthzPlugin: authRequestID 1628440016 Requesting mapping for User with DN and role: /O=dutchgrid/O=users/O=sara/CN=Ron Trompert/dteam/Role=NULL/Capability=NULL 05/21 08:15:07 Cell(gPlazma@gPlazma-dcadminDomain) : authRequestID 1628440016 authorized dteam 1991 [1135] / for /O=dutchgrid/O=users/O=sara/CN=Ron Trompert

which is OK and in the catalina.out file I see: 05/21 08:15:01 Cell(SrmSpaceManager@srm-srmDomain) : reserveSpace(group=dteam, role=, sz=1000, latency=NEARLINE, policy=CUSTODIAL, lifetime=3600000, description=TESTTOKEN 05/21 08:15:01 Cell(SrmSpaceManager@srm-srmDomain) : reserveSpaceInLinkGroup(linkGroupId=9group=dteam, role=, sz=1000, latency=NEARLINE, policy=CUSTODIAL, lifetime=3600000, description=TESTTOKEN

This is fine too. But when I do voms-proxy-init -voms dteam:/dteam/ne and I do a srm-reserve-space, I see in the gPlazma log:

05/21 08:29:30,230 GPLAZMALiteVORoleAuthzPlugin: authRequestID 1115292472 Requesting mapping for User with DN and role: /O=dutchgrid/O=users/O=sara/CN=Ron Trompert/dteam/ne/Role=NULL/Capability=NULL 05/21 08:29:30 Cell(gPlazma@gPlazma-dcadminDomain) : authRequestID 1115292472 authorized dteam 1991 [1135] / for /O=dutchgrid/O=users/O=sara/CN=Ron Trompert

which is OK but then in the catalina.out file:

05/21 08:29:25 Cell(SrmSpaceManager@srm-srmDomain) : reserveSpace(group=dteam, role=, sz=1000, latency=NEARLINE, policy=CUSTODIAL, lifetime=3600000, description=TESTTOKEN3 05/21 08:29:25 Cell(SrmSpaceManager@srm-srmDomain) : reserveSpaceInLinkGroup(linkGroupId=9group=dteam, role=, sz=1000, latency=NEARLINE, policy=CUSTODIAL, lifetime=3600000, description=TESTTOKEN3

which is wrong. After restarting the srm I get with the same proxy:

05/21 08:37:26 Cell(SrmSpaceManager@srm-srmDomain) : reserveSpace(group=/dteam/ne, role=NULL, sz=1000, latency=NEARLINE, policy=CUSTODIAL, lifetime=3600000, description=TESTTOKEN4

which is correct. In the setup file I have srmAuthzCacheLifetime=0.

Another thing is that when I do a dcache-core stop there is still one dcache java process running on our srm connected to init (pid=1) but this is probably not related to this.

Cheers,

Ron

Change History

05/27/08 22:18:12 changed by patrick

  • owner changed from litvinse to patrick.
  • status changed from new to assigned.

05/27/08 22:18:53 changed by patrick

  • description changed.

05/27/08 22:20:34 changed by patrick

rt ticket 2989

05/29/08 10:45:53 changed by patrick

  • status changed from assigned to closed.
  • resolution set to fixed.

05/31/08 08:55:22 changed by patrick

  • status changed from closed to reopened.
  • resolution deleted.

06/04/08 09:07:20 changed by patrick

  • milestone changed from 1.8.0-15p5 to 1.8.0-15p6.

06/17/08 21:30:30 changed by tigran

  • status changed from reopened to closed.
  • resolution set to fixed.

The actual issue was cased by SRM internal caching.