summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-cluster/upgrades/rpm_upgrade.yml
Commit message (Collapse)AuthorAgeFilesLines
* Stop restarting node after upgrading master rpms.Devan Goodwin2016-10-121-3/+0
| | | | | | | | | | This looks to be causing a customer issue where some HA upgrades fail, due to a missing EgressNetworkPolicy API. We update master rpms, we don't restart services yet, but then restart node service which tries to talk to an API that does not yet exist. (pending restart) Restarting node here is very out of place and appears to not be required.
* Introduce 1.3/3.3 upgrade path.Devan Goodwin2016-07-251-0/+10
Refactored the 3.2 upgrade common files out to a path that does not indicate they are strictly for 3.2. 3.3 upgrade then becomes a relatively small copy of the byo entry point, all calling the same code as 3.2 upgrade. Thus far there are no known 3.3 specific upgrade tasks. In future we will likely want to allow hooks out to version specific pre/upgrade/post tasks. Also fixes a bug where the handlers were not restarting nodes/openvswitch containers doing upgrades, due to a change in Ansible 2+.