commit 7c0485eb1a8c75a57936eaecce935091659429e9
Author: Vladimir Sharshov (warpc) <email address hidden>
Date: Fri Dec 30 14:11:36 2016 +0300
Network problem tolerance puppet status check
Connection between node and Astute can be lost some
times, so we need more tries to get info about task
status on node.
Two changes:
- instead of 1 try Astute will run 6 tries with 10
timeout for every attempt;
- it will process such behavior for puppet using separately
retries: puppet_undefined_retries
Instead of full puppet retry status retry is safety because
it is idempotent.
Puppet undefined retries can be setup using Astute config
or sending undefined_retries in puppet task parameters same
way as for usual retries. Most important thing: it will refresh
to original value every time when Astute get defined answer.
Reviewed: https:/ /review. openstack. org/415860 /git.openstack. org/cgit/ openstack/ fuel-astute/ commit/ ?id=7c0485eb1a8 c75a57936eaecce 935091659429e9
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7c0485eb1a8c75a 57936eaecce9350 91659429e9
Author: Vladimir Sharshov (warpc) <email address hidden>
Date: Fri Dec 30 14:11:36 2016 +0300
Network problem tolerance puppet status check
Connection between node and Astute can be lost some
times, so we need more tries to get info about task
status on node.
Two changes:
- instead of 1 try Astute will run 6 tries with 10 undefined_ retries
timeout for every attempt;
- it will process such behavior for puppet using separately
retries: puppet_
Instead of full puppet retry status retry is safety because
it is idempotent.
Puppet undefined retries can be setup using Astute config
or sending undefined_retries in puppet task parameters same
way as for usual retries. Most important thing: it will refresh
to original value every time when Astute get defined answer.
Change-Id: Ie86576a3400be5 a6b11041c8e6acf 89abf3bbd51
Related-Bug: #1653210
Closes-Bug: #1653737