Skip to content

NO-ISSUE: Remove remaining webhook tests from serial - #520

Closed
perdasilva wants to merge 1 commit into
openshift:mainfrom
perdasilva:webhook-test-no-serial
Closed

NO-ISSUE: Remove remaining webhook tests from serial#520
perdasilva wants to merge 1 commit into
openshift:mainfrom
perdasilva:webhook-test-no-serial

Conversation

@perdasilva

@perdasilvaperdasilva commented Oct 13, 2025

Copy link
Copy Markdown
Contributor

In the current state only the validating webhook test was not in the [Serial] OTE profile. This PR updates the remaining specs out of serial.

@openshift-ci-robotopenshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 13, 2025
@openshift-ci-robot

Copy link
Copy Markdown

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

[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-ciopenshift-ciBot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
@perdasilva
perdasilvaforce-pushed the webhook-test-no-serial branch from b4475b9 to bc138adCompareOctober 13, 2025 15:59
@tmshort

Copy link
Copy Markdown
Contributor

/hold
This needs to occur after PR #519

@openshift-ciopenshift-ciBot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 13, 2025

@anik120anik120 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/lgtm

@openshift-ciopenshift-ciBot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2025
},
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMWebhookProviderOpenshiftServiceCA] OLMv1 operator with webhooks should have a working mutating webhook [Serial]",
"name": "[sig-olmv1][OCPFeatureGate:NewOLMWebhookProviderOpenshiftServiceCA] OLMv1 operator with webhooks should have a working mutating webhook",

@camilamacedo86camilamacedo86Oct 13, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/hold

Those tests were created as SERIAL because all tests were using the same sample.
Therefore, they could not run in parallel.

Now, if we want to move away from SERIAL we must:

  • Rename as done
  • Then, ensure that they are not serial see Ordered, Serial, func() { <- It must be changed
  • Ensure that each test will create a sample with a unique name ( bundle, CE and all that is used by each test must be unique )
  • Ensure that it works fine and will not cause flakes by testing with payload-aggregation 10 times.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

I'm pretty sure with Todd's changes we are generating unique images now, so no serial should work. I'll start the aggregate jobs. If those pass please unblock and merge.

@camilamacedo86camilamacedo86Oct 13, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If we are using unqiue names then:
We still needing to change Ordered, Serial, func() { <- That is what make the test run as serial
See;


The TAG [SERIAL] is valid for OCP CI ecosystem only.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Weird - maybe these have different meanings then because now the tests run in the periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview job... I'll remove them though

@openshift-ci

Copy link
Copy Markdown
Contributor

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

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 10

@openshift-ci

Copy link
Copy Markdown
Contributor

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/39cb2850-a879-11f0-8afe-24e1601928fb-0

@kuiwang02

Copy link
Copy Markdown
Contributor

@perdasilva

currently these are four webhook cases:
1, should have a working validating webhook
2, should have a working mutating webhook
3, should have a working conversion webhook
4, should be tolerant to tls secret deletion
they are using same package, and olmv1 install package at cluster level.
so, they are possible unstable if they are running in parallel. it is why I change only one to parallel, and keep others as serial.

we could research and verify if they are running in parallel without any conflicts. I will try it soon.
before that, I would expect it is held.

/hold

but for 4), it could be parallel even we found way to make webhook case in parallel because it is deletion operation.
so, finally 1,2,and 3 maybe be parallel, and 4 still is serial.

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@perdasilva
perdasilvaforce-pushed the webhook-test-no-serial branch from bc138ad to 41f798cCompareOctober 14, 2025 07:33
@openshift-ciopenshift-ciBot removed the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2025
@openshift-ci

Copy link
Copy Markdown
Contributor

New changes are detected. LGTM label has been removed.

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview 10

@openshift-ci

Copy link
Copy Markdown
Contributor

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a59c4030-a8d0-11f0-810e-0ecd61737c15-0

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

Labels

approvedIndicates a PR has been approved by an approver from all required OWNERS files.do-not-merge/holdIndicates that a PR should not merge because someone has issued a /hold command.jira/valid-referenceIndicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@perdasilva@openshift-ci-robot@tmshort@kuiwang02@anik120@camilamacedo86