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.
DescriptionJessica 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:
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).
Comment 8RHEL Program Management
2023-09-05 11:06:33 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9RHEL Program Management
2023-09-05 12:03:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.