At some point during the iRODS 4.3 and python-irodsclient upgrade, landing zone moving and validation in dev fails with the following error:
Failed to move landing zone files: BatchValidateChecksumsTask failed: Could not connect to specified host and port: irods:1247 (Unable to read checksum file "xxx.md5")
Some facts:
The iRODS server is up and responding normally
The file exists and has the expected content
The rodsuser who uploaded the file can iget the file just fine.
What is suspicious is the irods:1247 URL there. Could this be another case of the redirecting "feature" introduced in python-irodsclient v1.1.9?
Update: Yes, of course it was that. So the solution right now is:
Add 127.0.0.1 irods into /etc/hosts
Add a note about this in the docs together with irods-test (already there)
Upgrade to python-irodsbackend v2.1.1 once it's out, as that will fix the default redirect problem
At some point during the iRODS 4.3 and python-irodsclient upgrade, landing zone moving and validation in dev fails with the following error:
Some facts:
iget
the file just fine.What is suspicious is the
irods:1247
URL there. Could this be another case of the redirecting "feature" introduced in python-irodsclient v1.1.9?Update: Yes, of course it was that. So the solution right now is:
127.0.0.1 irods
into/etc/hosts
irods-test
(already there)