Bug 1696086
Summary: | [Kubevirt-Foreman] wrong validation on x509 certificate | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Vatsal Parekh <vparekh> |
Component: | Compute Resources - CNV | Assignee: | Shira Maximov <mshira> |
Status: | CLOSED ERRATA | QA Contact: | Vladimír Sedmík <vsedmik> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.6.0 | CC: | dvoss, egolov, lhellebr, masayag, mmccune, pkliczew, vsedmik |
Target Milestone: | 6.7.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-fog-kubevirt-1.1.1 | Doc Type: | If docs needed, set a value |
Doc Text: |
Incorrect x509 certificates specified in the settings fields for Kubevirt Compute Resources can still show 'Test connection was successful'. If unable to view list of virtual machines after creating the Compute Resource, verify the x509 certificate is valid.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-14 13:24:10 UTC | 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: | |||
Bug Depends On: | 1746434 | ||
Bug Blocks: |
Description
Vatsal Parekh
2019-04-04 06:50:41 UTC
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. https://access.redhat.com/errata/RHSA-2020:1454 |