[release-4.9] Bug 2101794: Avoid kubernetes node port range #182

openshift-cherrypick-robot · 2022-06-28T11:51:22Z

This is an automated cherry-pick of #178

/assign cybertron

Per [0], the range 30000-32767 is used for kubernetes node ports. We should not have haproxy listening in that range to avoid possible conflicts. Setting the port to 20000 higher than the service port, per the network team convention[1]. 0: https://github.com/openshift/openshift-docs/blob/main/modules/installation-network-user-infra.adoc 1: openshift/enhancements#1076 (comment)

openshift-ci · 2022-06-28T11:51:42Z

@openshift-cherrypick-robot: Bugzilla bug 2084187 has been cloned as Bugzilla bug 2101794. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2101794: Avoid kubernetes node port range

In response to this:

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.

openshift-ci · 2022-06-28T11:51:57Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

vvoronkov · 2022-06-28T12:32:04Z

/label cherry-pick-approved

openshift-ci · 2022-06-28T14:26:54Z

@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/test-infra repository. I understand the commands that are listed here.

cybertron · 2022-06-28T21:32:16Z

/cherry-pick release-4.8
/lgtm
/label backport-risk-assessed

openshift-cherrypick-robot · 2022-06-28T21:32:19Z

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

In response to this:

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.

openshift-ci · 2022-06-28T21:33:11Z

[APPROVALNOTIFIER] This PR is APPROVED

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

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~~ [cybertron]

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

openshift-bot · 2022-06-29T01:01:16Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-06-29T01:01:25Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-06-30T01:01:13Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-06-30T01:01:39Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-01T01:01:08Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-01T01:02:50Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-02T01:00:40Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-02T01:01:02Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-03T01:00:39Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-03T01:01:01Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-04T01:00:41Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot · 2022-07-11T01:00:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-11T01:01:11Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-12T01:01:03Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-12T01:01:21Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-13T01:01:17Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-13T01:01:39Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-14T01:00:50Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-14T01:01:14Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-15T01:00:55Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-15T01:01:42Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-16T01:00:43Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-16T01:01:08Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-17T01:01:02Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-17T01:01:22Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-18T01:00:46Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-18T01:01:08Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-19T01:00:44Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-19T01:00:54Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

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

In response to this:

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.

openshift-bot · 2022-07-20T01:00:47Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-20T01:01:05Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is invalid:

expected dependent Bugzilla bug 2084187 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

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

In response to this:

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.

openshift-bot · 2022-07-21T01:01:02Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-07-21T01:01:34Z

@openshift-bot: This pull request references Bugzilla bug 2101794, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.9.z) matches configured target release for branch (4.9.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2084187 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2084187 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (sserafin@redhat.com), skipping review request.

In response to this:

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.

openshift-ci · 2022-07-21T01:05:20Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

openshift/baremetal-runtimecfg#182

Bugzilla bug 2101794 has been moved to the MODIFIED state.

In response to this:

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.

openshift-cherrypick-robot · 2022-07-21T01:05:59Z

@cybertron: new pull request created: #187

In response to this:

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.

openshift-bot · 2023-11-25T01:31:01Z

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-baremetal-runtimecfg-container-v4.9.0-202311250023.p0.ge3602f0.assembly.stream for distgit baremetal-runtimecfg.
All builds following this will include this PR.

openshift-cherrypick-robot mentioned this pull request Jun 28, 2022

[release-4.10] Bug 2084187: Avoid kubernetes node port range #178

Merged

openshift-ci bot assigned cybertron Jun 28, 2022

openshift-ci bot changed the title ~~[release-4.9] Bug 2084187: Avoid kubernetes node port range~~ [release-4.9] Bug 2101794: Avoid kubernetes node port range Jun 28, 2022

openshift-ci bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jun 28, 2022

openshift-ci bot requested review from celebdor and cybertron June 28, 2022 11:52

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 28, 2022

openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. lgtm Indicates that a PR is ready to be merged. labels Jun 28, 2022

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 28, 2022

openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jul 21, 2022

openshift-merge-robot merged commit e3602f0 into openshift:release-4.9 Jul 21, 2022

openshift-cherrypick-robot mentioned this pull request Jul 21, 2022

[release-4.8] Bug 2109329: Avoid kubernetes node port range #187

Merged

openshift-ci bot mentioned this pull request Aug 29, 2022

[release-4.9] Bug 2101794: Avoid kubernetes node port range openshift/machine-config-operator#3255

Merged

[release-4.9] Bug 2101794: Avoid kubernetes node port range #182

[release-4.9] Bug 2101794: Avoid kubernetes node port range #182

Conversation

openshift-cherrypick-robot commented Jun 28, 2022

openshift-ci bot commented Jun 28, 2022

openshift-ci bot commented Jun 28, 2022

vvoronkov commented Jun 28, 2022

openshift-ci bot commented Jun 28, 2022

cybertron commented Jun 28, 2022

openshift-cherrypick-robot commented Jun 28, 2022

openshift-ci bot commented Jun 28, 2022

openshift-bot commented Jun 29, 2022

openshift-ci bot commented Jun 29, 2022

openshift-bot commented Jun 30, 2022

openshift-ci bot commented Jun 30, 2022

openshift-bot commented Jul 1, 2022

openshift-ci bot commented Jul 1, 2022

openshift-bot commented Jul 2, 2022

openshift-ci bot commented Jul 2, 2022

openshift-bot commented Jul 3, 2022

openshift-ci bot commented Jul 3, 2022

openshift-bot commented Jul 4, 2022

openshift-bot commented Jul 11, 2022

openshift-ci bot commented Jul 11, 2022

openshift-bot commented Jul 12, 2022

openshift-ci bot commented Jul 12, 2022

openshift-bot commented Jul 13, 2022

openshift-ci bot commented Jul 13, 2022

openshift-bot commented Jul 14, 2022

openshift-ci bot commented Jul 14, 2022

openshift-bot commented Jul 15, 2022

openshift-ci bot commented Jul 15, 2022

openshift-bot commented Jul 16, 2022

openshift-ci bot commented Jul 16, 2022

openshift-bot commented Jul 17, 2022

openshift-ci bot commented Jul 17, 2022

openshift-bot commented Jul 18, 2022

openshift-ci bot commented Jul 18, 2022

openshift-bot commented Jul 19, 2022

openshift-ci bot commented Jul 19, 2022

openshift-bot commented Jul 20, 2022

openshift-ci bot commented Jul 20, 2022

openshift-bot commented Jul 21, 2022

openshift-ci bot commented Jul 21, 2022

openshift-ci bot commented Jul 21, 2022

openshift-cherrypick-robot commented Jul 21, 2022

openshift-bot commented Nov 25, 2023