Description of problem:
Even when the cert value was given wrong, the validation shows that `Test connection was successful`
And adding compute resource with that wrong value worked as well, was able to see the list of VMs, which reflects some wrong logic there.
Version-Release number of selected component (if applicable):
master of the plugin
Steps to Reproduce:
1.Add a wrong value in x509 cert
2.Test connection and add that compute resource
3.Still seeing the list of VMs
Compute resource works with wrong x509 cert, error in the logic
Should show failed validation at first, and should not be working if cert was wrong
Also seeing the issue with positive flow, not able to add it anymore with updated gem
Getting `wrong number of arguments (given 1, expected 0)`
This seems working on latest nightly Foreman + plugin master
Wrong cert now causes Test Connection to fail.
However, it is still possible to submit the form and the CR is added. It doesn't work then. This isn't necessarily wrong but it's inconsistent with other CRs. For example, it's not possible to add a RHEV CR with invalid cert at all. I think it shouldn't be possible to add Kubevirt when Test Connection fails.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.