Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When starting virt-who, we receive a traceback of proccess failing to start due to md5 hashlib in a FIPS enabled environment [rhsm.log]:
2021-03-24 17:45:04,490 [virtwho.main DEBUG] MainProcess(1721):Thread-2 @virt.py:run:407 - Thread 'virtwho-config' started
2021-03-24 17:45:04,490 [virtwho.main DEBUG] MainProcess(1721):Thread-2 @esx.py:_prepare:136 - Log into ESX
2021-03-24 17:45:04,495 [virtwho.destination_8660975658016899216 DEBUG] MainProcess(1721):Thread-3 @virt.py:run:407 - Thread 'destination_8660975658016899216' started
2021-03-24 17:45:04,494 [virtwho.main ERROR] MainProcess(1721):Thread-2 @virt.py:run:421 - Thread 'virtwho-config' fails with exception:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/virtwho/virt/virt.py", line 412, in run
self._run()
File "/usr/lib/python3.6/site-packages/virtwho/virt/esx/esx.py", line 149, in _run
self._prepare()
File "/usr/lib/python3.6/site-packages/virtwho/virt/esx/esx.py", line 137, in _prepare
self.login()
File "/usr/lib/python3.6/site-packages/virtwho/virt/esx/esx.py", line 365, in login
self.client = suds.client.Client(wsdl, location="%s/sdk" % self.url, **kwargs)
File "/usr/lib/python3.6/site-packages/suds/client.py", line 120, in __init__
self.wsdl = reader.open(url)
File "/usr/lib/python3.6/site-packages/suds/reader.py", line 101, in open
id = self.mangle(url, "wsdl")
File "/usr/lib/python3.6/site-packages/suds/reader.py", line 61, in mangle
h = md5(name.encode()).hexdigest()
ValueError: [digital envelope routines: EVP_DigestInit_ex] disabled for FIPS
2021-03-24 17:45:04,501 [virtwho.main INFO] MainProcess(1721):Thread-2 @virt.py:_send_data:980 - Report for config "virtwho-config" gathered, placing in datastore
2021-03-24 17:45:04,501 [virtwho.main INFO] MainProcess(1721):Thread-2 @virt.py:run:440 - Waiting 60 seconds before performing action again 'virtwho-config'
2021-03-24 17:45:05,497 [virtwho.destination_8660975658016899216 DEBUG] MainProcess(1721):Thread-3 @subscriptionmanager.py:_connect:152 - Authenticating with certificate: /etc/pki/consumer/cert.pem
Version-Release number of selected component (if applicable):
virt-who-1.30.5-1.el8.noarch
How reproducible:
100%
Steps to Reproduce:
1. Build a fips enabled host (Or enable fips on a host)
[root@bootp-73-5-204 virt-who.d]# fips-mode-setup --enable
Kernel initramdisks are being regenerated. This might take some time.
Setting system policy to FIPS
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
FIPS mode will be enabled.
Please reboot the system for the setting to take effect.
[root@bootp-73-5-204 virt-who.d]# reboot
[root@bootp-73-5-204 ~]# cat /proc/sys/crypto/fips_enabled
1
2. Install virt-who (latest for RHEL 8.4)
3. service virt-who start
Actual results:
Traceback seen above
Expected results:
virt-who running and in reporting state.
Additional info:
Same error see: https://bugzilla.redhat.com/show_bug.cgi?id=1349640
Converting this bug as test only bug. Please retest the observation once the related Bug 1921920 is resolved.
Requesting needinfo from QE, please clear the need info flag once the observation is retested.
Description of problem: When starting virt-who, we receive a traceback of proccess failing to start due to md5 hashlib in a FIPS enabled environment [rhsm.log]: 2021-03-24 17:45:04,490 [virtwho.main DEBUG] MainProcess(1721):Thread-2 @virt.py:run:407 - Thread 'virtwho-config' started 2021-03-24 17:45:04,490 [virtwho.main DEBUG] MainProcess(1721):Thread-2 @esx.py:_prepare:136 - Log into ESX 2021-03-24 17:45:04,495 [virtwho.destination_8660975658016899216 DEBUG] MainProcess(1721):Thread-3 @virt.py:run:407 - Thread 'destination_8660975658016899216' started 2021-03-24 17:45:04,494 [virtwho.main ERROR] MainProcess(1721):Thread-2 @virt.py:run:421 - Thread 'virtwho-config' fails with exception: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/virtwho/virt/virt.py", line 412, in run self._run() File "/usr/lib/python3.6/site-packages/virtwho/virt/esx/esx.py", line 149, in _run self._prepare() File "/usr/lib/python3.6/site-packages/virtwho/virt/esx/esx.py", line 137, in _prepare self.login() File "/usr/lib/python3.6/site-packages/virtwho/virt/esx/esx.py", line 365, in login self.client = suds.client.Client(wsdl, location="%s/sdk" % self.url, **kwargs) File "/usr/lib/python3.6/site-packages/suds/client.py", line 120, in __init__ self.wsdl = reader.open(url) File "/usr/lib/python3.6/site-packages/suds/reader.py", line 101, in open id = self.mangle(url, "wsdl") File "/usr/lib/python3.6/site-packages/suds/reader.py", line 61, in mangle h = md5(name.encode()).hexdigest() ValueError: [digital envelope routines: EVP_DigestInit_ex] disabled for FIPS 2021-03-24 17:45:04,501 [virtwho.main INFO] MainProcess(1721):Thread-2 @virt.py:_send_data:980 - Report for config "virtwho-config" gathered, placing in datastore 2021-03-24 17:45:04,501 [virtwho.main INFO] MainProcess(1721):Thread-2 @virt.py:run:440 - Waiting 60 seconds before performing action again 'virtwho-config' 2021-03-24 17:45:05,497 [virtwho.destination_8660975658016899216 DEBUG] MainProcess(1721):Thread-3 @subscriptionmanager.py:_connect:152 - Authenticating with certificate: /etc/pki/consumer/cert.pem Version-Release number of selected component (if applicable): virt-who-1.30.5-1.el8.noarch How reproducible: 100% Steps to Reproduce: 1. Build a fips enabled host (Or enable fips on a host) [root@bootp-73-5-204 virt-who.d]# fips-mode-setup --enable Kernel initramdisks are being regenerated. This might take some time. Setting system policy to FIPS Note: System-wide crypto policies are applied on application start-up. It is recommended to restart the system for the change of policies to fully take place. FIPS mode will be enabled. Please reboot the system for the setting to take effect. [root@bootp-73-5-204 virt-who.d]# reboot [root@bootp-73-5-204 ~]# cat /proc/sys/crypto/fips_enabled 1 2. Install virt-who (latest for RHEL 8.4) 3. service virt-who start Actual results: Traceback seen above Expected results: virt-who running and in reporting state. Additional info: Same error see: https://bugzilla.redhat.com/show_bug.cgi?id=1349640