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.
Bug 1220977 - RFE: virt-who limit the interval at no less than 1 minute
Summary: RFE: virt-who limit the interval at no less than 1 minute
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: gaoshang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-13 01:51 UTC by Liushihui
Modified: 2016-12-01 00:35 UTC (History)
7 users (show)

Fixed In Version: virt-who-0.16-1.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 23:55:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0859 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2016-05-10 22:44:47 UTC

Description Liushihui 2015-05-13 01:51:02 UTC
Description of problem:
When virt-who interval is small(eg: VIRTWHO_INTERVAL=5), it's very easy lead to  virt-who failed to communication with subscription manager,please see bug 1105053 and bug 1216278 

Version-Release number of selected component (if applicable):
virt-who-0.12-7.el6.noarch
subscription-manager-1.14.6-1.el6.x86_64
python-rhsm-1.14.2-1.el6.x86_64
candlepin-0.9.49.0-1.el7.noarch
katello-2.2.0.8-1.el7sat.noarch
foreman-1.7.2.19-1.el7sat.noarch
Satellite-6.1.0-RHEL-7-20150506.0

How reproducible:
Always

Steps to Reproduce:
1. Register system to Satellite/SAM
2. Configure virt-who interval to 5 then restart virt-who service
# vim /etc/sysconfig/virt-who
VIRTWHO_BACKGROUND=1
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=5
# service virt-who restart
3.Unregister system
# subscription-manager unregister
# tail -f /var/log/rhsm/rhsm.log
2015-05-11 17:07:08,882 [ERROR]  @virtwho.py:115 - Error in communication with subscription manager:
Traceback (most recent call last):
  File "/usr/share/virt-who/virtwho.py", line 102, in send
    self._sendGuestList(report)
  File "/usr/share/virt-who/virtwho.py", line 121, in _sendGuestList
    manager.sendVirtGuests(report.guests)
  File "/usr/share/virt-who/manager/subscriptionmanager/subscriptionmanager.py", line 119, in sendVirtGuests
    self.connection.updateConsumer(self.uuid(), guest_uuids=domains)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 858, in updateConsumer
    ret = self.conn.request_put(method, params)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 611, in request_put
    return self._request("PUT", method, params)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 505, in _request
    conn.request(request_type, handler, body=body, headers=headers)
  File "/usr/lib64/python2.6/httplib.py", line 936, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib64/python2.6/httplib.py", line 973, in _send_request
    self.endheaders()
  File "/usr/lib64/python2.6/httplib.py", line 930, in endheaders
    self._send_output()
  File "/usr/lib64/python2.6/httplib.py", line 802, in _send_output
    self.send(msg)
  File "/usr/lib64/python2.6/httplib.py", line 761, in send
    self.connect()
  File "/usr/lib64/python2.6/site-packages/M2Crypto/httpslib.py", line 73, in connect
    raise error
error: [Errno 4] Interrupted system call

Actual results:
When the refresh interval is too small, It will show many error messages when virt-who communication with subscription manager

Expected results:
If virt-who can limit the interval to at least 1 minute, it won't generate these errors 

Additional info:

Comment 2 Radek Novacek 2015-05-26 08:37:56 UTC
Well, I think the ability to set interval to arbitrary value is quite useful at least for testing.

On the other hand, we could state that intervals under one minute are not supported, but virt-who would continue to work normally.

What do you think?

Comment 3 Liushihui 2015-06-01 02:04:30 UTC
Yes, I totally agree. I think it is better to add the statement to virt-who's user doc.Thanks.

Comment 4 Chris Snyder 2015-09-02 20:54:27 UTC
commit c4d71d00a4578665bd9fb6517d04643dedbd0e57
Author: William Poteat <wpoteat>
Date:   Thu Jul 2 14:44:00 2015 -0400

    Limits interval settings
    
    Makes the default interval the minimal interval
    
    Removes heartbeat interval

The minimum interval has been set to 10 minutes as of the above commit.
I am presently working on better rate limiting that should allow us to lower the minimum interval.

Comment 5 Radek Novacek 2015-12-17 12:28:43 UTC
Fixed by rebase to virt-who-0.16-1.el6.

Comment 7 Liushihui 2016-02-23 05:17:21 UTC
Verified it on virt-who-0.16-4.el6.noarch since virt-who's default refresh interval has updated to 60s.Therefore, verified it.

Comment 9 errata-xmlrpc 2016-05-10 23:55:05 UTC
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/RHEA-2016-0859.html


Note You need to log in before you can comment on or make changes to this bug.