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

Bug 2024640: Rebase v1.20.14 #1101

Merged

Conversation

josefkarasek
Copy link

nilo19 and others added 30 commits October 22, 2021 10:33
hostPath volume plugin creates a directory within /tmp on host machine, to be mounted as volume.
inject-pod writes content to the volume, and a client-pod tried the read the contents and verify.
when SELinux is enabled on the host, client-pod can not read the content, with permission denied.
running the client-pod as privileged, so that it can access the volume content, even when SEinux is enabled on the host.
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
…ck-of-#105734-upstream-release-1.20

Automated cherry pick of kubernetes#105734: Fix race condition in logging when request times out
…leged-storage-client-1.20

Cherry pick of kubernetes#104551: Run storage hostpath e2e test client pod as privileged
…ick-of-#105997-upstream-release-1.20

Automated cherry pick of kubernetes#105997: Fixing how EndpointSlice Mirroring handles Service selector
Update debian, debian-iptables images to pick up CVEs fixes
…g paths

Signed-off-by: Monis Khan <mok@vmware.com>
…pick-of-#105755-upstream-release-1.20

Automated cherry pick of kubernetes#105755: Support cgroupv2 in node problem detector test
When GetSELinuxSupport() fails, don't assume a mounted filesystem does not
support SELinux at all. Try again instead in the next SetUp retry.

This may hurt performance a bit, since kubelet will call NodePublishVolume
again, but it's better than providing wrong information to the container
runtime that will then skip relabeling of the volume.
Skip parsing of /proc/mounts if SELinux is disabled on the machine.
Previously, an error from GetSELinuxSupport was treated as a filesystem did
not support SELinux. Now the error is treated separately.
…f-#94165-upstream-release-1.20

Automated cherry pick of kubernetes#94165: Use separate pathSpec for local and remote to properly handle
…ick-of-#105934-upstream-release-1.20

Automated cherry pick of kubernetes#105934: Don't guess SELinux support on error
Bump kube-openapi against kube-openapi/release-1.20 branch

Signed-off-by: Alper Rifat Ulucinar <ulucinar@users.noreply.github.com>
Manual cherry pick of kube-openapi changes for release-1.20
Different CSI drivers have different error messages, making it difficult
to check them accurately. We remove the check for the error message and
only check the failure type instead, since that is all we need.
…ck-of-#105512-upstream-release-1.20

Automated cherry pick of kubernetes#105512: Add check for subpaths
…-pick-of-#105673-upstream-release-1.20

Automated cherry pick of kubernetes#105673: support more than 100 disk mounts on Windows
@openshift-bot
Copy link

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Feb 26, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Feb 27, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Feb 28, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Mar 1, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Mar 2, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

@gangwgr
Copy link

gangwgr commented Mar 2, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 2, 2022
@openshift-bot
Copy link

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2022

@openshift-bot: This pull request references Bugzilla bug 2024640, which is invalid:

  • expected the bug to target the "4.7.z" release, but it targets "---" instead
  • expected dependent Bugzilla bug 2024642 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

@soltysh
Copy link

soltysh commented Mar 3, 2022

Since #1102 merged I'm marking this as a valid-bug
/label bugzilla/valid-bug
/remove-label bugzilla/invalid-bug

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 3, 2022
@soltysh
Copy link

soltysh commented Mar 3, 2022

/override ci/prow/verify-commits

@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2022

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits

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

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@josefkarasek
Copy link
Author

/retest

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@josefkarasek
Copy link
Author

/test e2e-vsphere

@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2022

@josefkarasek: 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/verify-commits 010866c link unknown /test verify-commits

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.

@openshift-merge-robot openshift-merge-robot merged commit cc556b1 into openshift:release-4.7 Mar 3, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2022

@josefkarasek: All pull requests linked via external trackers have merged:

Bugzilla bug 2024640 has been moved to the MODIFIED state.

In response to this:

Bug 2024640: Rebase v1.20.14

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.