| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Fix no proxy hostnames during upgrade.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This value not being set was causing missing hostnames in the sysconfig
files with NO_PROXY.
This is not the same way we set it during config playbooks, they use
vars definitions but this is too difficult in upgrade as there are too
many roles that might need it set.
|
|/
|
|
|
|
| |
Docker 1.10 is not widely available in RHEL / CentOS yet, lets remove
the restriction for users of master / origin. We can revert as soon as
it's available publically.
|
|\
| |
| | |
Bug 1338726 - never abort install if the latest version of docker is already installed
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds a separate playbook for Docker 1.10 upgrade that can be run
standalone on a pre-existing 3.2 cluster. The upgrade will take each
node out of rotation, and remove *all* containers and images on it, as
this is reportedly faster and more storage efficient than performing the
in place 1.10 upgrade.
This process is integrated into the 3.1 to 3.2 upgrade process.
Normal config playbooks now become 3.2 only, and require Docker 1.10.
Users of older environments will have to use an appropriate
openshift-ansible version.
Config playbooks no longer are in the business of upgrading or
downgrading docker.
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|\
| |
| | |
Task "Update router image to current version" failed, if router not in default namespace
|
| |
| |
| |
| |
| | |
default namespace
Also added hardcoded -n default to registry patch, since oc get has -n default, too.
|
|/
|
|
|
|
|
| |
Ansible is doing a full service stop and then start, which does not
allow systemd to keep the containerized services up and running.
Switching to this will cause the related services to come back within a
few seconds.
|
|\
| |
| | |
Don't pull cli image when we're not containerized
|
| | |
|
|\ \
| | |
| | | |
Fixes for openshift_docker_hosted_registry_insecure var.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes a failure on masters if you explicitly set
openshift_docker_hosted_registry_insecure=true. This is the default but
if you tried to set it an error would trigger as a relevant variable was
not passed in the master playbooks.
Fixes setting the variable to false being ignored.
master/node playbooks were referencing the docker fact, which was not
set at that point and thus we were always getting the default of true,
regardless what was in your inventory.
Stop passing registry insecure in via playbooks, we can access it when running
openshift_facts itself. Add a new default in openshift facts.
|
|\ \ \
| | | |
| | | | |
Containerized Upgrade Fixes
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Remove vars_files on play includes for upgrade playbooks.
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Add image-auditor role to ManageIQ SA
|
| | | |
|
| | | |
|
| |/
|/| |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
| |
If doing an upgrade with a 3.2.0.x version that was older than the
latest, the upgrade would actually use the latest in the systemd unit
files and thus the actual containers that get used. (despite pulling
down the correct version first)
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
containerized env
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
containerized systemd units
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fixing bugs 1322788 and 1323123
|
| |
| |
| |
| | |
and atomic-openshift-master-controllers
|
|\ \
| | |
| | | |
Pacemaker is unsupported for 3.2
|
| |/ |
|
|\ \
| |/
|/| |
We require docker 1.9 for the 3.2 upgrade
|
| | |
|
| |
| |
| |
| | |
and atomic-openshift-master-controllers
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
If the master or node aren't running we can't determine the correct version
that is currently installed.
|
| |
| |
| |
| |
| |
| |
| |
| | |
defined.
We already have a check in pre.yml to make sure openshift_image_tag is set to a
range that is allowed. This is an advanced setting and should be used to
override whatever is returned by the 'latest' image in a given registry.
|
|/ |
|
|\
| |
| | |
Bug 1315637 - The docker wasn't upgraded on node during upgrade
|