| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Prevents playbooks from accidentally restarting the master service.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
The Ansible package module will call the correct package manager for the
underlying OS.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This avoids the automatic image migration in 1.10, which can take a very
long time and potentially cause rpm db corruption.
|
| | |
|
| | |
|
|
|
We now handle the two pieces of upgrade that require a node evac in the
same play. (docker, and node itself)
|
