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 2016175: UPSTREAM: <carry>: bump cadvisor for 2957, 2999, 2979 upstream patches #1070

Closed
wants to merge 1 commit into from

Conversation

kolyshkin
Copy link

What type of PR is this?

/kind bug

What this PR does / why we need it:

This is the same as #1049 but for 4.8 branch.

This brings in latest cadvisor changes in our fork of 4.8 branch:

Which issue(s) this PR fixes:

Fixes # https://bugzilla.redhat.com/show_bug.cgi?id=1978528, https://bugzilla.redhat.com/show_bug.cgi?id=2016175

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

none

This was generated by hack/pin-dependency.sh, updated with
upstream commits 808659c and de47d00, using
the following commands:

	./hack/pin-dependency.sh github.com/google/cadvisor=github.com/openshift/google-cadvisor openshift-4.8-cdavisor-v0.39.2
	./hack/update-vendor.sh

I have also checked that warnings from ./hack/lint-dependencies.sh
are the same before and after this change.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@openshift-ci openshift-ci bot added kind/bug Categorizes issue or PR as related to a bug. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. labels Nov 22, 2021
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Nov 22, 2021
@openshift-ci-robot
Copy link

@kolyshkin: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 22, 2021
@openshift-ci
Copy link

openshift-ci bot commented Nov 22, 2021

@kolyshkin: This pull request references Bugzilla bug 2016175, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA 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:

Bug 2016175: UPSTREAM: : bump cadvisor for 2957, 2999, 2979 upstream patches

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 bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. vendor-update Touching vendor dir or related files labels Nov 22, 2021
@openshift-ci openshift-ci bot requested review from mrunalp and sttts November 22, 2021 20:56
@openshift-ci
Copy link

openshift-ci bot commented Nov 22, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kolyshkin
To complete the pull request process, please assign soltysh after the PR has been reviewed.
You can assign the PR to them by writing /assign @soltysh in a comment when ready.

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

@kolyshkin kolyshkin changed the base branch from master to release-4.8 November 22, 2021 20:58
@openshift-ci
Copy link

openshift-ci bot commented Nov 22, 2021

@kolyshkin: This pull request references Bugzilla bug 2016175, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.10.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA instead
  • expected Bugzilla bug 2016175 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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:

Bug 2016175: UPSTREAM: : bump cadvisor for 2957, 2999, 2979 upstream patches

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 removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 22, 2021
@kolyshkin
Copy link
Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Dec 4, 2021

@kolyshkin: 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/prow/artifacts 08879e7 link true /test artifacts
ci/prow/e2e-aws-cgroupsv2 08879e7 link false /test e2e-aws-cgroupsv2

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.

@kolyshkin
Copy link
Author

/retest

@kolyshkin
Copy link
Author

/test artifacts
/test e2e-aws-cgroupsv2

@openshift-ci
Copy link

openshift-ci bot commented Dec 21, 2021

@kolyshkin: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test configmap-scale
  • /test e2e-agnostic-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-downgrade
  • /test e2e-aws-fips
  • /test e2e-aws-jenkins
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-serial
  • /test e2e-aws-upgrade
  • /test e2e-azure
  • /test e2e-azure-upgrade
  • /test e2e-gcp
  • /test e2e-gcp-upgrade
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-vsphere
  • /test images
  • /test integration
  • /test k8s-e2e-conformance-aws
  • /test k8s-e2e-gcp
  • /test k8s-e2e-gcp-serial
  • /test unit
  • /test verify
  • /test verify-commits

The following commands are available to trigger optional jobs:

  • /test e2e-aws-csi-migration
  • /test e2e-aws-disruptive
  • /test e2e-aws-single-node

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-kubernetes-release-4.8-e2e-agnostic-cmd
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-csi
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-downgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-fips
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-jenkins
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-multitenant
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-ovn
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-serial
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-azure
  • pull-ci-openshift-kubernetes-release-4.8-e2e-azure-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.8-e2e-gcp-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-kubernetes-release-4.8-e2e-vsphere
  • pull-ci-openshift-kubernetes-release-4.8-images
  • pull-ci-openshift-kubernetes-release-4.8-integration
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-release-4.8-unit
  • pull-ci-openshift-kubernetes-release-4.8-verify
  • pull-ci-openshift-kubernetes-release-4.8-verify-commits

In response to this:

/test artifacts
/test e2e-aws-cgroupsv2

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

The requirements for Bugzilla bugs have changed, recalculating validity.

@openshift-ci
Copy link

openshift-ci bot commented Jan 1, 2022

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

  • expected the bug to target the "4.8.z" release, but it targets "4.10.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2016175 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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

The requirements for Bugzilla bugs have changed, recalculating validity.

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

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Apr 1, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 1, 2022

@kolyshkin: PR needs rebase.

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.

@kolyshkin kolyshkin closed this Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants