| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
object' has no attribute 'stdout'"
|
| |
|
| |
|
|
|