Skip to content

NO-ISSUE: Fix OCP-83105#1238

Closed
bandrade wants to merge 1 commit intoopenshift:mainfrom
bandrade:fix/ocp83105
Closed

NO-ISSUE: Fix OCP-83105#1238
bandrade wants to merge 1 commit intoopenshift:mainfrom
bandrade:fix/ocp83105

Conversation

@bandrade
Copy link
Copy Markdown
Contributor

@bandrade bandrade commented Feb 24, 2026

Summary

  • update OLMv0 static networkpolicy test expectations for API-server egress rule changes
  • align catalog-operator, olm-operator, package-server-manager, and packageserver expected first egress rule with wildcard egress ({})
  • keep remaining DNS and service-port checks unchanged

Why

Recent networkpolicy changes switched API-server egress from explicit 6443/TCP to wildcard rule semantics, causing PolarionID:83105 failures (egress ports count mismatch).

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@bandrade: This pull request explicitly references no jira issue.

Details

In response to this:

Summary\n- update OLMv0 static networkpolicy test expectations for API-server egress rule changes\n- align , , , and expected first egress rule with wildcard egress ()\n- keep remaining DNS and service-port checks unchanged\n\n## Why\nRecent networkpolicy changes switched API-server egress from explicit to wildcard rule semantics, causing PolarionID:83105 failures (egress ports count mismatch).\n\n## Testing\n- ? github.com/openshift/operator-framework-olm/tests-extension/test/qe/specs [no test files]

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 24, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details Needs approval from an approver in each of these files:

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 24, 2026

@bandrade: 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/e2e-aws-olmv0-ext 3f15a45 link true /test e2e-aws-olmv0-ext
ci/prow/e2e-upgrade 3f15a45 link true /test e2e-upgrade
ci/prow/e2e-gcp-ovn 3f15a45 link true /test e2e-gcp-ovn

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.

@kuiwang02
Copy link
Copy Markdown
Contributor

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 25, 2026
@kuiwang02
Copy link
Copy Markdown
Contributor

/close

because of #1239

@openshift-ci openshift-ci Bot closed this Feb 25, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 25, 2026

@kuiwang02: Closed this PR.

Details

In response to this:

/close

because of #1239

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.

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

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants