Skip to content

OPRUN-4441: fix(ote): Fix up own-namespace invalid configuration test#634

Open
perdasilva wants to merge 1 commit intoopenshift:mainfrom
perdasilva:fix-sons-e2e-own
Open

OPRUN-4441: fix(ote): Fix up own-namespace invalid configuration test#634
perdasilva wants to merge 1 commit intoopenshift:mainfrom
perdasilva:fix-sons-e2e-own

Conversation

@perdasilva
Copy link
Contributor

@perdasilva perdasilva commented Feb 7, 2026

When fixing up the sons ote tests #619 we also forgot to update the ownnamespace validity test.

Note: make fmt seems to have picked up some additional changes

@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 7, 2026
@openshift-ci-robot
Copy link

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

Details

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2026

@perdasilva: This PR was included in a payload test run from openshift/cluster-olm-operator#163
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e5d082e0-03fe-11f1-80a5-37871009a362-0

@perdasilva
Copy link
Contributor Author

perdasilva commented Feb 7, 2026

/retitle OPRUN-4441: fix(ote): Fix up own-namespace invalid configuration test

@openshift-ci openshift-ci bot changed the title NO-ISSUE: Fix up own-namespace invalid configuration test OPRUN-4441: fix(ote): Fix up own-namespace invalid configuration test Feb 7, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 7, 2026

@perdasilva: This pull request references OPRUN-4441 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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:

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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 7, 2026

@perdasilva: This pull request references OPRUN-4441 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

When fixing up the sons ote tests we also forgot to update the ownnamespace validity test

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 7, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 7, 2026

@perdasilva: This pull request references OPRUN-4441 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

When fixing up the sons ote tests #619 we also forgot to update the ownnamespace validity test

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

openshift-ci-robot commented Feb 7, 2026

@perdasilva: This pull request references OPRUN-4441 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

When fixing up the sons ote tests #619 we also forgot to update the ownnamespace validity test.

Note: make fmt seems to have picked up some additional changes

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
Contributor

openshift-ci bot commented Feb 7, 2026

@perdasilva: This PR was included in a payload test run from openshift/cluster-olm-operator#163
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/afda7730-03ff-11f1-9f39-2ffc63c478c4-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2026

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

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

2 participants