Add to Fuel UI field with number of retries for puppet run
Bug #1510912 reported by
Vladimir Sharshov
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:/
Changed in fuel: | |
status: | Confirmed → Triaged |
importance: | Medium → High |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/239898 /git.openstack. org/cgit/ openstack/ fuel-astute/ commit/ ?id=687458e949d edfa6877e3a2e68 3f8ee0c1cbd43c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 687458e949dedfa 6877e3a2e683f8e e0c1cbd43c
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 f95a1d493db8e00 c95db9bc67.
This reverts commit c145db34762532b
Change-Id: I8d3b98d66df19f 070f6b061348692 48a7c3d45fc