Openstack client puppet provider should retry failed commands
Bug #1485638 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Max Yatsenko |
Bug Description
Openstack client (OSC) provider raises puppet error on a first keystone service error encountered, like 503 Service unavailable.
While the correct fix would be to ensure keystone service (haproxy backend) always availabe while issuing commands to OSC provider, this seems barely possible in Fuel deploy patterns. Hence, retries should present as well.
Changed in fuel: | |
assignee: | MOS Deployment Automation Team (mos-da) → MOS Puppet Team (mos-puppet) |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | MOS Puppet Team (mos-puppet) → Max Yatsenko (myatsenko) |
Changed in fuel: | |
importance: | Critical → High |
tags: | added: area-mos |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: non-release |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The deployment impact is critical and there are multiple duplicates.