[release-4.19] OCPBUGS-67006: MCO-1886: add the missing service to the expose ports 22623 and 22624

[openshift-cherrypick-robot]

This is an automated cherry-pick of #5371

/assign aabughosh

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65544 has been cloned as Jira Issue OCPBUGS-67006. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-67006: MCO-1886: add the missing service to the expose ports 22623 and 22624

In response to this:

This is an automated cherry-pick of #5371

/assign aabughosh

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-67006, which is invalid:

• expected dependent Jira Issue OCPBUGS-65544 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead
• expected dependent Jira Issue OCPBUGS-65544 to target a version in 4.20.0, 4.20.z, but it targets "4.21.0" 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.

In response to this:

This is an automated cherry-pick of #5371

/assign aabughosh

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 NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign rishabhsaini for approval. For more information see the Code Review Process.

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

[aabughosh]

/jira refresh

[openshift-ci-robot]

@aabughosh: This pull request references Jira Issue OCPBUGS-67006, which is invalid:

• expected dependent Jira Issue OCPBUGS-65544 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
• expected dependent Jira Issue OCPBUGS-65544 to target a version in 4.20.0, 4.20.z, but it targets "4.21.0" 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.

In response to this:

/jira refresh

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.

[aabughosh]

/jira refresh

[openshift-ci-robot]

@aabughosh: This pull request references Jira Issue OCPBUGS-67006, which is invalid:

• expected dependent Jira Issue OCPBUGS-65544 to target a version in 4.20.0, 4.20.z, but it targets "4.19" 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.

In response to this:

/jira refresh

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.

[aabughosh]

/jira refresh

[openshift-ci-robot]

@aabughosh: This pull request references Jira Issue OCPBUGS-67006, which is invalid:

• expected dependent Jira Issue OCPBUGS-65544 to target a version in 4.20.0, 4.20.z, but it targets "4.20" 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.

In response to this:

/jira refresh

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.

[aabughosh]

/jira refresh

[openshift-ci-robot]

@aabughosh: This pull request references Jira Issue OCPBUGS-67006, 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-65544 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-65544 targets the "4.20.0" 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

In response to this:

/jira refresh

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]

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit	a2a1811	link	true	/test unit
ci/prow/e2e-gcp-op	a2a1811	link	true	/test e2e-gcp-op

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.

[sergiordlr]

Using AWS on IPI

$ oc -n openshift-machine-config-operator get service  |grep 22624
machine-config-server       ClusterIP   172.30.14.53     <none>        22623/TCP,22624/TCP   4h57m
$ oc -n openshift-machine-config-operator get service  |grep 22623
machine-config-server       ClusterIP   172.30.14.53     <none>        22623/TCP,22624/TCP   4h58m

/label qe-approved
/verified by @sergiordlr

[openshift-ci-robot]

@sergiordlr: This PR has been marked as verified by @sergiordlr.

In response to this:

Using AWS on IPI

$ oc -n openshift-machine-config-operator get service  |grep 22624
machine-config-server       ClusterIP   172.30.14.53     <none>        22623/TCP,22624/TCP   4h57m
$ oc -n openshift-machine-config-operator get service  |grep 22623
machine-config-server       ClusterIP   172.30.14.53     <none>        22623/TCP,22624/TCP   4h58m

/label qe-approved
/verified by @sergiordlr

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-67006, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-65544 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-65544 targets the "4.20.0" 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

In response to this:

This is an automated cherry-pick of #5371

/assign aabughosh

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]

Thanks for the verification. Will hold this until #5480 merges so we can backport together if possible

/hold

[yuqi-zhang]

/close

In favour of #5490

[openshift-ci]

@yuqi-zhang: Closed this PR.

In response to this:

/close

In favour of #5490

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]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-67006. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

This is an automated cherry-pick of #5371

/assign aabughosh

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.