Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@haircommander
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

If InfraCtrCPUSet is configured, then there is an expectation that all commands land on certain CPUs. However, this isn't always the case. Thus, we need a way of spawning commands given a list of CPUs.

To do this, update cmdrunner to be a singleton object that stores an optional command and args to prepend to commands. Then use this singleton anytime exec.Command would be called.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Add functionality to use taskset to spawn new commands cri-o runs. Now, if InfraCtrCPUSet is called, all newly spawned commands will be placed in the InfraCtrCPUSet (as it's expected to be set to the reserved CPU set that system commands should run on).

saschagrunert and others added 30 commits August 27, 2021 13:16
The quantile has to be added manually since a couple of prometheus
client releases and we missed that. Adding an integration test to ensure
that the quantile exist in the future.

Signed-off-by: Sascha Grunert <[email protected]>
…pick-5258-to-release-1.22

[release-1.22] Fix missing quantile in `latency_microseconds_total` metrics
if we fail to move conmon to a cgroup, we still need to call Wait() on the process, or else we will leak a child

Signed-off-by: Peter Hunt <[email protected]>
or else we will leak a pid

Signed-off-by: Peter Hunt <[email protected]>
…pick-5283-to-release-1.22

[release-1.22] oci: call wait on conmon if cgroup move fails
This reduces the noise on systems not having Intel RDT enabled.

Signed-off-by: Sascha Grunert <[email protected]>
…pick-5293-to-release-1.22

[release-1.22] Do not log on startup if Intel RDT is not supported
If we haven't signaled on the stop pipe, then conmon will be sitting waiting to be told to start
Instead, we need to kill the process.

Signed-off-by: Peter Hunt <[email protected]>
…pick-5306-to-release-1.22

[release-1.22] server: do not wait forever on conmon cgroup move fail
…pick-5313-to-release-1.22

[release-1.22] server: set spec when dropping infra
to remain consistent with other times it's specified

Signed-off-by: Peter Hunt <[email protected]>
…pick-5244-to-release-1.22

[release-1.22] server: fix some hostNet handling in container creation
RHEL/CentOS 7's container-selinux package replaces container_file_t with svirt_sandbox_file_t
under the hood. This causes the annotation to not work correctly.

Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
If a container or pod specifies the SELinux type `spc_t`, then we skip
the volume relabel.

Signed-off-by: Sascha Grunert <[email protected]>
[1.22] server: conditionally relabel volumes given annotation
Fix https://bugzilla.redhat.com/show_bug.cgi?id=2012838

Merge in the storage_option from drop-in crio.conf to the storage.conf, do not override the configs from storage.conf.
The override leads to configuration of containerruntimeconfig not working.

Signed-off-by: Qi Wang <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
haircommander and others added 16 commits November 11, 2021 18:21
…pick-5445-to-release-1.22

[release-1.22] release-notes: update to main
…pick-5423-to-release-1.22

[release-1.22] Bug 2020729: fix override storage options from storage.conf
[1.22] oci: fix a couple of deadlocks in container stop code
[1.22] workloads: fix if resources are empty
…pick-5336-to-release-1.22

[release-1.22] server: close namespaces on sandbox stop
Even if we kill the process, we still need to wait for it, or else we'll reap a zombie.

Signed-off-by: Peter Hunt <[email protected]>
…pick-5500-to-release-1.22

[release-1.22] oci: always reap conmon zombies
Signed-off-by: Peter Hunt <[email protected]>
@openshift-ci openshift-ci bot added kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: no Indicates the PR's author has not DCO signed all their commits. release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Jan 17, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2022

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

Details

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot requested review from fidencio and sameo January 17, 2022 18:06
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 17, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2022

@haircommander: PR needs rebase.

Details

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 added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 17, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2022

@haircommander: The following tests 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/openshift-jenkins/e2e_features_fedora 51b9a7e link true /test e2e_features_fedora
ci/openshift-jenkins/integration_crun 51b9a7e link true /test integration_crun
ci/openshift-jenkins/integration_fedora 51b9a7e link true /test integration_fedora
ci/openshift-jenkins/e2e_rhel 51b9a7e link true /test e2e_rhel
ci/openshift-jenkins/e2e_features_rhel 51b9a7e link true /test e2e_features_rhel
ci/openshift-jenkins/critest_fedora 51b9a7e link true /test critest_fedora
ci/openshift-jenkins/integration_rhel 51b9a7e link true /test integration_rhel
ci/openshift-jenkins/integration_crun_cgroupv2 51b9a7e link false /test integration_cgroupv2
ci/openshift-jenkins/e2e_crun_cgroupv2 51b9a7e link false /test e2e_cgroupv2
ci/openshift-jenkins/e2e_fedora 51b9a7e link true /test e2e_fedora
ci/openshift-jenkins/e2e_crun 51b9a7e link true /test e2e_crun
ci/openshift-jenkins/critest_rhel 51b9a7e link true /test critest_rhel

Full PR test history. Your PR dashboard.

Details

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.

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. dco-signoff: no Indicates the PR's author has not DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note Denotes a PR that will be considered when it comes time to generate release notes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants