What steps will reproduce the problem?
1. conn, errmsg = rcConnect('remote host', 1247, 'user', 'remotezone')
status = clientLogin(conn)
2. f.irodsOpen(conn, "/remotezone/home/user/coll/filename","r")
3. f.getInfos()
What is the expected output?
(dms)[irods@dms examples]$ isysmeta ls -l
/testZone/home/rods/122/1363042913398_B4bkAWMYteg4QhoZ
doing ls of /testZone/home/rods/122/1363042913398_B4bkAWMYteg4QhoZ
data_name: 1363042913398_B4bkAWMYteg4QhoZ
data_id: 16154
coll_id: 10112
data_repl_num: 0
data_version:
data_type_name: generic
data_size: 5375
resc_group_name:
resc_name: testResc
data_path :
/home/irods/data/irodsdata/Vault/home/rods/122/1363042913398_B4bkAWMYteg4QhoZ
data_owner_name: rods
data_owner_zone: testZone
data_repl_status: 1
data_status:
data_checksum :
data_expiry_ts (expire time): : None
data_map_id: 0
r_comment:
create_ts: 01363042913: 2013-03-11.17:01:53
modify_ts: 01363042913: 2013-03-11.17:01:53
What do you see instead?
> f = irodsOpen(conn, "/testZone/home/rods/122/1363042913398_B4bkAWMYteg4QhoZ",
'r')
>f.getInfos()
{'coll_id': '',
'create_ts': ' ',
'data_checksum': '',
'data_expiry_ts': ' ',
'data_id': 'mountP',
'data_is_dirty': '',
'data_map_id': '',
'data_mode': '',
'data_name': '1363042913398_B4bkAWMYteg4QhoZ',
'data_owner_name': ' ',
'data_owner_zone': ' ',
'data_path': '/testZone/home/rods/122',
'data_repl_num': '1',
'data_size': ' ',
'data_status': '',
'data_type_name': 'mountP',
'data_version': '',
'modify_ts': ' ',
'r_comment': '',
'resc_group_name': '',
'resc_name': 'test2Resc'}
What version of the product are you using? On what operating system?
PyRODS 3.2.3
CentOS 6.4
Please provide any additional information below.
The two zones are in a federated iRODS system. The sysmeta command was run on
the same machine as the PyRODS code. That machine is in a different iRODS zone
from the file being queried.
Original issue reported on code.google.com by
agrimst...@gmail.comon 28 Jul 2013 at 2:24