-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-7.9.z
-
None
-
Low
-
subs-client-tools
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
-
57,005
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:
- external trackers