summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-cluster/upgrades/v3_1_to_v3_2/upgrade.yml
Commit message (Collapse)AuthorAgeFilesLines
* The openshift_docker role must set the version facts for containerized installsBrenton Leanhardt2016-04-141-3/+12
| | | | | | QE found that for fresh installs we were basing the docker version facts of the images that could be pulled prior to configuring /etc/sysconfig/docker. This is an edge case but something we need to fix.
* Bug 1324728 - Ansible should not downgrade docker when installing 3.2 ↵Brenton Leanhardt2016-04-121-0/+14
| | | | containerized env
* Installs and upgrades from authenticated registries are not supported for nowBrenton Leanhardt2016-04-121-31/+0
|
* Containerized installs on RHEL were downgrading docker unnecessarilyBrenton Leanhardt2016-04-121-12/+14
|
* Bug 1322788 - The IMAGE_VERSION wasn't added to atomic-openshift-master-api ↵Brenton Leanhardt2016-04-011-1/+1
| | | | and atomic-openshift-master-controllers
* Bug 1322338 - The upgrade should keep the option insecure-registry=172.30.0.0/16Brenton Leanhardt2016-03-301-0/+2
|
* Use openshift.master.ha instead of duplicating the logicBrenton Leanhardt2016-03-291-3/+0
|
* Workaround for authenticated registriesBrenton Leanhardt2016-03-291-0/+29
| | | | | | | | | | Currently there's no good way to install from a registry that requires authentication. This applies both to RPM and containerized installs: https://bugzilla.redhat.com/show_bug.cgi?id=1316341 The workaround is to 'docker login' as root and then have ansible pull the images to the image cache.
* First pass at systemd unit refactorBrenton Leanhardt2016-03-291-2/+10
|
* Bug 1315564 - upgrade to ose3.2 failed on Atomic HostsBrenton Leanhardt2016-03-091-2/+11
|
* Support openshift_image_tagBrenton Leanhardt2016-03-071-1/+1
| | | | | | | | | | | | | This is the containerized openshift_pkg_version equivalent. Originally I was hoping to reuse openshift_pkg_version for containerized installs but the fact that it's very coupled to yum made that pretty ugly. However, I did opt to rely on the previously existing 'openshift_version' variable. Containerized and RPM installs can both use that variable and it will be set appropriately if either openshift_pkg_version or openshift_image_tag are set. I suspect someday containerized installs will be the only option and I didn't can to have thinkgs like openshift_pkg_version and openshift_image_tag in the playbooks anymore the necessary.
* Adding verify_upgrade_version variable for upgrade debuggingBrenton Leanhardt2016-03-031-1/+5
|
* Correctly set the image tag for containerized installs (and upgrades)Brenton Leanhardt2016-03-031-5/+4
|
* First past at the upgrade processBrenton Leanhardt2016-03-031-0/+147