summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-cluster/upgrades/files
Commit message (Collapse)AuthorAgeFilesLines
* Force reconciliation of role for 3.6Simo Sorce2017-10-101-0/+37
| | | | | | | | This is needed because in 3.6 we cannot reconcile non-cluster roles in the bootstrap reconciliation code. In 3.7 this is taken care of in code. Signed-off-by: Simo Sorce <simo@redhat.com>
* Refactor docker upgrade playbooksRussell Teague2017-04-101-25/+0
| | | | | The playbooks were crossing byo/common boundaries for task includes. This moves all 'common' files/tasks into the 'common' folder.
* Remove unused fileRodolfo Carvalho2017-01-091-12/+0
| | | | | All references to it were removed in b89c835e3235f2628b37de15713c311d1b5a4bad
* Remove unused fileRodolfo Carvalho2017-01-091-193/+0
| | | | | All references to it were removed in 739ad9de2a11bb8c67d77641a86cfd39e4594542
* Improvements for Docker 1.10+ upgrade image nuking.Devan Goodwin2016-08-111-3/+5
| | | | | | | | | | | | | | | | 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.
* Merge branch 'aoi-32-up' into upgrade33Devan Goodwin2016-07-081-1/+1
|\
| * Fix dnf variant of rpm_versions.shScott Dodson2016-07-051-1/+1
| |
* | Merge branch 'master' into upgrade33Devan Goodwin2016-07-042-11/+15
|\ \ | |/
| * Switch to repoquery, enable plugins for satellite supportScott Dodson2016-06-291-3/+7
| |
* | Refactor 3.2 upgrade to avoid killing nodes without evac.Devan Goodwin2016-06-231-0/+23
| | | | | | | | | | We now handle the two pieces of upgrade that require a node evac in the same play. (docker, and node itself)
* | Always populate openshift_image_tag and openshift_pkg_version.Devan Goodwin2016-06-151-22/+0
|/ | | | | Allows the use of arbitrary tags, precise control over containers and rpms, and likely mixed environments.
* Conditionally bind mount /usr/bin/docker-current when it is present (#1941)Scott Dodson2016-05-241-1/+1
| | | | | | | | | | * Conditionally bind mount /usr/bin/docker-current when it is present * fix upgrade * add atomic-openshift-node-dep files to uninstall playbook * Fix variable expansion
* Fetching the current version a little more carefullyBrenton Leanhardt2016-04-121-5/+5
| | | | | | | | Previously we were trying to use the running container to get the current version. There are cases in which the Master or Node may not be running during upgrade. It's actually safer to just run the container to fetch the version that would be launch if the container were running. Then we pull the image to see what the latest image contains.
* First pass at systemd unit refactorBrenton Leanhardt2016-03-291-51/+0
|
* Docker stderr can break this script if ansible executes it remotelyBrenton Leanhardt2016-03-141-2/+2
|
* Bug 1315563 - Upgrade failed to containerized install OSE 3.1 on RHELBrenton Leanhardt2016-03-091-1/+1
| | | | | | Previously I was greping for 'ose' in the systemd units. That was only working on my machine because my Nodes were also Masters. It's safer to grep for openshift3 since that would be present for Masters or Nodes.
* Bug 1315563 - stdout IO redirection wasn't working as expected over SSH ↵Brenton Leanhardt2016-03-081-3/+3
| | | | | | connections Bug 1315563 - Upgrade failed to containerized install OSE 3.1 on RHEL
* Correctly set the image tag for containerized installs (and upgrades)Brenton Leanhardt2016-03-032-20/+3
|
* First past at the upgrade processBrenton Leanhardt2016-03-034-9/+98
|
* Fix checking for update package availabilityNikolai Prokoschenko2016-01-261-2/+2
| | | | | Currently, if `yum list available` returns two versions, for whatever reason, no sorting is imposed. Therefore it's possible that an upgraded package version is available but is not being detected. This patch sorts the version number list so that most recent version is always picked first.
* Clean up versions.shScott Dodson2015-12-161-3/+2
|
* Merge pull request #986 from sdodson/preflightBrenton Leanhardt2015-12-081-7/+10
|\ | | | | Clarify the preflight port check output
| * Clarify the preflight port check outputScott Dodson2015-11-301-7/+10
| |
* | Add -q flag to remove unwantend output (such as mirror and cache information)Urs Breu2015-11-261-2/+2
|/ | | | This prevents ansible failures when trying to set version facts
* pre-upgrade-check: differentiates between port and targetPort in outputSteve Milner2015-11-131-7/+9
|
* Refactor upgrade playbook(s)Jason DeTiberus2015-11-102-0/+198
- Split playbooks into two, one for 3.0 minor upgrades and one for 3.0 to 3.1 upgrades - Move upgrade playbooks to common/openshift/cluster/upgrades from adhoc - Added a byo wrapper playbooks to set the groups based on the byo conventions, other providers will need similar playbooks added eventually - installer wrapper updates for refactored upgrade playbooks - call new 3.0 to 3.1 upgrade playbook - various fixes for edge cases I hit with a really old config laying around. - fix output of host facts to show connect_to value.