[release-1.1] Deprecate cpu and memory exceeds alerts #11445

avlitman · 2024-03-06T08:49:57Z

What this PR does / why we need it:
Deprecate the KubeVirtComponentExceedsRequestedCPU and KubeVirtComponentExceedsRequestedMemory alerts.
These alerts are wrong and don't need to be reported to the user.

Which issue(s) this PR fixes:
Jira-Ticket: https://issues.redhat.com/browse/CNV-37900

Special notes for your reviewer:

https://issues.redhat.com/browse/CNV-38320 will handle adding a metric to be able to track this issue without creating noise.

Release note:

KubeVirtComponentExceedsRequestedCPU and KubeVirtComponentExceedsRequestedMemory alerts are deprecated; they do not indicate a genuine issue.

Signed-off-by: avlitman <alitman@redhat.com>

avlitman · 2024-03-07T08:14:28Z

/retest

avlitman · 2024-03-07T10:52:41Z

/retest

avlitman · 2024-03-07T11:26:05Z

/retest

avlitman · 2024-03-10T09:53:57Z

/retest

avlitman · 2024-03-10T14:50:43Z

/retest

avlitman · 2024-03-12T10:48:01Z

/retest

kubevirt-commenter-bot · 2024-03-12T10:48:05Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:08Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:11Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:13Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:16Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:18Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:20Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:22Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:24Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:26Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:28Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:31Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:32Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:35Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-12T10:48:37Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-13T09:35:14Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-13T09:35:16Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-13T09:35:19Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-13T09:35:21Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-13T09:35:24Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

kubevirt-commenter-bot · 2024-03-13T09:35:26Z

✋🧢

/hold

⚠️ 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!

👌 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 KubeVirt community!

Checklist:

✅ your changes compile
✅ no linting errors
✅ no unit test errors
✅ no recurring e2e test errors, i.e. in the check-tests-for-flakes lane
✅ no infrastructure issues, i.e. GitHub 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. Note that Phase2 comments are excluded from this number.

enp0s3 · 2024-03-13T10:20:44Z

@machadovilaca Hey, can you please help investigating the failure? maybe some leftover from previous monitoring test spec.

avlitman · 2024-03-13T10:49:54Z

@machadovilaca @enp0s3 I did ran make generate and make all and it passed manually, and I looked at the ci logs it does not seem related to the changed I did in this pr so I'm really not sure..

enp0s3 · 2024-03-13T11:02:59Z

@avlitman It may not be related to your changes but still it can be flaky. The flake could be fixed in main but didn't backport. Note that monitoring lane is not always triggered so it may have been flaky and unnoticed

machadovilaca · 2024-03-13T11:07:12Z

looking

enp0s3 · 2024-03-13T11:11:41Z

@avlitman @machadovilaca Please note that the previous ginkgo container errors metrics deals with deleting and creating the virt-operator role binding, it may affect the access of virt-operator to to the api components

machadovilaca · 2024-03-13T11:51:25Z

@avlitman @machadovilaca Please note that the previous ginkgo container errors metrics deals with deleting and creating the virt-operator role binding, it may affect the access of virt-operator to to the api components

seems strange, in that case I would expect a fail in both:

_, err = virtClient.RbacV1().ClusterRoleBindings().Create(context.Background(), crb, metav1.CreateOptions{})
			if !errors.IsAlreadyExists(err) {
				util.PanicOnError(err)
			}

and

			waitUntilAlertDoesNotExist(virtClient, virtOperator.downAlert, virtApi.downAlert, virtController.downAlert, virtHandler.downAlert)

the role binding wouldn't have been restored properly, and the alert should still be firing

machadovilaca · 2024-03-14T13:21:35Z

@enp0s3 @avlitman #11506

avlitman · 2024-03-14T13:23:25Z

@enp0s3 @avlitman #11506

Thank you for creating a fix. So @enp0s3 let's merge the fix first right?

dhiller · 2024-03-14T14:25:13Z

/test pull-kubevirt-goveralls-1.1

avlitman · 2024-04-03T11:06:29Z

