Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1990851

Summary: Enable TLS configuration settings in web console
Product: Migration Toolkit for Virtualization Reporter: Franco Bladilo <fbladilo>
Component: User ExperienceAssignee: Fabien Dupont <fdupont>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: low Docs Contact: Avital Pinnick <apinnick>
Priority: low    
Version: 2.1.0CC: apinnick, fdupont, istein
Target Milestone: ---Keywords: RFE
Target Release: 2.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-09 19:20:47 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:

Description Franco Bladilo 2021-08-06 12:37:00 UTC
Description of problem:

It would be ideal to get the same functionality as in forklift controller for TLS settings on UI, that is enabling/disabling , configurable cert/key locations and port , example of controller pod below :

    Environment:
      POD_NAMESPACE:                 konveyor-forklift (v1:metadata.namespace)
      ROLE:                          inventory
      SECRET_NAME:                   webhook-server-secret
      API_PORT:                      8443
      API_TLS_ENABLED:               true
      API_TLS_CERTIFICATE:           /var/run/secrets/forklift-inventory-serving-cert/tls.crt
      API_TLS_KEY:                   /var/run/secrets/forklift-inventory-serving-cert/tls.key
      METRICS_PORT:                  8081
      POLICY_AGENT_URL:              https://forklift-validation.konveyor-forklift.svc.cluster.local:8181
      POLICY_AGENT_SEARCH_INTERVAL:  120
      LOG_LEVEL:                     4

This will certainly help cases in where we have to switch off TLS or the location for the certs/keys are different than default. 

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

2.1.0

How reproducible:

Always

Steps to Reproduce:
1.Deploy MTV 
2.Try to change TLS settings
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fabien Dupont 2021-09-01 21:57:21 UTC
This is an internal change with no impact on MTV. Only regressions should be tested.

Comment 2 Ilanit Stein 2021-11-14 06:44:19 UTC
No regression has been found in regards to this change so far.
Thus moving bug to VERIFIED.

Comment 5 errata-xmlrpc 2021-12-09 19:20:47 UTC
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 (MTV 2.2.0 Images), 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/RHEA-2021:5066