[e2e-tests]Should remove and restore labeler only from workers

[Barakmor1]

Currently in some tests we are waiting for
the node labeller to be resumed in any nodes
including unschedulable nodes and that will not work
because master shouldn't be labeled by node
labeller.

Signed-off-by: bmordeha bmodeha@redhat.com

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

NONE

[iholder101]

/lgtm
Great stuff @Barakmor1! Thanks for the fix!

Tiny nit, in the PR description you write: including master nodes and that will not work because master shouldn't be labeled by node labeller. Can you replace master nodes with unschedulable nodes to align with the actual code?

[Barakmor1]

@iholder101 Done

[iholder101]

/lgtm

[kubevirt-bot]

@Barakmor1: 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-fossa	39a8d48	link	false	/test pull-kubevirt-fossa

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]

/approve

[kubevirt-bot]

[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:

• tests/OWNERS [enp0s3]

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

[Barakmor1]

/cherrypick release-0.58

[Barakmor1]

/cherrypick release-0.53

[kubevirt-bot]

@Barakmor1: new pull request created: #9274

In response to this:

/cherrypick release-0.58

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]

@Barakmor1: #9215 failed to apply on top of branch "release-0.53":

Applying: Should remove and restore labeller only from workers Currently in some tests we are waiting for the node labeller to be resumed in any nodes including unschedulable nodes and that will not work because master shouldn't be labeled by node labeller.
Using index info to reconstruct a base tree...
M	tests/hyperv_test.go
Falling back to patching base and 3-way merge...
Auto-merging tests/hyperv_test.go
CONFLICT (content): Merge conflict in tests/hyperv_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Should remove and restore labeller only from workers Currently in some tests we are waiting for the node labeller to be resumed in any nodes including unschedulable nodes and that will not work because master shouldn't be labeled by node labeller.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-0.53

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.

[fossedihelm]

/cherrypick release-0.59

[kubevirt-bot]

@fossedihelm: new pull request created: #9347

In response to this:

/cherrypick release-0.59

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.