/retest

avlitman · 2024-04-10T11:59:49Z

/retest

avlitman · 2024-04-10T17:43:33Z

Hi @enp0s3 monitoring lane succeed any chance you can take a look again? can we close #11506?

enp0s3 · 2024-04-11T06:15:54Z

Hi @enp0s3 monitoring lane succeed any chance you can take a look again? can we close #11506?

@avlitman @machadovilaca I don't think its a good idea to close #11506 unless the situation described there is not correct. However with regards to this PR I think we can merge it since the issue was with the CI.

enp0s3

/hold cancel
/approve

kubevirt-bot · 2024-04-11T06:16:33Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enp0s3

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~~ [enp0s3]

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

enp0s3 · 2024-04-11T06:16:38Z

/retest-required

kubevirt-bot · 2024-04-11T08:54:40Z

@avlitman: 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
pull-kubevirt-e2e-arm64	`5b07175`	link	false	`/test pull-kubevirt-e2e-arm64-1.1`
pull-kubevirt-check-tests-for-flakes	`5b07175`	link	false	`/test pull-kubevirt-check-tests-for-flakes-1.1`
pull-kubevirt-goveralls	`5b07175`	link	false	`/test pull-kubevirt-goveralls-1.1`

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.

enp0s3 · 2024-04-11T10:36:58Z

/retest-required

[release-1.1] Deprecate cpu and memory exceeds alerts

5b07175

Signed-off-by: avlitman <alitman@redhat.com>

kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/L labels Mar 6, 2024

kubevirt-bot requested review from jean-edouard, kbidarkar and rthallisey March 6, 2024 08:50

kubevirt-bot added the area/monitoring label Mar 6, 2024

kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 12, 2024

machadovilaca mentioned this pull request Mar 13, 2024

Fix monitoring e2e failures due to missing CRBs #11506

Closed

8 tasks

enp0s3 approved these changes Apr 11, 2024

View reviewed changes

kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 11, 2024

kubevirt-bot assigned enp0s3 Apr 11, 2024

kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 11, 2024

kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 11, 2024

kubevirt-bot merged commit 6b6d0a1 into kubevirt:release-1.1 Apr 11, 2024
33 of 36 checks passed

[release-1.1] Deprecate cpu and memory exceeds alerts #11445

[release-1.1] Deprecate cpu and memory exceeds alerts #11445

Conversation

avlitman commented Mar 6, 2024 • edited

avlitman commented Mar 7, 2024

avlitman commented Mar 7, 2024

avlitman commented Mar 7, 2024

avlitman commented Mar 10, 2024

avlitman commented Mar 10, 2024

avlitman commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 12, 2024

kubevirt-commenter-bot commented Mar 13, 2024

kubevirt-commenter-bot commented Mar 13, 2024

kubevirt-commenter-bot commented Mar 13, 2024

kubevirt-commenter-bot commented Mar 13, 2024

kubevirt-commenter-bot commented Mar 13, 2024

kubevirt-commenter-bot commented Mar 13, 2024

enp0s3 commented Mar 13, 2024

avlitman commented Mar 13, 2024

enp0s3 commented Mar 13, 2024

machadovilaca commented Mar 13, 2024

enp0s3 commented Mar 13, 2024

machadovilaca commented Mar 13, 2024

machadovilaca commented Mar 14, 2024

avlitman commented Mar 14, 2024

dhiller commented Mar 14, 2024

avlitman commented Apr 3, 2024

avlitman commented Apr 10, 2024

avlitman commented Apr 10, 2024 • edited

enp0s3 commented Apr 11, 2024

enp0s3 left a comment

Choose a reason for hiding this comment

kubevirt-bot commented Apr 11, 2024

enp0s3 commented Apr 11, 2024

kubevirt-bot commented Apr 11, 2024 • edited

enp0s3 commented Apr 11, 2024

avlitman commented Mar 6, 2024 •

edited

avlitman commented Apr 10, 2024 •

edited

kubevirt-bot commented Apr 11, 2024 •

edited