[release-1.2] sig-observability: Update ownerships

[kubevirt-bot]

This is an automated cherry-pick of #11249

/assign avlitman

NONE

[iholder101]

/approve
FYI @fabiand, do you think it's okay to backport these?

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iholder101

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:

• OWNERS [iholder101]

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

[avlitman]

@fabiand @machadovilaca @sradco Can we remove the hold here?

[fabiand]

/unhold

[avlitman]

/retest

[avlitman]

/lgtm

[kubevirt-commenter-bot]

/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[kubevirt-commenter-bot]

/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[kubevirt-commenter-bot]

/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[kubevirt-commenter-bot]

/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[kubevirt-commenter-bot]

✋🧢

/hold

Dear @kubevirt-commenter-bot

⚠️ this pull request exceeds the number of retests that are allowed per individual commit.

🔎 Please check that the changes you committed are fine and that there are no infrastructure issues present!

Checklist:

• your changes compile
• your tests succeed locally, i.e. for k/kubevirt see
  • getting-started - testing and
  • CONTRIBUTING.md - testing
• no linting errors
• no recurring e2e test errors, i.e. in the pull-kubevirt-check-tests-for-flakes lane
• no infrastructure issues, i.e.
  • GitHub Status,
  • quay.io status at status.redhat.com or
  • KubeVirt prow status

💬 How we calculate the number of retests: The number of retest comments are the number of /test or /retest comments after the latest commit only.

👌 After all issues have been resolved, you can remove the hold on this pull request by commenting /unhold on it.

🙇 Thank you, your friendly referee automation, on behalf of the @sig-buildsystem and the KubeVirt community!

[brianmcarey]

/hold cancel

vgpu failures unrelated to this PR.

/override pull-kubevirt-e2e-kind-1.27-vgpu

[kubevirt-bot]

@brianmcarey: Overrode contexts on behalf of brianmcarey: pull-kubevirt-e2e-kind-1.27-vgpu

In response to this:

/hold cancel

vgpu failures unrelated to this PR.

/override pull-kubevirt-e2e-kind-1.27-vgpu

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.

[kubevirt-bot]

@kubevirt-bot: 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
pull-kubevirt-goveralls	9845584	link	false	/test pull-kubevirt-goveralls-1.2

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.