Bug 1503700

Summary: Virt-who polls job status too quickly
Product: Red Hat Enterprise Linux 7 Reporter: Chris Snyder <csnyder>
Component: virt-whoAssignee: candlepin-bugs
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact:
Priority: high    
Version: 7.4CC: hsun, rjerrido, toneata, yuefliu
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: toneata: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1506263 1506546 (view as bug list) Environment:
Last Closed: 2018-04-10 16:21:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1506263, 1506546    

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