Bug 2102020

Summary: [ MTC UI ] Updating the replication repository to a different storage provider type is not respected by the UI
Product: Migration Toolkit for Containers Reporter: mohamed <midays>
Component: UIAssignee: John Matthews <jmatthew>
Status: ASSIGNED --- QA Contact: ssingla
Severity: medium Docs Contact: Richard Hoch <rhoch>
Priority: medium    
Version: 1.7.2   
Target Milestone: ---   
Target Release: 1.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mohamed 2022-06-29 07:18:45 UTC 
Description of problem:

After updating the replication repository to a different type and clicking on ‘Update Repository' button, it shows connection successful but the UI is not updated with the correct details, and when clicking on the edit button for a second time, it shows the old replication repository information.

Another interesting behavior is when you try to update the replication repo again, it still shows the old replication details, and when you select the new repo it also shows all the information you entered in the previous edit and the update repository button is not enabled, as if there are no changes to be submitted.


Version-Release number of selected component (if applicable):
Source GCP 4.5   MTC 1.7.2 + OADP 1.0.3
Target  GCP  4.10   MTC 1.7.2 + OADP 1.0.3


Steps to reproduce: 
Navigate to the replication repository page
Open the menu for a replication repo and click edit
Select a different Storage provider type and fill in the rest of the details accordingly
Click Update repository

Expected Result: The UI should update and display the correct details accordingly, and when clicking on edit again it should show the updated details not the old one.

Actual Result: The UI displays the old repo details and when clicking on the edit button again the details of the old repo is present and updating it again does not enable the update repository button.

Additional Info: 

In the backend it also shows the old repo, not the new one

$ oc get migstorage -n openshift-migration -o yaml

apiVersion: v1
items:
- apiVersion: migration.openshift.io/v1alpha1
  kind: MigStorage
  metadata:
    annotations:
      openshift.io/touch: 059c29c8-f54e-11ec-ba3c-0a580a80020b
    creationTimestamp: "2022-06-26T12:45:54Z"
    generation: 4
    name: automatic
    namespace: openshift-migration
    resourceVersion: "169932"
    uid: 36fbeedc-33f1-403f-b9eb-33241ecfc749
  spec:
    backupStorageConfig:
      awsBucketName: camreplication
      awsRegion: us-east-2
      credsSecretRef:
        name: automatic-vpvfr
        namespace: openshift-config
      gcpBucket: camreplication
    backupStorageProvider: gcp
    volumeSnapshotConfig:
      awsRegion: us-east-2
      credsSecretRef:
        name: automatic-vpvfr
        namespace: openshift-config
    volumeSnapshotProvider: gcp
  status:
    conditions:
    - category: Required
      lastTransitionTime: "2022-06-26T12:45:55Z"
      message: The storage is ready.
      status: "True"
      type: Ready
    observedDigest: 3a71ac0bab933675d63872750dbe4d0d1ad7ec25def45f99ee70e4cbde67fce7
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""