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

CNF-10170: bootkube.sh: Render kernel boot arguments for SNO #8007

Closed

Conversation

jlojosnegros
Copy link
Contributor

In an effort to speed up installation and avoid node reboots this command will run tuneD on a properly isolated environment and render a MachineConfig to apply the kernel boot args readed from /etc/tuned/bootcmdline

reverts: #7979

See:

In an effort to speed up installation and avoid node reboots this
command will run `tuneD` on a properly isolated environment and render a
MachineConfig to apply the kernel boot args readed from
`/etc/tuned/bootcmdline`

Signed-off-by: Jose Luis Ojosnegros Manchón <jojosneg@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 13, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 13, 2024

@jlojosnegros: This pull request references CNF-10170 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.16." or "openshift-4.16.", but it targets "openshift-4.15" instead.

In response to this:

In an effort to speed up installation and avoid node reboots this command will run tuneD on a properly isolated environment and render a MachineConfig to apply the kernel boot args readed from /etc/tuned/bootcmdline

reverts: #7979

See:

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@jlojosnegros
Copy link
Contributor Author

/hold
until openshift/cluster-node-tuning-operator#935 is merged

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 13, 2024
@jlojosnegros jlojosnegros marked this pull request as ready for review February 13, 2024 11:27
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 13, 2024
Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign rna-afk for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@vitus133
Copy link

/test okd-e2e-aws-ovn-upgrade

4 similar comments
@jlojosnegros
Copy link
Contributor Author

/test okd-e2e-aws-ovn-upgrade

@jlojosnegros
Copy link
Contributor Author

/test okd-e2e-aws-ovn-upgrade

@jlojosnegros
Copy link
Contributor Author

/test okd-e2e-aws-ovn-upgrade

@yanirq
Copy link

yanirq commented Feb 26, 2024

/test okd-e2e-aws-ovn-upgrade

@yanirq
Copy link

yanirq commented Feb 26, 2024

/retest

@jlojosnegros
Copy link
Contributor Author

/test okd-e2e-aws-ovn-upgrade

tmpfolder=$(mktemp -d)
echo ${tmpfolder}
podmancmd="bootkube_podman_run --attach=stderr --rm "
for folder in var/lib/tuned/profile-data etc/modprobe.d etc/sysconfig etc/kubernetes etc/sysctl.d etc/systemd run sys lib/modules var/lib/kubelet usr/lib/tuned etc/tuned; do
Copy link

Choose a reason for hiding this comment

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

@jmencak @jlojosnegros do we need to align with openshift/cluster-node-tuning-operator#970 in some manner ? or that change is not affecting the installer ?

Copy link

Choose a reason for hiding this comment

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

Good point. It looks like it needs an update. Also note that /var/lib/tuned/profiles-data was removed, not sure what var/lib/tuned/profile-data (singular) is used for. @jlojosnegros typo?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah it is a typo

@jlojosnegros
Copy link
Contributor Author

/test okd-e2e-aws-ovn-upgrade

Copy link
Contributor

openshift-ci bot commented Feb 28, 2024

@jlojosnegros: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-e2e-aws-ovn-upgrade ecfb02a link false /test okd-e2e-aws-ovn-upgrade

Full PR test history. Your PR dashboard.

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.

@vitus133
Copy link

vitus133 commented Mar 5, 2024

/close
continue this work at #8099

Copy link
Contributor

openshift-ci bot commented Mar 5, 2024

@vitus133: Closed this PR.

In response to this:

/close
continue this work at #8099

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-ci openshift-ci bot closed this Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants