summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-cluster/upgrades
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Revert "Fix OpenStack cloud provider"Scott Dodson2016-11-071-6/+4
| |/ | | | | | | This reverts commit 1f2276fff1e41c1d9440ee8b589042ee249b95d7.
* / Add missing symlink for node openvswitch oom fix.Devan Goodwin2016-11-081-0/+1
|/
* Merge pull request #2637 from dgoodwin/ctrl-plane-restartScott Dodson2016-10-251-9/+6
|\ | | | | Fix and reorder control plane service restart.
| * Fix and reorder control plane service restart.Devan Goodwin2016-10-211-9/+6
| | | | | | | | | | | | | | | | | | This was missed in the standalone upgrade control plane playbook. However it also looks to be out of order, we should restart before reconciling and upgrading nodes. As such moved the restart directly into the control plane upgrade common code, and placed it before reconciliation.
* | [upgrades] Fix containerized nodeScott Dodson2016-10-251-2/+0
| | | | | | | | This file was removed and no longer used
* | Move infrastructure templates into openshift_hosted_templates role.Andrew Butcher2016-10-211-0/+4
| |
* | trouble creating service signer while running upgrade dockerizedHenning Fjellheim2016-10-211-4/+4
| |
* | Merge pull request #2623 from rhcarvalho/typosAndrew Butcher2016-10-201-1/+1
|\ \ | | | | | | Fix typos
| * | Fix typosRodolfo Carvalho2016-10-191-1/+1
| | |
* | | Merge pull request #2621 from dgoodwin/symlink-fixScott Dodson2016-10-193-11/+7
|\ \ \ | |/ / |/| | Switch from "oadm" to "oc adm" and fix bug in binary sync.
| * | Switch from "oadm" to "oc adm" and fix bug in binary sync.Devan Goodwin2016-10-193-11/+7
| |/ | | | | | | | | | | | | | | Found bug syncing binaries to containerized hosts where if a symlink was pre-existing, but pointing to the wrong destination, it would not be corrected. Switched to using oc adm instead of oadm.
* / Template with_items for upstream ansible-2.2 compat.Andrew Butcher2016-10-143-3/+3
|/
* Resume restarting node after upgrading node rpms.Devan Goodwin2016-10-141-0/+4
| | | | | | | Error in commit 245fef16573757b6e691c448075d8564f5d569f4. As it turns out this is the only place a rpm based node can be restarted in upgrade. Restoring the restart but making it conditional to avoid the two issues reported with out of sync node restarts.
* upgrade: Don't check avail docker version if not already installed.Devan Goodwin2016-10-141-2/+4
|
* 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.
* Fix bug with service signer cert on upgrade.Devan Goodwin2016-09-292-1/+7
| | | | | | It is invalid Ansible to use a when on an include that contains plays, as it cannot be applied to plays. Issue filed upstream for a better error, or to get it working.
* Use pre_upgrade tag instread of a dry run variable.Devan Goodwin2016-09-291-1/+1
|
* Move etcd backup from pre-upgrade to upgrade itself.Devan Goodwin2016-09-292-87/+86
|
* Allow a couple retries when unscheduling/rescheduling nodes in upgrade.Devan Goodwin2016-09-291-0/+12
| | | | | | | | This can fail with a transient "object has been modified" error asking you to re-try your changes on the latest version of the object. Allow up to three retries to see if we can get the change to take effect.
* Skip the docker role in early upgrade stages.Devan Goodwin2016-09-292-5/+6
| | | | | | | | This improves the situation further and prevents configuration changes from accidentally triggering docker restarts, before we've evacuated nodes. Now in two places, we skip the role entirely, instead of previous implementation which only skipped upgrading the installed version. (which did not catch config issues)
* Allow filtering nodes to upgrade by label.Devan Goodwin2016-09-297-13/+55
|
* Allow customizing node upgrade serial value.Devan Goodwin2016-09-291-1/+3
|
* Split upgrade for control plane/nodes.Devan Goodwin2016-09-299-103/+87
|
* Verify masters are upgraded before proceeding with node only upgrade.Devan Goodwin2016-09-281-3/+0
|
* Attempt to tease apart pre upgrade for masters/nodes.Devan Goodwin2016-09-288-305/+251
|
* Split upgrade entry points into control plane/node.Devan Goodwin2016-09-282-1/+49
|
* Reunite upgrade reconciliation gating with the play it gates on.Devan Goodwin2016-09-281-17/+18
|
* Drop atomic-enterprise as a valid deployment type in upgrade.Devan Goodwin2016-09-281-2/+2
|
* Stop guarding against pacemaker in upgrade, no longer necessary.Devan Goodwin2016-09-281-8/+0
|
* Support openshift_upgrade_dry_run=true for pre-upgrade checks only.Devan Goodwin2016-09-281-0/+7
|
* Fix OpenStack cloud providerLénaïc Huard2016-09-261-4/+4
|
* Merge pull request #2295 from dgoodwin/override-docker-upgradeScott Dodson2016-09-151-1/+1
|\ | | | | Allow overriding the Docker 1.10 requirement for upgrade.
| * Allow overriding the Docker 1.10 requirement for upgrade.Devan Goodwin2016-08-151-1/+1
| | | | | | | | Respect an explicit docker_version, and the use of docker_upgrade=False.
* | [upgrade] Create/configure service signer cert when missing.Andrew Butcher2016-09-143-1/+102
| |
* | Flush handlers before marking a node schedulable after upgrade.Devan Goodwin2016-09-091-0/+2
| | | | | | | | | | | | Handlers normally only trigger at the end of the play, but in this case we just set our node schedulable again resulting in it immediately getting taken down again.
* | Record schedulability of node prior to upgrade and re-set it to thatScott Dodson2016-09-021-1/+13
| | | | | | | | | | | | | | Previously we were setting schedulability to the state defined in the inventory without regard to whether or not it was manually made schedulable or unschedulable. The right thing seems to be to record the state prior to upgrade and set it back.
* | Fix ops/qps typoJordan Liggitt2016-09-022-3/+3
| |
* | Reload docker facts after upgrading dockerScott Dodson2016-08-301-0/+4
| |
* | Fix upgrade failure when master-config does not have pluginOrderOverride.Devan Goodwin2016-08-241-0/+1
| |
* | Merge pull request #2339 from dgoodwin/plugin-order-warningScott Dodson2016-08-231-0/+13
|\ \ | | | | | | Add warning at end of 3.3 upgrade if pluginOrderOverride is found.
| * | Add warning at end of 3.3 upgrade if pluginOrderOverride is found.Devan Goodwin2016-08-221-0/+13
| |/
* | Don't run node config upgrade hook if host is not a node.Devan Goodwin2016-08-231-1/+1
| |
* | Reconcile roles after master upgrade, but before nodes.Devan Goodwin2016-08-161-43/+46
|/ | | | | | | | | | Prevents the network egress bug causing node restart to fail during 3.3 upgrade. (even though a separate fix is incoming for this) Only catch is preventing the openshift_cli role, which requires docker, from triggering a potential upgrade, which we still don't want at this point. To avoid we use the same variable to protect docker installed version as we use in pre.yml.
* Improvements for Docker 1.10+ upgrade image nuking.Devan Goodwin2016-08-114-20/+55
| | | | | | | | | | | | | | | | In a parallel step prior to real upgrade tasks, clear out all unused Docker images on all hosts. This should be relatively safe to interrupt as no real upgrade steps have taken place. Once into actual upgrade, we again clear all images only this time with force, and after stopping and removing all containers. Both rmi commands use a new and hopefully less error prone command to do the removal, this should avoid missed orphans as we were hitting before. Added some logging around the current image count before and after this step, most of them are only printed if we're crossing the 1.10 boundary but one does not, just for additional information in your ansible log.
* Shutdown Docker before upgrading the rpm.Devan Goodwin2016-08-101-0/+4
| | | | | This avoids the automatic image migration in 1.10, which can take a very long time and potentially cause rpm db corruption.
* Merge pull request #2211 from dgoodwin/33-upgrade-playbookScott Dodson2016-08-0827-64/+124
|\ | | | | 1.3 / 3.3 Upgrades
| * Migrate ca.crt to ca-bundle.crtScott Dodson2016-08-081-0/+25
| |
| * Upgrade configs for protobuf support.Devan Goodwin2016-08-083-0/+66
| |
| * Introduce 1.3/3.3 upgrade path.Devan Goodwin2016-07-2525-64/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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+.
* | Add missing nuke_images.sh symlink.Devan Goodwin2016-07-221-0/+1
|/
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-11 08:45:49 +0000