-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport excluders to 1.4 #4367
Closed
ingvagabund
wants to merge
345
commits into
openshift:master
from
ingvagabund:backport-excluders-to-1.4
Closed
Backport excluders to 1.4 #4367
ingvagabund
wants to merge
345
commits into
openshift:master
from
ingvagabund:backport-excluders-to-1.4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Backport-3.4] scheduler upgrades
[3.4] Remove Hostname from 1.1 and 1.2 predicates
We did this for install but not upgrade, leading to situations where the service restarts after upgrade could take much longer than expected as docker pulls down the new image. Now the images are present when we restart services and should allow them to come back online much more quickly, equivalent to rpm service restarts.
Pre-pull master/node/ovs images during upgrade.
[release-1.4] etcd_upgrade: Simplify package installation
Backport 1.4 - Include etcd upgrade in normal upgrade playbooks
Release 1.4 backports
Backport 1.4 - modify_yaml error on non existant key
This reverts commit ab14b72. If docker upgrade is required, this was occurring at a time when docker was down as we'll soon be restarting it for all services to come back. Will sort out for 3.5.
Revert "Pre-pull master/node/ovs images during upgrade."
Merged by openshift-bot
Created by command: /usr/bin/tito tag --accept-auto-changelog --use-version=v3.4.1.26
Created by command: /usr/bin/tito tag --accept-auto-changelog --use-version=3.4.1.27
Bug 1454370
[3.4] Fix auditConfig for non-HA environments
[3.4] Set metrics url even if metrics_deploy is false
Created by command: /usr/bin/tito tag --accept-auto-changelog --use-version=3.4.1.28
…upgrade Prepending v to registry-console version
Created by command: /usr/bin/tito tag --accept-auto-changelog --use-version=3.4.1.29
Created by command: /usr/bin/tito tag --accept-auto-changelog --use-version=3.4.1.30
…er-14 [JMAN4-161] Add templates and pv example for cloudforms jboss middlew…
Created by command: /usr/bin/tito tag
…er,registry}=false
[3.4] AMP 2.0
…try-cert-redeploy [1.4] Skip router/registry cert redeploy when openshift_hosted_manage_{router,registry}=false
Add missing AMP 2.0 files
Created by command: /usr/bin/tito tag
Created by command: /usr/bin/tito tag --accept-auto-changelog
Two tasks for initializing group names for the byo playbooks was located in the common folder in the std_include.yml file. Byo dependencies should not be in the common folder. The two tasks have been removed from common/openshift-cluster/std_include.yml to a new file byo/openshift-cluster/initialize_groups.yml. All references where these tasks were included from either std_include.yml or other various files have been updated to use the byo initialize_groups.yml. The methodology implemented follows the pattern of having groups set up in byo then calling out to playbooks in common, which are common to all deployments.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on 1.5 backport #4266. Given excluders are new in 3.4, it is picked from the latest master. Thus, a lot of PRs from 1.5 are already integrated.
This will require a lot of testing: