Skip to content
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

Merged

Conversation

franckgr
Copy link

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

@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 28, 2018
@papr-bot
Copy link

Can one of the admins verify this patch?
I understand the following commands:

  • bot, add author to whitelist
  • bot, test pull request
  • bot, test pull request once


# Tuned profile are removed when removing tuned-profiles-atomic-openshift-node rpm
# Need to be re apply
- name: Re-enable tuned profiles
Copy link
Member

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
Copy link
Member

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.

@sdodson
Copy link
Member

sdodson commented Sep 28, 2018

/ok-to-test

@openshift-ci-robot openshift-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Sep 28, 2018
@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 3, 2018
@franckgr franckgr changed the title [release-3.9] Re-apply tuned profile dunring upgrade [release-3.9] Re-apply tuned profile during upgrade Oct 15, 2018
@franckgr
Copy link
Author

ci/openshift-jenkins/gcp — Jenkins job failed.
Doesn't seems to be relevant to tuned modification

@michaelgugino
Copy link
Contributor

/test gcp

Copy link
Contributor

@michaelgugino michaelgugino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2018
@michaelgugino
Copy link
Contributor

/approve

@michaelgugino michaelgugino added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 15, 2018
@openshift-ci-robot
Copy link

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@michaelgugino
Copy link
Contributor

/cherrypick release-3.10

@openshift-cherrypick-robot

@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:

/cherrypick release-3.10

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
Copy link
Contributor

/cherrypick release-3.11

@openshift-cherrypick-robot

@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:

/cherrypick release-3.11

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.

@openshift-merge-robot openshift-merge-robot merged commit 89a65c0 into openshift:release-3.9 Oct 15, 2018
@openshift-cherrypick-robot

@michaelgugino: #10266 failed to apply on top of branch "release-3.10":

Applying: move tuned role from a separated play to a post task in upgrade_nodes.yml
Applying: move tuned role from post_control_plane.yml to an additional task in upgrade.yml
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	playbooks/common/openshift-cluster/upgrades/post_control_plane.yml
M	playbooks/openshift-master/private/upgrade.yml
Falling back to patching base and 3-way merge...
Auto-merging playbooks/openshift-master/private/upgrade.yml
CONFLICT (content): Merge conflict in playbooks/openshift-master/private/upgrade.yml
Auto-merging playbooks/common/openshift-cluster/upgrades/post_control_plane.yml
Patch failed at 0003 move tuned role from post_control_plane.yml to an additional task in upgrade.yml

In response to this:

/cherrypick release-3.10

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.

@openshift-cherrypick-robot

@michaelgugino: #10266 failed to apply on top of branch "release-3.11":

Applying: move tuned role from a separated play to a post task in upgrade_nodes.yml
Applying: move tuned role from post_control_plane.yml to an additional task in upgrade.yml
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	playbooks/common/openshift-cluster/upgrades/post_control_plane.yml
M	playbooks/openshift-master/private/upgrade.yml
Falling back to patching base and 3-way merge...
Auto-merging playbooks/openshift-master/private/upgrade.yml
CONFLICT (content): Merge conflict in playbooks/openshift-master/private/upgrade.yml
Auto-merging playbooks/common/openshift-cluster/upgrades/post_control_plane.yml
Patch failed at 0003 move tuned role from post_control_plane.yml to an additional task in upgrade.yml

In response to this:

/cherrypick release-3.11

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
Copy link
Contributor

@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.

@openshift-ci-robot
Copy link

@franckgr: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/openshift-jenkins/gcp ae57c0c link /test gcp

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.

mtnbikenc added a commit to mtnbikenc/openshift-ansible that referenced this pull request Mar 29, 2019
mtnbikenc added a commit to mtnbikenc/openshift-ansible that referenced this pull request Mar 29, 2019
mtnbikenc added a commit to mtnbikenc/openshift-ansible that referenced this pull request Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants