Back to bug 1514004

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2017-11-16 13:24:28 UTC Target Milestone ovirt-4.3.0 ---
Red Hat Bugzilla Rules Engine 2017-11-16 13:36:03 UTC Depends On 1451297
Target Milestone --- ovirt-4.3.0
Link ID Red Hat Knowledge Base (Solution) 2335221
Link ID Red Hat Knowledge Base (Solution) 2845461
Target Milestone ovirt-4.3.0 ---
Martin Perina 2017-11-16 15:12:18 UTC Target Milestone --- ovirt-4.3.0
Oved Ourfali 2018-01-04 09:47:56 UTC CC oourfali
Martin Perina 2018-01-04 14:00:08 UTC Target Milestone ovirt-4.3.0 ovirt-4.4.0
PnT Account Manager 2018-03-05 15:11:50 UTC CC bazulay
Lukas Svaty 2018-10-25 11:39:19 UTC CC lsvaty
QA Contact jbelka pmatyas
PnT Account Manager 2018-10-31 23:19:29 UTC CC jbelka
Martin Perina 2019-01-07 08:34:51 UTC Status NEW POST
Link ID oVirt gerrit 96647
Target Milestone ovirt-4.4.0 ovirt-4.3.0
Martin Perina 2019-01-07 08:35:03 UTC Assignee pkliczew mperina
Moran Goldboim 2019-01-07 09:06:57 UTC CC mgoldboi
Yaniv Kaul 2019-01-07 09:10:55 UTC CC ykaul
Martin Perina 2019-01-10 19:40:44 UTC Status POST MODIFIED
Martin Perina 2019-01-10 19:41:54 UTC Doc Text TLSv1 and TLSv1.1 protocols are no longer secure, so they are forcefully disabled in VDSM configuration and cannot no longer be enabled within configuration.

Only TLSv1.2 and higher version of protocols are enabled, exact versions depends on underlying openssl version.
Doc Type Enhancement Release Note
Dusan Fodor 2019-01-16 00:40:11 UTC Status MODIFIED ON_QA
CC dfodor
Sandro Bonazzola 2019-01-16 10:24:50 UTC Fixed In Version v4.30.6
Petr Matyáš 2019-01-17 09:29:56 UTC Status ON_QA VERIFIED
Rolfe Dlugy-Hegwer 2019-01-17 19:34:04 UTC CC rdlugyhe
Docs Contact rdlugyhe
Doc Text TLSv1 and TLSv1.1 protocols are no longer secure, so they are forcefully disabled in VDSM configuration and cannot no longer be enabled within configuration.

Only TLSv1.2 and higher version of protocols are enabled, exact versions depends on underlying openssl version.
TLSv1 and TLSv1.1 protocols are no longer secure, so they are forcefully disabled in the VDSM configuration and cannot be enabled.

Only TLSv1.2 and higher versions of the protocol are enabled. The exact version enabled depends on underlying OpenSSL version.
Rolfe Dlugy-Hegwer 2019-01-21 16:20:47 UTC Doc Text TLSv1 and TLSv1.1 protocols are no longer secure, so they are forcefully disabled in the VDSM configuration and cannot be enabled.

Only TLSv1.2 and higher versions of the protocol are enabled. The exact version enabled depends on underlying OpenSSL version.
The TLSv1 and TLSv1.1 protocols are no longer secure. They have been forcefully disabled in the VDSM configuration and cannot be enabled.

Only TLSv1.2 and higher versions of the protocol are enabled. The exact version enabled depends on the underlying OpenSSL version.
Rolfe Dlugy-Hegwer 2019-04-11 17:08:28 UTC Doc Text The TLSv1 and TLSv1.1 protocols are no longer secure. They have been forcefully disabled in the VDSM configuration and cannot be enabled.

Only TLSv1.2 and higher versions of the protocol are enabled. The exact version enabled depends on the underlying OpenSSL version.
The TLSv1 and TLSv1.1 protocols are no longer secure. In the current release, they have been forcefully disabled in the VDSM configuration and cannot be enabled. Only TLSv1.2 and higher versions of the protocol are enabled. The exact version enabled depends on the underlying OpenSSL version.
Gil Klein 2019-04-14 12:37:04 UTC CC gklein
errata-xmlrpc 2019-04-30 00:04:20 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2019-05-08 12:35:59 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2019-05-08 12:35:59 UTC
errata-xmlrpc 2019-05-08 12:36:29 UTC Link ID Red Hat Product Errata RHBA-2019:1077
Red Hat One Jira (issues.redhat.com) 2021-08-30 12:10:52 UTC Link ID Red Hat Issue Tracker RHV-43208

Back to bug 1514004