Add to Fuel UI field with number of retries for puppet run

Bug #1510912 reported by Vladimir Sharshov
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
In Progress
High
Vladimir Sharshov
Mitaka
Won't Fix
High
Vladimir Sharshov

Bug Description

This bug for created, because we need more strong behavior in case of testing: zero retries. If production we should use several retires (by default 2). We should also add notice that this option do not override task retries if it setup explicitly.

Expected result:

In common settings of cluster we should add new field: default puppet retries number which should be set by default to 2. System test can change this params using Fuel cli by downloading, modifying and uploading cluster settings.

Related with: https://bugs.launchpad.net/fuel/+bug/1457887

Changed in fuel:
status: Confirmed → Triaged
importance: Medium → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to fuel-astute (master)

Reviewed: https://review.openstack.org/239898
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=687458e949dedfa6877e3a2e683f8ee0c1cbd43c
Submitter: Jenkins
Branch: master

commit 687458e949dedfa6877e3a2e683f8ee0c1cbd43c
Author: Vladimir Sharshov <email address hidden>
Date: Wed Oct 28 10:31:35 2015 +0000

    Revert "Don't use retries for puppet deployments by default"

    Instead of just setup zero retries we should give ability to
    changing this parameter explicitly using web interface or fuel
    cli

    Related-Bug: #1510912
    This reverts commit c145db34762532bf95a1d493db8e00c95db9bc67.

    Change-Id: I8d3b98d66df19f070f6b06134869248a7c3d45fc

Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

This is feature. Move it to 9.0 because Soft Code Freeze was reached.

Changed in fuel:
milestone: 8.0 → 9.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to fuel-web (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/266400

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-astute (master)

Fix proposed to branch: master
Review: https://review.openstack.org/266445

Changed in fuel:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-astute (master)

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/266445
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-web (master)

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/266400
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Changed in fuel:
milestone: 9.0 → 10.0
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

This is a feature request. Removing from the Mitaka release because we don't backport patches of this kind.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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