Loading...

XML

Word

Printable

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Release Note Text:

Hide
In {project-short} 2.11.0, an update to Golang 1.25 causes a connection failure on FIPS-enabled clusters with VMware 6 or 7, due to unsupported TLS 1.2 with Extended Master Secret. As a consequence, users cannot migrate vSphere 6 or 7 VMs to a FIPS-compliant cluster.
+
*Workaround:* Disable FIPS mode on the cluster or use a vSphere version that supports TLS 1.2 with Extended Master Secret to migrate VMs.
+
link:https://issues.redhat.com/browse/MTV-4411[~~MTV-4411~~]

Show
In {project-short} 2.11.0, an update to Golang 1.25 causes a connection failure on FIPS-enabled clusters with VMware 6 or 7, due to unsupported TLS 1.2 with Extended Master Secret. As a consequence, users cannot migrate vSphere 6 or 7 VMs to a FIPS-compliant cluster. + *Workaround:* Disable FIPS mode on the cluster or use a vSphere version that supports TLS 1.2 with Extended Master Secret to migrate VMs. + link: https://issues.redhat.com/browse/MTV-4411 [ MTV-4411 ]
Release Note Status:
Done
Intelligence Requested:
Market:

Description of problem:

From MTV 2.11.0, MTV update the golang version to 1.25 which enforcec TLS 1.2 with Extended Master Secret. https://go.dev/doc/go1.25 commit

However the VMware 6 and 7 do not support TLS 1.2 with Extended Master Secret.

This is known issue on the MTV

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

2.11.0

How reproducible:

Always

Steps to Reproduce:

1. FIPS enabled cluster
2. Create VMware provider to VMware 6 or 7
3. Failing to connect

Actual results:

Failing to connect

is caused by

MTV-4411 MTV with FIPS cluster can not connect to VMware 6 and 7

is related to

MTV-4412 [DOC] MTV with FIPS cluster can not connect to VMware 6 and 7