| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
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.
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Allow disabling authorization migration check
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Add execution times to checkpoint status
This PR adds execution times to the checkpoint status report at the end of an installer playbook run.
- Checkpoint plays now use `all` host group to avoid using an undefined host group during the Initialization phase as well as maintaining the need to collect inventory vars for host group conditionals
- `run_once: true` is used to limit the execution to only one host
- `installer_phase_*` data is now stored as a dict so multiple data points can be stored for that phase
- Documentation updated
```
INSTALLER STATUS ***************************************************************
Initialization : Complete (0:02:14)
Health Check : Complete (0:01:10)
etcd Install : Complete (0:02:01)
Master Install : Complete (0:11:43)
Master Additional Install : Complete (0:00:54)
Node Install : Complete (0:14:11)
Hosted Install : Complete (0:03:28)
```
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
This also causes a failure if nfs block is not defined, because the condition is missing.
Anyway this shouldn't have been committed.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Temporarily set master servingInfo.clientCA as client-ca-bundle.crt during rolling CA redeployment.
This PR temporarily configures master `servingInfo.clientCA` as `client-ca-bundle.crt` during CA redeploy so that clients referencing the old OpenShift CA can continue to function until all cluster certificates have been replaced and `servingInfo.clientCA` is reset to `ca.crt`.
`client-ca-bundle.crt` is a new bundle created by the `openshift_ca` role which contains old and new OpenShift CA certificates.
https://bugzilla.redhat.com/show_bug.cgi?id=1509124
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1493276
|
| | |
| | |
| | |
| | | |
rolling CA redeployment.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Enable SC, ASB, TSB by default
It was decided that SC, ASB, and TSB should be installed by default.
This will not install the components on an upgrade from 3.6 to 3.7, that will require that you run the sc playbook on your own.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1508085
|
| | |
| | |
| | |
| | | |
This will not install the components on an upgrade.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Automatic merge from submit-queue.
openshift_hosted: Add docker-gc
Two new inventory variables have been created:
- ``openshift_crio_enable_docker_gc``: Enable docker_gc daemon set
- ``openshift_crio_docker_gc_node_selector``: Optional dictionary to use node
selector
When ``openshift_crio_enable_docker_gc`` and ``openshift_use_crio`` are both true
then ``docker_gc`` daemonset will be created along with adding a ``docker-gc``
sa.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two new inventory variables have been created:
- openshift_crio_enable_docker_gc: Enable docker_gc daemon set
- openshift_crio_docker_gc_node_selector: Optional dictionary to use node
selector
When openshift_crio_enable_docker_gc and openshift_use_crio are both true
then dockergc daemonset will be created along with adding a dockergc
sa.
Signed-off-by: Steve Milner <smilner@redhat.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Automatic merge from submit-queue.
Create default storageclass for cloudprovider openstack
With this patch, a default storageclass will be created on openstack cloudprovider after installation.
|
| | |
|
|\ \
| | |
| | | |
Force include_role to static for loading openshift_facts module
|
| | | |
|
|\ \ \
| | | |
| | | | |
1504593 Refactor health check playbooks
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Standardize play/tasks naming
- Move install checks to separate playbook with checkpointing
- Correct 'docker_storage' tags
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
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.
Add installer checkpoint for prometheus
|
| | |_|/
| |/| |
| | | |
| | | | |
Add checkpoint steps for full cluster install and individual entry point playbook.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Generate internal hostnames of no_proxy
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
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
|
|\ \ \
| | | |
| | | | |
Provisioning updates.
|