[release-4.19] OCPBUGS-67264: cherry pick to few fixes that needed for missing services and configuration

[openshift-cherrypick-robot]

This is an automated cherry-pick of #5480

/assign yuqi-zhang

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65545 has been cloned as Jira Issue OCPBUGS-67264. Will retitle bug to link to clone.

Jira Issue OCPBUGS-67007 has been cloned as Jira Issue OCPBUGS-67265. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-67264, OCPBUGS-67265: cherry pick to few fixes that needed for missing services and configuration

Details

In response to this:

This is an automated cherry-pick of #5480

/assign yuqi-zhang

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-67264, which is invalid:

• expected dependent Jira Issue OCPBUGS-65545 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-67265, which is invalid:

• expected dependent Jira Issue OCPBUGS-67007 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #5480

/assign yuqi-zhang

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.

[yuqi-zhang]

/jira refresh

removed one of the bugs to make it easier to backport

[openshift-ci-robot]

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-67264, which is invalid:

• expected dependent Jira Issue OCPBUGS-65545 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

removed one of the bugs to make it easier to backport

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.

[yuqi-zhang]

/jira refresh
/approve
/lgtm
/label backport-risk-assessed

[openshift-ci-robot]

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-67264, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.z) matches configured target version for branch (4.19.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-65545 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-65545 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
• bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

/jira refresh
/approve
/lgtm
/label backport-risk-assessed

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yuqi-zhang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [yuqi-zhang]

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

[yuqi-zhang]

/cherry-pick release-4.18
/verified later @aabughosh

I think we can get this in given the previous versions have been validated, and we can continue the process that way.

[openshift-cherrypick-robot]

@yuqi-zhang: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.18
/verified later @aabughosh

I think we can get this in given the previous versions have been validated, and we can continue the process that way.

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.

[openshift-ci-robot]

@yuqi-zhang: This PR has been marked to be verified later by @aabughosh.

Details

In response to this:

/cherry-pick release-4.18
/verified later @aabughosh

I think we can get this in given the previous versions have been validated, and we can continue the process that way.

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 1953be0 and 2 for PR HEAD 507dbb2 in total

[yuqi-zhang]

/retest-required

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-67264: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#5490

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-67264 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #5480

/assign yuqi-zhang

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.

[openshift-cherrypick-robot]

@yuqi-zhang: #5490 failed to apply on top of branch "release-4.18":

Applying: Add hostIP 127.0.0.1 to machine-config-daemon port 8798
Applying: add a relevant svc to the crio port
Using index info to reconstruct a base tree...
A	templates/arbiter/01-arbiter-kubelet/_base/files/criometricsproxy.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): templates/arbiter/01-arbiter-kubelet/_base/files/criometricsproxy.yaml deleted in HEAD and modified in add a relevant svc to the crio port. Version add a relevant svc to the crio port of templates/arbiter/01-arbiter-kubelet/_base/files/criometricsproxy.yaml left in tree.
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 0002 add a relevant svc to the crio port

Details

In response to this:

/cherry-pick release-4.18
/verified later @aabughosh

I think we can get this in given the previous versions have been validated, and we can continue the process that way.

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.