| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
This was missed in the standalone upgrade control plane playbook.
However it also looks to be out of order, we should restart before
reconciling and upgrading nodes. As such moved the restart directly into
the control plane upgrade common code, and placed it before
reconciliation.
|
| |\
| |
| | |
add regionendpoint parameter for registry s3
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Do not error on node labels set too non-string values.
|
| | | |
| | |
| | |
| | | |
see #2602
|
| |\ \ \
| |/ /
|/| | |
[logging] Use inventory variables rather than facts
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Resume restarting node after upgrading node rpms.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Error in commit 245fef16573757b6e691c448075d8564f5d569f4.
As it turns out this is the only place a rpm based node can be restarted
in upgrade. Restoring the restart but making it conditional to avoid the
two issues reported with out of sync node restarts.
|
| |\ \ \
| | | |
| | | | |
upgrade: Don't check avail docker version if not already installed.
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
update handling of use_dnsmasq
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Fix standalone docker upgrade playbook skipping nodes.
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
Transition to being able to specify nodes to upgrade caused standalone
nodes to get skipped in this playbook.
|
| |\ \ \ \
| | | | |
| | | | | |
Fix missing play assignment in a-o-i callback plugin
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If a task fails in the quick installer it calls the
`v2_runner_on_failed` method in the callback plugin. I missed setting
`self._play` in the first iteration of the callback plugin, which it
turns out is critical for the `on_failed` method to work. This fixes
that by adding back in the assignment in the `play_start` method.
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
nfs: Handle seboolean aliases not just in Fedora
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I'm testing with a bleeding edge RHEL Atomic Host, and it looks
like we pulled in a new version of selinux-policy that has
`virt_sandbox_use_nfs` aliased to `virt_use_nfs`.
In https://github.com/openshift/openshift-ansible/pull/2356
Adam changed this to check for Fedora. This changes things
to drop the distribution check, and instead parse the `getsebool`
output to determine whether or not the boolean is an alias,
and should hence work on all distributions/versions.
|
| |\ \ \ \
| | | | |
| | | | | |
Stop restarting node after upgrading master rpms.
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This looks to be causing a customer issue where some HA upgrades fail,
due to a missing EgressNetworkPolicy API. We update master rpms, we
don't restart services yet, but then restart node service which tries to
talk to an API that does not yet exist. (pending restart)
Restarting node here is very out of place and appears to not be
required.
|
| |\ \ \ \
| |_|_|/
|/| | | |
Fix upgrade mappings in quick installer
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Update to use the correct playbook for 3.2 to 3.3 upgrades
and some error handling for unsupported upgrades.
Fixes Bug 1381411
|
| |/ / |
|
| |\ \
| |/
|/| |
set defaults for debug_level in template and task
|
| | |\
| |/
|/|
| | |
variable_with_no_default_2576
|
| |\ \
| | |
| | | |
Fix config and namespace for registry volume detection
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Set HTTPS_PROXY in example builddefaults_json
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
Check that OpenStack hostnames are resolvable
|
| | | | |
| | | |
| | | |
| | | | |
If they’re not, then use IP instead
|
| |\ \ \ \
| | | | |
| | | | | |
Retry starting master and node services once
|
| | | | | | |
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Retry failed master startup once
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Master startup can fail when ec2 transparently reallocates the block
storage, causing etcd writes to temporarily fail. Retry failures blindly
just
once to allow time for this transient condition to to resolve and for
systemd
to restart the master (which will eventually succeed).
https://github.com/coreos/etcd/issues/3864
https://github.com/openshift/origin/issues/6065
https://github.com/openshift/origin/issues/6447
|
| | |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
Nuage Monitor: Enumerate over etcd servers
|
| | | | | |
|
| |\ \ \ \
| |_|_|/
|/| | | |
[logging] Fix openshift_hosted_logging_fluentd_nodeselector
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
[a-o-i] -v disables quiet ansible config.
|
| |/ / / |
|