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 1503700 - 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 7
Classification: Red Hat
Component: virt-who
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks: 1506263 1506546
TreeView+ depends on / blocked
 
Reported: 2017-10-18 14:51 UTC by Chris Snyder
Modified: 2019-10-28 07:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1506263 1506546 (view as bug list)
Environment:
Last Closed: 2018-04-10 16:21:32 UTC
Target Upstream Version:
Embargoed:
toneata: needinfo-

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:46:48 UTC
Red Hat Product Errata RHEA-2018:0895 0 None None None 2018-04-10 16:22:08 UTC

Description Chris Snyder 2017-10-18 14:51:26 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.19-6 (and older, until virt-who-0.14-9 RHEL 7.2)

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:
- with an exponential backoff from 2 second polling time to 32 seconds
- respecting http 429s (if they include a retry-after header, using that)
- with a maximum polling time of 24 hours (if a job has not completed by then, log it and move on to the next)
Comment 1 Oneata Mircea Teodor 2017-10-18 15:05:59 UTC 
(In reply to Chris Snyder from comment #0)
> 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.19-6 (and older, until virt-who-0.14-9 RHEL 7.2)
> 
> 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:
> - with an exponential backoff from 2 second polling time to 32 seconds
> - respecting http 429s (if they include a retry-after header, using that)
> - with a maximum polling time of 24 hours (if a job has not completed by
> then, log it and move on to the next)

Hello, 
This is an illegal clone if it's done directly into z stream. Zstream clones are issued for y stream bugs. Please review the zstream process for cloning bugs.
https://mojo.redhat.com/docs/DOC-1021938#jive_content_id_The_goal
Thank you
Comment 2 Chris Snyder 2017-10-18 18:11:05 UTC 
Fair enough.

@Dev the work for this bug is now to verify that this has been fixed in virt-who for RHEL 7.5. If it has not, this bug will track the PR associated with the fix.
If it has been fixed in virt-who for 7.5, we'll move this bug along when the first build for 7.5 is produced.
Comment 3 Eko 2017-10-19 14:13:20 UTC 
*** Bug 1503011 has been marked as a duplicate of this bug. ***
Comment 4 Chris Snyder 2017-10-19 20:25:23 UTC 
Moving to MODIFIED as the fix has been merged upstream and will be included in the first build for 7.5.
Comment 18 errata-xmlrpc 2018-04-10 16:21:32 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/RHEA-2018:0895
Note You need to log in before you can comment on or make changes to this bug.