diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-10-03 16:53:57 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-03 16:53:57 -0700 |
| commit | 859d38301d90166ce4f348b76551409658991d9d (patch) | |
| tree | 8cc959970c7106720e2a77efd60faa3fb3151137 /playbooks/common/openshift-cluster/upgrades/v3_5 | |
| parent | cf99c367d6f6a3c55969b4e6c77c1fa691cd5852 (diff) | |
| parent | 3f931ea57f510e6d081866c50c6910544d92285a (diff) | |
| download | openshift-859d38301d90166ce4f348b76551409658991d9d.tar.gz openshift-859d38301d90166ce4f348b76551409658991d9d.tar.bz2 openshift-859d38301d90166ce4f348b76551409658991d9d.tar.xz openshift-859d38301d90166ce4f348b76551409658991d9d.zip | |
Merge pull request #5632 from mgugino-upstream-stage/limit-version-upgrade-masters
Automatic merge from submit-queue.
Limit base-package install during master upgrades
Currently, openshift_version installs RPM packages
on all nodes and masters to aid in determining and
setting the proper version across the cluster.
This commit limits the host groups to only
masters during upgrade_control_plane plays.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1495107
Diffstat (limited to 'playbooks/common/openshift-cluster/upgrades/v3_5')
| -rw-r--r-- | playbooks/common/openshift-cluster/upgrades/v3_5/upgrade_control_plane.yml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/playbooks/common/openshift-cluster/upgrades/v3_5/upgrade_control_plane.yml b/playbooks/common/openshift-cluster/upgrades/v3_5/upgrade_control_plane.yml index 6cdea7b84..e9cec9220 100644 --- a/playbooks/common/openshift-cluster/upgrades/v3_5/upgrade_control_plane.yml +++ b/playbooks/common/openshift-cluster/upgrades/v3_5/upgrade_control_plane.yml @@ -72,6 +72,7 @@ # defined, and overriding the normal behavior of protecting the installed version openshift_release: "{{ openshift_upgrade_target }}" openshift_protect_installed_version: False + openshift_install_base_package_group: "oo_masters_to_config" # We skip the docker role at this point in upgrade to prevent # unintended package, container, or config upgrades which trigger |