Cloud-Migration-Tool
Cloud-Migration-Tool copied to clipboard
success reported on failure when destination inaccessible
When the destination isn't directly accessable, cloudmig reports a successful migration when no files were transferred. The transfer fails properly if the source is not accessible. This only occurs when destination is not accessible.
Example1: When cloudmig receives HTTP-403 during posix->RS2 migration, it results in:
cloudmig:3476:[INFO][Migrating] File 'newfile.txt' transfer failed !
cloudmig:3476:[ERR][Migrating] : Could not migrate file newfile.txt
cloudmig:3469:[INFO]Uploading digest: 0/0 objs, 1/0 bytes
cloudmig:3469:[INFO][Uploading Status Digest] Uploaded digest: { "objects": 1, "done_objects": 0, "bytes": 1024, "done_bytes": 0 }
cloudmig:3469:[INFO]Migration finished with success !
Example2: When cloudmig receives HTTP-307 during S3->S3 migration, it results in:
cloudmig:2545:[INFO][Migrating] File '100Kfile.txt' transfer failed !
cloudmig:2545:[ERR][Migrating] : Could not migrate file 100Kfile.txt
cloudmig:2538:[INFO]Uploading digest: 0/0 objs, 1/0 bytes
cloudmig:2538:[INFO][Uploading Status Digest] Uploaded digest: { "objects": 1, "done_objects": 0, "bytes": 102400, "done_bytes": 0 }
cloudmig:2538:[INFO]Migration finished with success !