[release-4.18] NO-JIRA: Fix the failures in qe ci jobs

[openshift-cherrypick-robot]

This is an automated cherry-pick of #374

/assign sunzhaohua2

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OCPQE-27285

In response to this:

This is an automated cherry-pick of #374

/assign sunzhaohua2

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 openshift-eng/jira-lifecycle-plugin repository.

[sunzhaohua2]

/retest

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[sunzhaohua2]

@JoelSpeed can you help to add labels to merge?

[JoelSpeed]

/approve
/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 [JoelSpeed]

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

[sunzhaohua2]

/label cherry-pick-approved

[sunzhaohua2]

I need to open a bug or we can merge this directly by adding a label manually?

[damdo]

Try with NO-JIRA in front of the PR title (after the release bit).
Not sure that will work but it is worth trying.
Also we'll likely need to wait until 4.18 is GA, as this requires steff-eng approved label

[sunzhaohua2]

/retitle [release-4.18] NO-JIRA: Fix the failures in qe ci jobs

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request explicitly references no jira issue.

In response to this:

This is an automated cherry-pick of #374

/assign sunzhaohua2

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 openshift-eng/jira-lifecycle-plugin repository.

[damdo]

@JoelSpeed will probably also need to add the jira/valid-bug label

[sunzhaohua2]

/cherry-pick release-4.17 release-4.16 release-4.15 release-4.14 release-4.13 release-4.12

[openshift-cherrypick-robot]

@sunzhaohua2: #380 failed to apply on top of branch "release-4.17":

Applying: Fix the failures in qe ci jobs
Using index info to reconstruct a base tree...
M	pkg/framework/framework.go
M	pkg/framework/machinesets.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/framework/machinesets.go
Auto-merging pkg/framework/framework.go
CONFLICT (content): Merge conflict in pkg/framework/framework.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Fix the failures in qe ci jobs

In response to this:

/cherry-pick release-4.17 release-4.16 release-4.15 release-4.14 release-4.13 release-4.12

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-sigs/prow repository.