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 1507786 - Virt-who polls job status too quickly [rhel-6.9.z]
Summary: Virt-who polls job status too quickly [rhel-6.9.z]
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: 1506371
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-31 07:34 UTC by Oneata Mircea Teodor
Modified: 2017-11-14 21:00 UTC (History)
8 users (show)

Fixed In Version: virt-who-0.18-4.el6_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1506371
Environment:
Last Closed: 2017-11-14 21:00:53 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-31 07:34:27 UTC
Red Hat Product Errata RHBA-2017:3208 0 normal SHIPPED_LIVE virt-who bug fix update 2017-11-15 01:36:10 UTC

Description Oneata Mircea Teodor 2017-10-31 07:34:10 UTC 
This bug has been copied from bug #1506371 and has been proposed to be backported to 6.9 z-stream (EUS).
Comment 3 Eko 2017-11-03 02:30:08 UTC 
verified in virt-who-0.18-5.el6_9,

1. start virt-who service the first time, will wait for 15s to check the job state [PASS]
2. if 429 code received, but no Retry-After setting,will wait for 30s to check the job state [PASS]
3. if 429 code received, and set Retry-After to 10, will wait for 10s to check the job state [PASS]
4. if 404/500 code received, virt-who will be killed [PASS]
5. if two or more config files in /etc/virt-who.d, all the reports will be sent together, and then check the job state one by one(every 15s) [PASS]
Comment 5 errata-xmlrpc 2017-11-14 21:00:53 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-2017:3208
Note You need to log in before you can comment on or make changes to this bug.