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:
virt-who errors out when you delete profiles it reported from Satellite 5.
Version-Release number of selected component (if applicable):
virt-who-0.12-10.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. # rm -rf /var/lib/virt-who/*
2. # virt-who --one-shot --satellite5 --esx --satellite-server=<sat5>
--satellite-username=<satuser> --satellite-password=<satpass>
--esx-server=<vCenter> --esx-username=<esxuser> --esx-password=<esxpass>
3. Now delete profiles it has created on Sat5
4. # virt-who --one-shot --satellite5 --esx --satellite-server=<sat5>
--satellite-username=<satuser> --satellite-password=<satpass>
--esx-server=<vCenter> --esx-username=<esxuser> --esx-password=<esxpass>
Actual results:
2016-02-25 12:20:32,161 INFO: Using configuration "env/cmdline" ("esx" mode)
2016-02-25 12:20:43,125 INFO: Initialized satellite connection
2016-02-25 12:20:43,126 INFO: Sending update in hosts-to-guests mapping: {[...]}
2016-02-25 12:20:43,893 ERROR: Unable to send data: Unable to send host/guest assocaition to the satellite: <Fault -9: '\nError Message:\n Please run rhn_register as root on this client\nError Class Code: 9\nError Class Info: Invalid System Credentials.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please consult the Red Hat Customer Portal Knowledge Base\n landing page on common registration Error Class Codes at\n https://access.redhat.com/solutions/17036 for a possible resolution.\n If you choose to open a support case in the Red Hat Customer Portal,\n please be sure to include details of what you were trying to do when\n this error occurred and specifics on how to reproduce this problem.\n'>
Expected results:
Should work.
Additional info:
When you `rm -rf /var/lib/virt-who/*`, it works again.
When on this, there is also small typo in the error message above: assocaition -> association.
This was spotted when working on bug 1268799.
Verified the bug on virt-who-0.18-3.el6.noarch with satellite5.7, do as the bug's steps, host/guest mapping info can be sent to sat server successfully after delete profiles by run 'rm -rf /var/lib/virt-who/*', no such bug reproduce, so verified it.
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, 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://rhn.redhat.com/errata/RHBA-2017-0675.html
Description of problem: virt-who errors out when you delete profiles it reported from Satellite 5. Version-Release number of selected component (if applicable): virt-who-0.12-10.el6.noarch How reproducible: always Steps to Reproduce: 1. # rm -rf /var/lib/virt-who/* 2. # virt-who --one-shot --satellite5 --esx --satellite-server=<sat5> --satellite-username=<satuser> --satellite-password=<satpass> --esx-server=<vCenter> --esx-username=<esxuser> --esx-password=<esxpass> 3. Now delete profiles it has created on Sat5 4. # virt-who --one-shot --satellite5 --esx --satellite-server=<sat5> --satellite-username=<satuser> --satellite-password=<satpass> --esx-server=<vCenter> --esx-username=<esxuser> --esx-password=<esxpass> Actual results: 2016-02-25 12:20:32,161 INFO: Using configuration "env/cmdline" ("esx" mode) 2016-02-25 12:20:43,125 INFO: Initialized satellite connection 2016-02-25 12:20:43,126 INFO: Sending update in hosts-to-guests mapping: {[...]} 2016-02-25 12:20:43,893 ERROR: Unable to send data: Unable to send host/guest assocaition to the satellite: <Fault -9: '\nError Message:\n Please run rhn_register as root on this client\nError Class Code: 9\nError Class Info: Invalid System Credentials.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please consult the Red Hat Customer Portal Knowledge Base\n landing page on common registration Error Class Codes at\n https://access.redhat.com/solutions/17036 for a possible resolution.\n If you choose to open a support case in the Red Hat Customer Portal,\n please be sure to include details of what you were trying to do when\n this error occurred and specifics on how to reproduce this problem.\n'> Expected results: Should work. Additional info: When you `rm -rf /var/lib/virt-who/*`, it works again. When on this, there is also small typo in the error message above: assocaition -> association. This was spotted when working on bug 1268799.