Starto migration status not updating fix and Backend listing as SSP fix #1360
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug fix
What this PR does / why we need it:
In Strato functional testing yesterday discovered that after creating migration plans. Even though object is migrated from src to the target bucket the status of the migration plan doesn't reflect the same due to an internal issue in code related to the database update
In Storage Service Plan mode of installation backends was getting listed as SSPs
Which issue(s) this PR fixes:
Fixes #
Test Report Added?:
/kind TESTED
Test Report:
Storage Service Plan Testing
Creating a service plan now lists the service plan instead of the previous backends
Creating bucket with SSP is now working
Migration from one cloud vendor to another
Migration from AWS to GCP
Status and number of objects migrated is correct
Object is also present in the target bucket
Migration from GCP to AWS
Status and number of objects migrated is correct
Object is aslo present in the target bucket
Special notes for your reviewer: