Bug 2054504
| Summary: | Failed to run virt-who in esx mode with fips enabled | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | yuefliu <yuefliu> |
| Component: | virt-who | Assignee: | Pino Toscano <ptoscano> |
| Status: | CLOSED ERRATA | QA Contact: | yuefliu <yuefliu> |
| Severity: | urgent | Docs Contact: | Jiri Herrmann <jherrman> |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | hsun, jherrman, jhnidek, kuhuang, ptoscano, redakkan, wpoteat |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-who-1.31.23-1.el9 | Doc Type: | Bug Fix |
| Doc Text: |
.`virt-who` now connects to ESX servers correctly when in FIPS mode
Previously, when using the `virt-who` utility on a RHEL 9 system in FIPS mode, `virt-who` could not connect to ESX servers. As a consequence, `virt-who` did not report any ESX servers, even if configured for them, and logged the following error message:
----
ValueError: [digital envelope routines] unsupported
----
With this update, `virt-who` has been fixed to handle FIPS mode correctly, and the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 10:13:34 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: | |||
| Bug Blocks: | 2027125 | ||
|
Comment 1
Pino Toscano
2022-02-17 12:31:51 UTC
From bug 1921920 there is an attempt to fix it upstream: https://github.com/suds-community/suds/pull/72 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 (virt-who bug fix and enhancement update), 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/RHBA-2022:8055 |