| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, double upgrade process (3.7 -> 3.9)
for control plane attempts to run openshift_version
role twice to set the appropriate values for
upgrading each major version, 3.8 and 3.9.
This commit instructs openshift_version to
only inquire about the proper settings for 3.9,
and hard-sets the appropriate values for 3.8.
This allows a simplification of the
openshift_version role, allowing for easier
debugging.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1542368
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
[1540537] Add base package installation to upgrade playbooks
Hosts will need python ipaddress module installed if it was not
installed during initial installation.
Bug 1540537
https://bugzilla.redhat.com/show_bug.cgi?id=1540537
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Hosts will need python ipaddress module installed if it was not
installed during initial installation.
Bug 1540537
https://bugzilla.redhat.com/show_bug.cgi?id=1540537
|
| |/
|
|
|
|
|
| |
* 'rolling_restart_mode' should be 'services', not 'service'
* use 'state: restarted' to properly restart services
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
| |\
| |
| | |
Fix version handling in 3.8/3.9 control plane upgrades
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
Upgrade playbook improvements
Two changes in this PR:
* Avoid duplication in upgrade.yml - it now would simply run upgrade_control_plane and upgrade_nodes playbooks
* Restart controllers instead of start/stop if restart mode is 'services'
* For 'system' restart mode controllers are disabled before master upgrade and re-enabled after upgrades are finished
|
| | |
| |
| |
| |
| |
| | |
mode is system
This removes a start/stop after control plane upgrade
|
| |/
|
|
|
|
|
|
|
|
| |
Version 3.8 is an intermediate step when upgrading to 3.9 and
openshift_pkg_version may be set in the inventory for 3.9. This will
ensure there is not a conflict between the intermediate step and the
final version requested.
Bug 1540108
https://bugzilla.redhat.com/show_bug.cgi?id=1540108
|
| |
|
|
|
|
|
|
|
|
|
| |
Due to complexities upgrading two versions
at the same time, openshift_image_tag was being
set incorrectly during control_plane upgrades.
This commit ensures that openshift_image_tag
is set correctly during this process.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1536839
|
| |
|
|
|
|
|
|
| |
The `assetConfig` is no longer used now that the console is split into
its own pod.
- Remove `assetConfig` on upgrades to 3.9
- Stop writing logging and metrics URLs to assetConfig for 3.9
|
| |
|
|
|
|
|
|
|
|
| |
Master version is unprotected during all upgrades.
During node-only upgrades, master version should
remain protected to ensure correct image tag is
set for node upgrades.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1536839
|
| |
|
|
|
|
|
|
| |
Currently, users have no way to run preqrequisites.yml
on just newly added nodes during scaleup.
This commit ensures only the new nodes are changed during
scaleup as well as ensure prerequisites are run.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This commit limits common init code to exclude
oo_nodes_to_config during upgrade_control_plane runs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit refactors some upgrade code paths.
Touched areas are:
1) Reduces usage of 'oo_all_hosts' in various places,
especially when running upgrade_control_plane.
2) Reuses common code across the various upgrade*
playbooks.
3) Moves docker upgrade checks into container_runtime_role.
4) Combines smaller playbooks and plays to reduce file sprawl.
|
| |
|
|
|
| |
Bring openshift_facts into scope for plays that utilize
openshift_service_type as it is defined there.
|
| | |
|
| |
|
