Bug #33392: Outdated certificate is accepted when creating new CR - KubeVirt - Foreman

Actions

Copy link

Bug #33392

open

Outdated certificate is accepted when creating new CR

Added by yifat makias about 3 years ago. Updated about 3 years ago.

Status:

New

Priority:

Normal

Assignee:

yifat makias

Target version:

foreman_kubevirt_v0.1.5

Difficulty:

Triaged:

Bugzilla link:

1816726

Pull request:

https://github.com/fog/fog-kubevirt/pull/147

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Description of problem:
Creating new KubeVirt CR with outdated certificate works but it shouldn't, as the certificate is outdated (not valid).

Version-Release number of selected component (if applicable):
Satellite 6.7.0 snap 16:
satellite-6.7.0-6.el7sat.noarch
tfm-rubygem-foreman_kubevirt-0.1.7-1.el7sat.noarch
tfm-rubygem-fog-kubevirt-1.3.3-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. In Sat WebUI go to Infrastructure > Compute Resources > Create CR
2. Select KubeVirt provider and provide (among other fields) an outdated certificate
3. Click 'Test Connection' or 'Submit' button

Actual results:
action succeeds although it shouldn't

Expected results:
should fail with an appropriate error message

Additional info: