| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Playbook Consolidation - openshift-master
|
| | |
|
|/
|
|
| |
Cleaning out reference to etcd_runtime in openshift facts.
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, having openshift_node and openshift_node_upgrade
as two distinct roles has created a duplication across
handlers, templates, and some tasks.
This commit combines the roles to reduce duplication
and bugs encountered by not putting code in both places.
|
|\
| |
| | |
Playbook Consolidation - Initialization
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Add role to configure project request template
The OpenShift master role already supports changing the master
configuration to refer to a project template, but there's no way to
manage that template directly. This role adds the necessary code to
generate a default template and to apply customizations using the
"yedit" module.
We need to configure custom services and endpoints in every project. The project request template enables us to do that automatically in every project and we'd like to manage the template using Ansible.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The OpenShift master role already supports changing the master
configuration to refer to a project template, but there's no way to
manage that template directly. This role adds the necessary code to
generate a default template and to apply customizations using the
"yedit" module.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Automatic merge from submit-queue.
Combine master upgrade play with role
Currently, there are plays importing tasks directly from
openshift_master role. This has caused numerous bugs
and code duplicaiton in the past.
This commit combines the upgrade into openshift_master role
utilizing include_role syntax.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently, there are plays importing tasks directly from
openshift_master role. This has caused numerous bugs
and code duplicaiton in the past.
This commit combines the upgrade into openshift_master role
utilizing include_role syntax.
|
|\ \ \ \
| |_|_|/
|/| | | |
Removed old version code
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit removes any references to versions < 1.5/3.5
We assume the version is always greater than or equal to 1.5/3.5.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Automatic merge from submit-queue.
Remove upgrade playbooks for 3.3 through 3.5
Release branches should be used for older upgrades.
|
| | |/ /
| |/| | |
|
| |/ /
|/| | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, we check that upgrade target is less than 3.8,
but this will break for minor upgrades.
This commit set's a fact early in the upgrade process to
deterime what the currently installed version on the
first master is.
This fact is used to determine if our currently installed
version is less than 3.7.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1508301
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, this task is executed based on openshift_version.
openshift_version is based on the upgrade target, thus not
the currently install versions.
This commit ensures that the task executes as intended.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1508301
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, upgrade_control_plane calls tasks meant for
master on etcd group.
This commit corrects the groupname.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1508734
|
|\ \
| | |
| | |
| | |
| | | |
This previously passed all CI tests, merge queue broke last night.
Merging, this is a blocker bug.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, in 1.5, 3.6, 1.7 upgrade-all plays, control
plane upgrades are not called correctly.
This commit ensures the master config hook is appropriately
applied during these upgrades to match the steps in
control plane only upgrades.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1486054
|
|\ \ \
| |/ /
|/| | |
Remove base package install
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, base atomic-openshift package is
installed for versioning.
This doesn't appear to be necessary.
This commit removes this step.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1504196
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Automatic merge from submit-queue.
Enable oreg_auth credential replace during upgrades
Currently, upgrades run a docker image pull prior to
upgrading masters and nodes for containerized installs.
If using a secure registry, and a user wishes to upgrade
their credentials due to expiry, the image pull will fail.
This commit ensures docker login credentials are updated
during upgrades, if necessary.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1503995
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently, upgrades run a docker image pull prior to
upgrading masters and nodes for containerized installs.
If using a secure registry, and a user wishes to upgrade
their credentials due to expiry, the image pull will fail.
This commit ensures docker login credentials are updated
during upgrades, if necessary.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1503995
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
ingvagabund/strip-dash-when-comparing-versions-python3
strip dash when comparing version with Python3
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Automatic merge from submit-queue.
Ensure upgrades apply latest journald settings
Currently, existing clusters might not have journald
configurations applied. This may result in a rate-
limiting of important log messages on openshift-masters.
This commit ensures that journald settings are applied
during the upgrade process openshif-masters.
Fixes: https://github.com/openshift/openshift-ansible/issues/5642
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently, existing clusters might not have journald
configurations applied. This may result in a rate-
limiting of important log messages on openshift-masters.
This commit ensures that journald settings are applied
during the upgrade process openshif-masters.
Fixes: https://github.com/openshift/openshift-ansible/issues/5642
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Correct version gates on policy reconciliation and add retries
|
| | | | | | |
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
Handles spurious failures and does not get mad if it just cannot do it.
Signed-off-by: Simo Sorce <simo@redhat.com>
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Check if the master service is non-ha or not
|
| | |_|/
| |/| | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Fixes 1504515
https://bugzilla.redhat.com/show_bug.cgi?id=1504515
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Set servingInfo.clientCA to ca.crt during upgrade.
https://bugzilla.redhat.com/show_bug.cgi?id=1501795
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Remove unneeded master config updates during upgrades
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, upgrade_control_plane.yml will add any
missing sections to the openshift master's config.
These additions are only needed once. Users who
perform multiple upgrades to their clusters over
time do not need to have these variables re-inserted.
Currently, re-inserting these variables can cause
unwanted local changes.
This commit ensures that the variables are only
inserted into openshift master's config once.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1486054
|
|\ \
| |/
|/| |
Restart all controllers to force reconfiguration during upgrade
|
| | |
|
| | |
|
| |
| |
| |
| | |
https://bugzilla.redhat.com/show_bug.cgi?id=1484324
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
1499254 Ensure host was reached for proper conditional validation
If a host was unreachable during module setup, facts will not be
initialized properly and will result in later failures when stepping
through host groups. Verification that 'openshift' is defined will skip
any hosts which were previously unreachable and did not have facts
initialized.
Fixes 1499254
https://bugzilla.redhat.com/show_bug.cgi?id=1499254
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a host was unreachable during module setup, facts will not be
initialized properly and will result in later failures when stepping
through host groups. Verification that 'openshift' is defined will skip
any hosts which were previously unreachable and did not have facts
initialized.
Fixes 1499254
https://bugzilla.redhat.com/show_bug.cgi?id=1499254
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, debug_level is documented as a way to change
the debug output level for both masters and nodes.
debug_level does not currently have any effect.
This commit removes debug_level from openshift_facts
and properly sets openshift_master_debug_level and
openshift_node_debug_level to the value of debug_level
specified in the inventory.
This commit also reorganizes some set_fact tasks
needed during master upgrades to put all work-around
set-facts for undefined variables in one place, allowing
for easier cleanup in the future. This includes an
entry for openshift_master_debug_level.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1500164
|
| | |
|
|/
|
|
|
|
|
|
| |
This is needed because in 3.6 we cannot reconcile non-cluster roles in the
bootstrap reconciliation code.
In 3.7 this is taken care of in code.
Signed-off-by: Simo Sorce <simo@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change sets the controllerConfig.election.lockName to
openshift-master-controllers on a 3.7 upgrade.
This is the default in a new 3.7 cluster. Important excerpt from
the docs inside the origin codebase (slightly modified):
There are two modes for lease operation - a legacy mode that
directly connects to etcd, and the preferred mode which coordinates
on a configmap or endpoint in the kube-system namespace. Because
legacy mode and the new mode do not coordinate on the same key, an
upgrade must stop all controllers before changing the configuration
and starting controllers with the new config.
Signed-off-by: Monis Khan <mkhan@redhat.com>
|