MULTIARCH-4229: UPSTREAM:<carry>:bump cadvisor for 3516 upstream patches

[harche]

What type of PR is this?

/kind feature

What this PR does / why we need it: To bring in google/cadvisor#3516 in OCP

Which issue(s) this PR fixes:

Fixes # https://issues.redhat.com/browse/MULTIARCH-4229

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

[openshift-ci-robot]

@harche: This pull request references MULTIARCH-4229 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 the "4.17.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it: To bring in google/cadvisor#3516 in OCP 4.17

Which issue(s) this PR fixes:

Fixes # https://issues.redhat.com/browse/MULTIARCH-4229

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

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.

[openshift-ci-robot]

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

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

• c8bc7a4|UPSTREAM::bump cadvisor for 3516 upstream patches: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[harche]

@madeelibm is the PR to bump the cadvisor in OCP 4.17

[madeelibm]

lgtm

[harche]

/test k8s-e2e-conformance-aws

[haircommander]

@harche can you retarget this to master? I think master is still forwarding down to 4.18/4.17 so you'll get it here too

[openshift-ci-robot]

@harche: This pull request references MULTIARCH-4229 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 the "4.17.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it: To bring in google/cadvisor#3516 in OCP 4.17

Which issue(s) this PR fixes:

Fixes # https://issues.redhat.com/browse/MULTIARCH-4229

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

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.

[harche]

@harche can you retarget this to master? I think master is still forwarding down to 4.18/4.17 so you'll get it here too

Done. let's see if it builds successfully.

[openshift-ci-robot]

@harche: This pull request references MULTIARCH-4229 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 the "4.17.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it: To bring in google/cadvisor#3516 in OCP

Which issue(s) this PR fixes:

Fixes # https://issues.redhat.com/browse/MULTIARCH-4229

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

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.

[madeelibm]

/retest

[madeelibm]

@harche verify-commits is failing due to commit message. See below:

UPSTREAM commit c8bc7a48e19 has invalid summary UPSTREAM:<carry>:bump cadvisor for 3516 upstream patches.

UPSTREAM commits are validated against the following regular expression:
  ^UPSTREAM: (revert: )?(([\w.-]+/[\w-.-]+)?: )?(\d+:|<carry>:|<drop>:)

UPSTREAM commit summaries should look like:

UPSTREAM: <PR number|carry|drop>: description

[openshift-ci-robot]

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

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

• 10f7516|UPSTREAM: :bump cadvisor for 3516 upstream patches: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

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

• 4ccf91a|UPSTREAM: : bump cadvisor for 3516 upstream patches: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

@harche: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

[rphillips]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: harche, mrunalp, rphillips

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:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: harche, mrunalp, rphillips

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:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rphillips]

/label acknowledge-critical-fixes-only

This should be extremely safe as it brings in s390 support.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-pod-container-v4.17.0-202407152240.p0.g27bcad5.assembly.stream.el9 for distgit openshift-enterprise-pod.
All builds following this will include this PR.