| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Wait for nodes to be ready before proceeding with upgrade.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Near the end of node upgrade, we now wait for the node to report Ready
before marking it schedulable again. This should help eliminate delays
when pods need to relocate as the next node in line is evacuated.
Happens near the end of the process, the only remaining task would be to
mark it schedulable again so easy for admins to detect and recover from.
|
|\ \
| | |
| | | |
Implement simple hooks pre/post master upgrade.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
Begin requiring Docker 1.12.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Building off the work done for Docker 1.10, we now require Docker 1.12
by default.
The upgrade process was already set to ensure you are running the latest
docker during upgrade, and the standalone docker upgrade playbook can
also be used if desired.
As before, you can override this Docker 1.12 requirement by setting a
docker_version=1.10.3 (or similar), and you can skip the default to
upgrade docker by setting docker_upgrade=False.
|
|\ \ \
| | | |
| | | | |
use etcdctl from the container when containerized=True
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| | | |
| | | |
| | | |
| | | | |
Closes #3070
|
|\ \ \ \
| | | | |
| | | | | |
Cleanup cluster upgrade
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
All references to it were removed in
b89c835e3235f2628b37de15713c311d1b5a4bad
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
All references to it were removed in
739ad9de2a11bb8c67d77641a86cfd39e4594542
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The script nuke_images.sh was introduced in
0c31d72be3bf32f848eedad9859a81ba858f8c8f and seems that the shell
argument $1 was never used (the only $1 in the script back then refers
to a field in a awk script).
There was a reference to $2 that was always undefined/empty.
The script was then simplified in
b89c835e3235f2628b37de15713c311d1b5a4bad, removing any reference to $1
and $2.
This commit cleans up the only call site to the shell script.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
etcd 3.x image is 'etcd' not 'etcd3'
|
| | | | | |
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes Bug 1408668
Fixes BZ1408668
|
| | | |
| | | |
| | | |
| | | | |
versions
|
|\ \ \ \
| | | | |
| | | | | |
Deprecate node 'evacuation' with 'drain'
|
| | |_|/
| |/| |
| | | |
| | | | |
* https://trello.com/c/TeaEB9fX/307-3-deprecate-node-evacuation
|
|\ \ \ \
| | | | |
| | | | | |
Add master config hook for 3.4 upgrade and fix facts ordering
|
| |/ / /
| | | |
| | | |
| | | | |
hook run.
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
* Added checks to make ci for yaml linting
* Modified y(a)ml files to pass lint checks
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Drop 3.2 upgrade playbooks.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Silence warnings when using some commands directly
|
| |/ / / |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
etcd_upgrade: Simplify package installation
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Scheduler upgrades
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- do not upgrade predicates if openshift_master_scheduler_predicates is
defined
- do not upgrade priorities if openshift_master_scheduler_priorities is
defined
- do not upgrade predicates/priorities unless they match known previous
default configs
- output WARNING to user if predictes/priorities are not updated during
install
|
| | | | |
|
|/ / / |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In 3.3 one of our services lays down a systemd drop-in for configuring
Docker networking to use lbr0. In 3.4, this has been changed but the
file must be cleaned up manually by us.
However, after removing the file docker requires a restart. This had big
implications particularly in containerized environments where upgrade is
a very fragile series of upgrading and service restarts.
To avoid double docker restarts, and thus double service restarts in
containerized environments, this change does the following:
- Skip restart during docker upgrade, if it is required. We will restart
on our own later.
- Skip containerized service restarts when we upgrade the services
themselves.
- Clean shutdown of all containerized services.
- Restart Docker. (always, previously this only happened if it needed an
upgrade)
- Ensure all containerized services are restarted.
- Restart rpm node services. (always)
- Mark node schedulable again.
At the end of this process, docker0 should be back on the system.
|
|/ / |
|
| |
| |
| |
| | |
Fixes Bug 1395945
|