Recently introduced retry function suffers from several issues.

Bug #1674358 reported by VIncent S. Cojot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

There were multiple issues in retry() in rhel-registration:
 - There was no need for it to be recursive (local variables
   got overwritten)
 - There was no delay between multiple attempts, leading to faster but
   more frequent failures.
 - The max number of attempts was set too low for some environements.

This is fixed by: https://review.openstack.org/#/c/445045

It would be very useful to backport this as far as stable/newton.
Thank you,
Vincent

Revision history for this message
Michael Turek (mjturek) wrote :

Seems unrelated to Ironic, switching over to tripleo bug. Let me know if you disagree.

affects: ironic → tripleo
Revision history for this message
VIncent S. Cojot (vincent-m) wrote :

Sorry about that, Thanks Michael.

Revision history for this message
Emilien Macchi (emilienm) wrote :

Vincent, please backport the fixes to stable/ocata and stable/newton and add in the commit message (at the end): Closes-Bug: #1674358

Thanks

Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-1
assignee: nobody → VIncent S. Cojot (vincent-m)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/447671

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/ocata)

Reviewed: https://review.openstack.org/447671
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1652f1b2518a60bfbfbd1f3f3714e8c22d4e17e5
Submitter: Jenkins
Branch: stable/ocata

commit 1652f1b2518a60bfbfbd1f3f3714e8c22d4e17e5
Author: Vincent S. Cojot <email address hidden>
Date: Mon Mar 13 14:39:16 2017 -0400

    Fixes multiple issues with retry function in rhel-registration.

    There were multiple issues in retry() in rhel-registration:
     - There was no need for it to be recursive (local variables
       got overwritten)
     - There was no delay between multiple attempts, leading to faster but
       more frequent failures.
     - The max number of attempts was set too low for some environements.

    With this patch, rhel-registration now works more reliably with slow-links
    for portal registration and does not attempt to DDos the portal or your
    satellite server.

    Closes-Bug: #1674358
    Change-Id: I594d3c94867b45a7a58766dbcc66edead78d6a4e
    (cherry picked from commit 038eae089130bc3a814897c0e282223de16f4658)

tags: added: in-stable-ocata
Changed in tripleo:
milestone: pike-1 → pike-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 6.1.0

This issue was fixed in the openstack/tripleo-heat-templates 6.1.0 release.

Changed in tripleo:
milestone: pike-2 → pike-3
Revision history for this message
Emilien Macchi (emilienm) wrote :

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

Changed in tripleo:
assignee: VIncent S. Cojot (vincent-m) → nobody
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.