[17.0][FIX] dms: Change save_type when migrate to another storage

[peluko00]

When migrating files from one storage to another, their save type needs to change to match the storage's save_type. After that, these files will no longer require migration.

cc https://github.com/APSL 38655
@miquelalzanillas @lbarry-apsl @javierobcn @mpascuall @BernatObrador @ppyczko please review

[victoralmau]

IMP, this change isn't appropriate. Currently, the save_type field is set to compute (not store); perhaps it should be store, but in any case, the value shouldn't be defined this way. The proper approach is to set the appropriate value in the compute (_compute_save_type) based on different scenarios and/or add a depends clause if necessary.

To clarify, I have never used this migration action.

[peluko00]

IMP, this change isn't appropriate. Currently, the save_type field is set to compute (not store); perhaps it should be store, but in any case, the value shouldn't be defined this way. The proper approach is to set the appropriate value in the compute (_compute_save_type) based on different scenarios and/or add a depends clause if necessary.

To clarify, I have never used this migration action.

When executes action_migrate they need change the save_type because if you change from filestore to Amazon s3 if you don't change this attribute the migration will be failed.