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 1448267 - When receive 429 info for stage candlepin, it will loop to show log "Trying again in 60" every 60s.
Summary: When receive 429 info for stage candlepin, it will loop to show log "Trying a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.4
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Chris Snyder
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-05 03:52 UTC by yuefliu
Modified: 2019-10-28 07:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 19:26:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github virt-who virt-who pull 67 0 None None None 2017-05-10 20:37:36 UTC
Red Hat Product Errata RHBA-2017:2084 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2017-08-01 18:14:28 UTC

Comment 3 Kevin Howell 2017-05-08 14:53:17 UTC 
> - without oneshot option, virt-who should loop to restart with 60s, 120s and 180s, then send mapping info out successfully.

Where did this expectation come from?

Did this work as expected in a prior virt-who release?
Comment 4 yuefliu 2017-05-09 01:32:24 UTC 
Yes, it worked as expected before virt-who-0.19, now 429 info makes virt-who keeping restart every 60s, cannot stop and send mapping info out, which have blocked all our automation test for stage candlepin.
Comment 5 Chris Snyder 2017-05-09 16:54:59 UTC 
A couple of comments on the issues in this bug.

Regarding the issue of CTRL-C causing virt-who to loop without waiting, I believe that is an issue and it shall be fixed.

As the RFC below[1] specifies that the 429 response MAY or MAY NOT include the Retry-After header I propose the new behavior be as follows:

If the response includes Retry-After -> wait Retry-After seconds and try again
If the response does not include Retry-After -> wait 60s * number of failures for the given request. (So for the first failure wait 60s, for the second subsequent failure wait 120s, for the third subsequent failure wait 180s).


[1]: https://tools.ietf.org/html/rfc6585
Comment 6 Chris Snyder 2017-05-10 20:37:37 UTC 
Attaching a PR with my proposed changes to solve this bug.
Comment 8 yuefliu 2017-06-08 08:15:14 UTC 
Verified the bug with virt-who-0.19-5, it works as design to wait 60s and try again.
Comment 9 errata-xmlrpc 2017-08-01 19:26:06 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:2084
Note You need to log in before you can comment on or make changes to this bug.