Bug 2150053

Summary:	virt-who cannot report to Satellite when FIPS mode is enabled
Product:	Red Hat Enterprise Linux 7	Reporter:	Jessica Richards <jrichards2>
Component:	python-suds	Assignee:	Jeff Ortel <jortel>
Status:	NEW ---	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	aganbat, ahumbe, ptoscano, shughes
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Jessica Richards 2022-12-01 18:12:34 UTC

Description of problem:

On a Satellite 6 server on RHEL 7, where FIPS was enabled at build time, virt-who fails to update Satellite.


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

virt-who-0.28.10-1.el7_9.noarch
satellite-6.11.4-2.el7sat.noarch
redhat-release-server-7.9-6.el7_9.x86_64


How reproducible:

unclear; only one example so far


Steps to Reproduce:
1.  create a RHEL 7 host with FIPS enabled
2.  install satellite
3.  configure virt-who for a VMware environment
4.  check the logs:  /var/log/rhsm/rhsm.log, /var/log/foreman-installer/satellite.log, /var/log/secure

Actual results:

The Satellite server doesn't show new hypervisors under Hosts > All Hosts, and subscriptions like RHEL for VDC don't work when applied to guests of hypervisors.

Log entries like these in /var/log/rhsm/rhsm.log:

Nov 30 09:42:07 SERVERNAME /usr/bin/virt-who: 2022-11-30 09:42:07,830 [virtwho.main ERROR] MainProcess(9193):Thread-3 @virt.py:run:416 - Thread 'virt-who-config-2' fails with error: Cannot recv data: FIPS mode initialized#015#012Host key verification failed.: Connection reset by peer
Nov 30 09:42:07 SERVERNAME /usr/bin/virt-who: 2022-11-30 09:42:07,835 [virtwho.main ERROR] MainProcess(9193):Thread-5 @libvirtd.py:_connect:288 - Error in libvirt backend#012libvirtError: Cannot recv data: Value too large for defined data type


Expected results:

The Satellite server should show new hypervisors under Hosts > All Hosts, and subscriptions like RHEL for VDC should work when applied to guests of subscribed hypervisors.


Additional info:

Comment 3 Pino Toscano 2022-12-06 13:40:01 UTC

Note that there were issues in the Python library, suds, used to do SOAP communication with ESX; in RHEL 8, this was handled as bug 1921920 (bug 2051883).