-
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
[release-3.9] Re-apply tuned profile during upgrade #10266
[release-3.9] Re-apply tuned profile during upgrade #10266
Conversation
Can one of the admins verify this patch?
|
|
||
# Tuned profile are removed when removing tuned-profiles-atomic-openshift-node rpm | ||
# Need to be re apply | ||
- name: Re-enable tuned profiles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than doing this in a completely separate play add it as another post_task after line 59.
@@ -70,4 +70,11 @@ | |||
when: | |||
- __shared_resource_viewer_protected | default(false) | |||
|
|||
# Tuned profile are removed when removing tuned-profiles-atomic-openshift-node rpm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would be better as an additional task at
openshift_manage_node_is_master: true |
rather than a new play.
/ok-to-test |
ci/openshift-jenkins/gcp — Jenkins job failed. |
/test gcp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: franckgr, michaelgugino The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherrypick release-3.10 |
@michaelgugino: once the present PR merges, I will cherry-pick it on top of release-3.10 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherrypick release-3.11 |
@michaelgugino: once the present PR merges, I will cherry-pick it on top of release-3.11 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@michaelgugino: #10266 failed to apply on top of branch "release-3.10":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@michaelgugino: #10266 failed to apply on top of branch "release-3.11":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@franckgr would you be willing to cherrypick this to master, 3.11, and 3.10? This way, anyone that has already hit this and not noticed will be covered in the future. |
@franckgr: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
cherry-picks openshift#10266
cherry-picks openshift#10266
cherry-picks openshift#10266
During upgrade from 3.7 to 3.9 tuned-profiles-atomic-openshift-node rpm is removed and all tuned profiles.
Tuned role is not applied during an upgrade but during a fresh install. So tuned profiles are missing after an upgrade
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1626558