Host errors are not fatal
Bug #1833737 reported by
Mark Goddard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
High
|
Mark Goddard | ||
Antelope |
Confirmed
|
High
|
Unassigned | ||
Bobcat |
Fix Released
|
High
|
Mark Goddard | ||
Yoga |
New
|
High
|
Unassigned | ||
Zed |
Confirmed
|
High
|
Unassigned |
Bug Description
Currently we are using the default value of 'false' for
'any_errors_fatal'. This means that plays will execute until the end or
all hosts have failed. A host can fail and others may continue. This can
lead to odd situations, and makes errors harder to diagnose.
One specific example of where this can be an issue is during upgrade. If
one host fails early on, then it will not be upgraded. For clustered
services such as RabbitMQ or MariaDB this can cause problems. Many
OpenStack services have specific instructions for rolling upgrades which
would not work well if one or more hosts are not involved.
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/666876
Review: https:/