| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
The playbooks were crossing byo/common boundaries for task includes.
This moves all 'common' files/tasks into the 'common' folder.
|
|
|
|
|
| |
All references to it were removed in
b89c835e3235f2628b37de15713c311d1b5a4bad
|
|
|
|
|
| |
All references to it were removed in
739ad9de2a11bb8c67d77641a86cfd39e4594542
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| | |
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
We now handle the two pieces of upgrade that require a node evac in the
same play. (docker, and node itself)
|
|/
|
|
|
| |
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
* fix upgrade
* add atomic-openshift-node-dep files to uninstall playbook
* Fix variable expansion
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
connections
Bug 1315563 - Upgrade failed to containerized install OSE 3.1 on RHEL
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|\
| |
| | |
Clarify the preflight port check output
|
| | |
|
|/
|
|
| |
This prevents ansible failures when trying to set version facts
|
| |
|
|
- 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.
|