Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
After system has been registered to SAM server, Though virt-who run normally, it will pop up some error message during communicate with subscription manager occasionally.
Version-Release number of selected component (if applicable):
subscription-manager-1.12.12-1.el6.x86_64
python-rhsm-1.12.5-1.el6.x86_64
virt-who-0.10-6.el6.noarch
How reproducible:
Always
Steps to Reproduce:
1. Register system to SAM server and make sure virt-who run at libvirtd mode normally
virt-who configuration:
VIRTWHO_BACKGROUND=1
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=5
2. Check the virt-who status
[root@dhcp-128-110 libvirt-test-API]# service virt-who status
virt-who (pid 32168) is running...
3. Check the virt-who's log in the /var/log/rhsm/rhsm.log
Actual results:
virt-who run normally, But sometimes it will generate some error log when communicate with subscription-manager as the following, please see detail in the attachment.
"RestlibException: Runtime Error Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1 at org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched:81"
Expected results:
virt-who should communicate with subscription-manager normally when it's running .it shouldn't pop up any error messages in the log file.
Additional info:
This is a problem server side in candlepin, moving components.
Liushihui if you could provide information about the version of SAM being used, and if possible the candlepin.log or a katello-debug tar.gz from the SAM server after this has happened, that would be ideal. With just this one line we're probably not going to be able to tell exactly what happened server side, though it looks like an issue that is likely already fixed in candlepin master.
Comment 8RHEL Program Management
2014-11-21 15:43:44 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Do the same test with latest rhel6.6 against SAM-1.4.1-RHEL-6-20141113.0, it still occurred on this build,please see the rhsm.log, candlepin.log and katello-debug tar.gz in the attachment.
Version-Release number of selected component (if applicable):
subscription-manager-1.12.14-7.el6.x86_64
python-rhsm-1.12.5-2.el6.x86_64
virt-who-0.10-8.el6.noarch
katello-headpin-1.4.3.28-1.el6sam_splice.noarch
candlepin-0.9.6.5-1.el6sam.noarch