Bump KUBEVIRT to v0.30.0-rc.1

[github-actions]

Bump KUBEVIRT to v0.30.0-rc.1
Executed by HCO Release-Bumper Bot.

Bump KUBEVIRT to v0.30.0-rc.1

[ovirt-infra]

Hello contributor, thanks for submitting a PR for this project!

I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.

In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

1. Type ci test please on this PR to trigger automated tests for it.
2. Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow Manage kubevirt CR from sdk generated code #3 option )
3. If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

[openshift-ci-robot]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign orenc1
You can assign the PR to them by writing /assign @orenc1 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:

• OWNERS

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

[orenc1]

/ok-to-test

[orenc1]

@danielBelenky @tiraboschi kubevirt is degraded because of:

 Available	False	KubeVirt is not available: An error occurred during deployment: unable to create config map &ConfigMap{ObjectMeta:{kubevirt-cpu-plugin-configmap  kubevirt-hyperconverged    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[app.kubernetes.io/managed-by:kubevirt-operator] map[kubevirt.io/install-strategy-identifier:020973b690602ac48140963e236ea950769a19f6 kubevirt.io/install-strategy-registry:docker.io/kubevirt kubevirt.io/install-strategy-version:v0.30.0-rc.1] [] []  []},Data:map[string]string{cpu-plugin-configmap.yaml: obsoleteCPUs:
- "486"
- "pentium"
- "pentium2"
- "pentium3"
- "pentiumpro"
- "coreduo"
- "n270"
- "core2duo"
- "Conroe"
- "athlon"
- "phenom"
minCPU: "Penryn",},BinaryData:map[string][]byte{},}: configmaps "kubevirt-cpu-plugin-configmap" already exists 

[orenc1]

/retest

[danielBelenky]

@danielBelenky @tiraboschi kubevirt is degraded because of:

 Available	False	KubeVirt is not available: An error occurred during deployment: unable to create config map &ConfigMap{ObjectMeta:{kubevirt-cpu-plugin-configmap  kubevirt-hyperconverged    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[app.kubernetes.io/managed-by:kubevirt-operator] map[kubevirt.io/install-strategy-identifier:020973b690602ac48140963e236ea950769a19f6 kubevirt.io/install-strategy-registry:docker.io/kubevirt kubevirt.io/install-strategy-version:v0.30.0-rc.1] [] []  []},Data:map[string]string{cpu-plugin-configmap.yaml: obsoleteCPUs:
- "486"
- "pentium"
- "pentium2"
- "pentium3"
- "pentiumpro"
- "coreduo"
- "n270"
- "core2duo"
- "Conroe"
- "athlon"
- "phenom"
minCPU: "Penryn",},BinaryData:map[string][]byte{},}: configmaps "kubevirt-cpu-plugin-configmap" already exists 

This error is because we have node lablerrer code in virt-handler and in the standalone code... I thought that it was reverted already... @omeryahud

[orenc1]

This error is because we have node lablerrer code in virt-handler and in the standalone code... I thought that it was reverted already... @omeryahud

NodeLabeller is still part of virt-handler in tag v0.30.0-rc.1
https://github.com/kubevirt/kubevirt/tree/v0.30.0-rc.1/pkg/virt-handler/node-labeller

[omeryahud]

node-labeller was reverted from kubevirt in the release-0.29 branch
kubevirt/kubevirt#3462

[orenc1]

node-labeller was reverted from kubevirt in the release-0.29 branch
kubevirt/kubevirt#3462

Then how did it popped out in v0.30.0-rc.1 again?
https://github.com/kubevirt/kubevirt/blob/v0.30.0-rc.1/cmd/virt-launcher/BUILD.bazel#L64

[orenc1]

/rebase

[orenc1]

/rebase

[kubevirt-bot]

@github-actions[bot]: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-hyperconverged-cluster-operator-e2e-ocp-4.3	15af91d	link	/test pull-hyperconverged-cluster-operator-e2e-ocp-4.3
pull-hyperconverged-cluster-operator-e2e-k8s-1.15.1	15af91d	link	/test pull-hyperconverged-cluster-operator-e2e-k8s-1.15.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.

[openshift-ci-robot]

@github-actions[bot]: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/hco-e2e-aws	15af91d	link	/test hco-e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[tiraboschi]

waiting for #615