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 1506371 - Virt-who polls job status too quickly
Summary: Virt-who polls job status too quickly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.10
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks: 1506745 1507786
TreeView+ depends on / blocked
 
Reported: 2017-10-25 19:38 UTC by Chris Snyder
Modified: 2018-06-19 05:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1507786 (view as bug list)
Environment:
Last Closed: 2018-06-19 05:21:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github virt-who virt-who pull 103 0 None None None 2017-10-25 19:51:04 UTC
Red Hat Product Errata RHBA-2018:1915 0 None None None 2018-06-19 05:23:02 UTC

Description Chris Snyder 2017-10-25 19:38:05 UTC 
Description of problem:
When reporting is done asynchrounously, virt-who checks the status of the jobs it starts far too frequently. Specifically, all known jobs are effectively checked once every second.

This causes far too much traffic and is not necessary for proper async reporting.


Version-Release number of selected component (if applicable):
virt-who-0.18-3

How reproducible:
100%

Steps to Reproduce:
1. Just run virt-who with any valid configuration against any version of candlepin newer than or equal to 2.0

Actual results:
Virt-who checks the job status every second

Expected results:

Virt-who checks the job status:
- 15 second wait after job submission, 30 second wait thereafter
- respecting http 429s (if they include a retry-after header, using that)
Comment 8 errata-xmlrpc 2018-06-19 05:21:42 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://access.redhat.com/errata/RHBA-2018:1915
Note You need to log in before you can comment on or make changes to this bug.