kubevirt-bot

[APPROVALNOTIFIER] This PR is **APPROVED** This pull-request has been approved by: *RamLavi* The full list of commands accepted by this bot can be found [here](https://prow.ci.kubevirt.io/command-help?repo=kubevirt%2Fcluster-network-addons-operator). The pull request process is...

@RamLavi: Overrode contexts on behalf of RamLavi: pull-e2e-cnao-workflow-k8s-release-0.95 In response to [this](https://github.com/kubevirt/cluster-network-addons-operator/pull/2178#issuecomment-2764469802): >I inspected the issue. >The lane failed on macvtap-cni, on an unrelated issue. I will address it on...

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

Rotten issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle rotten`. /close

@kubevirt-bot: Closing this issue. In response to [this](https://github.com/kubevirt/containerized-data-importer/issues/2550#issuecomment-2022873463): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

@akalenyu: Reopened this issue. In response to [this](https://github.com/kubevirt/containerized-data-importer/issues/2550#issuecomment-3211420094): >/reopen > >@mhenriks in case you're interested, this is very old, but the issue was with selinux, >you get context matching for...

Rotten issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle rotten`. /close