Description of problem:

After enabling 'Require SSL verification' and adding content to the CA bundle file for an MCG NooBaa bucket in migstorage, the connection fails as expected. However, when reverting these changes by removing the CA bundle content and unchecking 'Require SSL verification,' the connection still fails. The issue is only resolved by deleting and re-adding the repository.


Version-Release number of selected component (if applicable):
MTC 1.8.0

How reproducible:
Always

Steps to Reproduce:

1. Edit the migstorage bucket
2. check require SSL verification
3. add CA cert
4. click update repository
5. Remove CA cert & uncheck require SSL verification
6. click update repository


Actual results:
The changes are not reverted causing the bucket shows connection failed

Expected results:
the changes should be proerly cleared and the connection should be successfull

Additional info:
On migstorage in API insecure: true is properly set again, but s3CustomCABundle is still set:
    backupStorageConfig:
      awsBucketName: migstorage
      awsRegion: ""
      awsS3Url: https://s3-ocs-storage.apps.cam-man-tgt.qe.devcluster.openshift.com
      credsSecretRef:
        name: automatic-xxxrm
        namespace: openshift-config
      insecure: true
      s3CustomCABundle: Vm1wR1UxUXlSbkpQVm1SU1lrZG9WMVpyVWtaTmJIQnVVRlF4ZW1RPWY=