BUG: Move own data - permissions

[pwalczysko]

Move to another group does not work when moving OWN images between groups in some cases.
For example:

• Login as user-3
• Go to Read-annotate-1 group, your own data, choose an image, right-click > Move (to read-only-1 group)
• Action works OK
• Go to Read-only-1 group, your own data, choose an image, right-click > Move (to read-annotate-1 group)
• Move fails (see screenshot)

Interestingly, this looks like if user-3 does not have permissions to do the move from Read-only-1 to Read-annotate-1 (this is true, user-3 cannot move OTHER'S data like this).
But here, user-3 tries to move HIS OWN DATA. This should always work.
@ jburel has advised this is a server side problem.

[pwalczysko]

@ jburel Entry at ​https://docs.google.com/spreadsheet/ccc?key=0AuHdV7GT-8hmdDJXalU3VlhOS0cxdm1QcjE5eEFIRmc#gid=1 created.

[pwalczysko]

Changed the description - this is not a problem of choosing more images for move, but a strange "permissions" problem.

[jmoore]

I found this in the server-log:

2013-02-25 14:16:26,968 INFO  [          ome.services.graphs.GraphState] (2-thread-1) Failed to process Image/FilesetImageLink/Fileset/FilesetImageLink: 378 due to GraphException: No top-level item found: update FilesetImageLink  set details.group.id = :grp where id = :id and details.group.id = :gid  (id=378, grp=7)

Still trying to reproduce locally:

$ bin/omero group add ra10461 --perms=rwra--
...
Created session 4638de73-20ed-469c-b38c-947f1bf536cd (root@localhost:4064). Idle timeout: 10.0 min. Current group: system
Added group 3553 (id=ra10461) with permissions rwra--
$ bin/omero group add ro10461 --perms=rwr---
Using session 4638de73-20ed-469c-b38c-947f1bf536cd (root@localhost:4064). Idle timeout: 10.0 min. Current group: system
Added group 3554 (id=ro10461) with permissions rwr---
$ bin/omero user add 10461 test user ro10461 ra10461
Using session 4638de73-20ed-469c-b38c-947f1bf536cd (root@localhost:4064). Idle timeout: 10.0 min. Current group: system
Please enter password for your new user (10461): 
Password cannot be empty
Please enter password for your new user (10461): 
Please re-enter password for your new user (10461): 
Added user 3502 with password
$ bin/omero login 10461@localhost
Password:
Created session db003fe5-c9f9-4d7d-96f5-5657980cd214 (10461@localhost:4064). Idle timeout: 10.0 min. Current group: ro10461
$ touch a.fake
$ bin/omero import a.fake
Using session db003fe5-c9f9-4d7d-96f5-5657980cd214 (10461@localhost:4064). Idle timeout: 10.0 min. Current group: ro10461
...
2013-02-25 15:27:51,965 20791      [      main] INFO   ormats.importer.cli.LoggingImportMonitor  - IMPORT_DONE Imported file: /Users/moore/GlencoeSoftware.git/git/omero.git/dist/a.fake
Imported pixels:
967
Other imported objects:
Fileset:1152
Image:967
2013-02-25 15:27:51,966 20792      [      main] INFO      ome.formats.importer.cli.ErrorHandler  - Number of errors: 0
$ bin/omero chgrp ra10461 /Image:967
Using session db003fe5-c9f9-4d7d-96f5-5657980cd214 (10461@localhost:4064). Idle timeout: 10.0 min. Current group: ro10461
omero.cmd.Chgrp /Image 967... ok

Jean-Marie, is there any chance of getting the error message in omeroinsight.log?

[jburel]

I will check the code but I assume it should not be a problem
Petr did you notice the issue on dev_4_4 too?

[jmoore]

Not included in fs demo 2 tag. Removing from sprint

[pwalczysko]

@ jburel, @ jmoore :

The situation on Howe is as follows:

Repeat of the situation described for Gretzky works fine - this means
User-3, moving own data from read-only-1 to read-annotate-1 on Howe
User-3, moving own data from read-annotate to read-only on Howe.

Repeated once more on Gretzky with build #173 (the build where Move is not disabled yet).
User-3 cannot move his data to read-annotate on Gretzky, as reported previously.

User-2 cannot move his data from private-1 to read-only-1 on Gretzky. This precise action is okay on Howe though.

[jburel]

Moved from sprint FS Demo 4.3

[jburel]

Tested with Today's build
Move image back and forth between the groups as described. Everything works as expected.
The recent changes server side fixed the issue. Closing