Description of problem:

the scenario is the following:

1. user creates a S3 data connection "aws-connection"
2. user creates a workbench "workbench-test"
3. user creates another S3 dc and connect it to "workbench-test". By mistake user assignes "aws-connection" as name (i.e., duplicate)

After step 3, "workbench-test" gets unexpected restarted and the first S3 DC gets connected to that workbench.

The GIF shows the scenario:

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. user creates a S3 data connection "aws-connection"
2. user creates a workbench "workbench-test"
3. user creates another S3 dc and connect it to "workbench-test". By mistake user assignes "aws-connection" as name (i.e., duplicate)
4. check the status of the workbench and its pod
5. check which S3 dc got connected to the workbench

Actual results:

although the data connection creation failed, the workbench gets restarted and connected to the wrong data connection

Expected results:

failure in data connection does not trigger any workbench update

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

RHODS v1.21.0-20

Workaround:

N/A

Additional info:

the scenario may become more frequent when there are many  data connections