Skip to content

Conversation

sabinaaledort
Copy link
Contributor

@sabinaaledort sabinaaledort commented Mar 13, 2025

The port is missing in the communication matrix

Version(s):

Issue:

Link to docs preview:
OpenShift Container Platform network flow matrix -- New line in Table 1.

QE review:

  • QE has approved this change.

Additional information:

The port is missing in the communication matrix
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 13, 2025
@sabinaaledort sabinaaledort changed the title Add missing metal3 5051 proxy port OCPBUGS-53084: Add missing metal3 5051 proxy port Mar 13, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 13, 2025
@openshift-ci-robot
Copy link

@sabinaaledort: This pull request references Jira Issue OCPBUGS-53084, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-53084 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

The port is missing in the communication matrix

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@sabinaaledort
Copy link
Contributor Author

/label peer-review-needed

@sabinaaledort
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@sabinaaledort: This pull request references Jira Issue OCPBUGS-53084, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-53084 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Mar 13, 2025
@sabinaaledort
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@sabinaaledort: This pull request references Jira Issue OCPBUGS-53084, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-53084 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

@ocpdocs-previewbot
Copy link

🤖 Thu Mar 13 15:25:06 - Prow CI generated the docs preview:

https://90235--ocpdocs-pr.netlify.app/

Copy link

openshift-ci bot commented Mar 13, 2025

@sabinaaledort: 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.

@mburke5678 mburke5678 added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Mar 13, 2025
@openshift-ci-robot
Copy link

@sabinaaledort: This pull request references Jira Issue OCPBUGS-53084, which is invalid:

  • expected Jira Issue OCPBUGS-53084 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

The port is missing in the communication matrix

Version(s):

Issue:

Link to docs preview:
OpenShift Container Platform network flow matrix -- New line in Table 1.

QE review:

  • QE has approved this change.

Additional information:

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.

@mburke5678
Copy link
Contributor

@sabinaaledort LGTM. Don't forget about QE review.

@mburke5678 mburke5678 added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Mar 13, 2025
@anuragthehatter
Copy link

Indeed, thanks for fixing @sabinaaledort

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 14, 2025
@sabinaaledort
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 14, 2025
@opayne1 opayne1 added merge-review-in-progress Signifies that the merge review team is reviewing this PR branch/enterprise-4.16 and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Mar 14, 2025
@opayne1 opayne1 added this to the Continuous Release milestone Mar 14, 2025
Copy link
Contributor

@opayne1 opayne1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@opayne1 opayne1 merged commit ec2fa2b into openshift:enterprise-4.16 Mar 14, 2025
2 checks passed
@openshift-ci-robot
Copy link

@sabinaaledort: Jira Issue OCPBUGS-53084: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-53084 has been moved to the MODIFIED state.

In response to this:

The port is missing in the communication matrix

Version(s):

Issue:

Link to docs preview:
OpenShift Container Platform network flow matrix -- New line in Table 1.

QE review:

  • QE has approved this change.

Additional information:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.16 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants