Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-33378: Verify Build Webhooks on Upgrade #28783

Merged

Conversation

adambkaplan
Copy link
Contributor

Updating the build suite test to verify the unautenticated build webhook behavior on upgrade. For clusters upgrading from v4.15 or earlier to v4.16, unauthenticated webhooks should continue to be allowed. For clusters that upgrade from v4.16 to a later version, unauthenticated webhooks should be denied by default.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 May 8, 2024
@openshift-ci-robot
Copy link

@adambkaplan: This pull request references Jira Issue OCPBUGS-33378, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

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:

Updating the build suite test to verify the unautenticated build webhook behavior on upgrade. For clusters upgrading from v4.15 or earlier to v4.16, unauthenticated webhooks should continue to be allowed. For clusters that upgrade from v4.16 to a later version, unauthenticated webhooks should be denied by default.

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.

@adambkaplan
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 8, 2024
@openshift-ci-robot
Copy link

@adambkaplan: This pull request references Jira Issue OCPBUGS-33378, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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.

@adambkaplan
Copy link
Contributor Author

/hold

Can we live with this skewed behavior when it comes to build webhooks?

cc @deads2k @soltysh

@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 May 8, 2024
@openshift-ci openshift-ci bot requested review from divyansh42 and stlaz May 8, 2024 17:15
@adambkaplan
Copy link
Contributor Author

Maintaining hold - this PR now depends on #28781

@stbenjam
Copy link
Member

stbenjam commented May 8, 2024

/retest-required
/payload-job periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade

Copy link
Contributor

openshift-ci bot commented May 8, 2024

@stbenjam: 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.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5c5ad590-0d7b-11ef-9e75-f6489e31cd5e-0

@stbenjam
Copy link
Member

stbenjam commented May 8, 2024

/payload-job periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-sdn-upgrade

Copy link
Contributor

openshift-ci bot commented May 8, 2024

@stbenjam: 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.16-e2e-aws-sdn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/73cf03e0-0d7b-11ef-8969-56421e5d3111-0

@stbenjam
Copy link
Member

stbenjam commented May 8, 2024

/lgtm

Should be ok to remove the hold once we get clean micro and minor upgrade signal (see above)

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 8, 2024
…ticated-webhook-bc"

This reverts commit e3c844d,
restoring the test changes in origin#28750.
Updating the build suite test to verify the unautenticated build
webhook behavior on upgrade. For clusters upgrading from v4.15 or
earlier to v4.16, unauthenticated webhooks should continue to be
allowed. For clusters that upgrade from v4.16 to a later version,
unauthenticated webhooks should be denied by default.

Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 8, 2024
@stbenjam
Copy link
Member

stbenjam commented May 8, 2024

/payload-job periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade
/payload-job periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-sdn-upgrade
/lgtm

Copy link
Contributor

openshift-ci bot commented May 8, 2024

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

  • periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-sdn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/10091070-0d7c-11ef-857e-f5518f7e2113-0

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 8, 2024
Copy link
Contributor

openshift-ci bot commented May 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan, stbenjam

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:

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


// AUTH-509: Webhooks do not allow unauthenticated requests by default.
// Create a role binding which allows unauthenticated webhooks.
g.BeforeEach(func() {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note - for clusters upgrading from 4.15 or earlier, this is effectively a no-op. system:unauthenticated is granted the system:webhooks role globally.

@sanchezl
Copy link
Contributor

sanchezl commented May 9, 2024

/retest-required

@adambkaplan
Copy link
Contributor Author

/payload-job periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade

Copy link
Contributor

openshift-ci bot commented May 9, 2024

@adambkaplan: 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.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0c1e6a80-0e05-11ef-8a55-969d840c8a15-0

@adambkaplan
Copy link
Contributor Author

/hold cancel

Payload upgrade test from 4.15 stable to 4.16 passed 🎉

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 9, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8045e28 and 2 for PR HEAD 4820d3e in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ac69ee5 and 1 for PR HEAD 4820d3e in total

@sanchezl
Copy link
Contributor

/retest-required

@adambkaplan
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 62c5f67 and 0 for PR HEAD 4820d3e in total

Copy link
Contributor

openshift-ci bot commented May 10, 2024

@adambkaplan: The following test 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-ovn-single-node-upgrade 4820d3e link false /test e2e-aws-ovn-single-node-upgrade

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.

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 4820d3e

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6 High
Undiagnosed panic detected in pod
This test has passed 100.00% of 42 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-metal-ipi-ovn-ipv6' 'periodic-ci-openshift-release-master-nightly-4.16-e2e-metal-ipi-ovn-ipv6'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade High
[sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator
This test has passed 99.26% of 2421 runs on release 4.17 [Overall] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones High
Undiagnosed panic detected in pod
This test has passed 100.00% of 2 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-edge-zones'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-fips IncompleteTests
Tests for this run (99) are below the historical average (2093): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-gcp-ovn-builds Medium
Undiagnosed panic detected in pod
This test has passed 94.74% of 38 runs on release 4.17 [amd64 gcp ha ovn] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-serial Medium
Undiagnosed panic detected in pod
This test has passed 97.73% of 44 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-ci-4.17-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-serial'] in the last 14 days.

@openshift-ci-robot
Copy link

/hold

Revision 4820d3e was retested 3 times: holding

@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 May 10, 2024
@sanchezl
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 62c5f67 and 2 for PR HEAD 4820d3e in total

@openshift-merge-bot openshift-merge-bot bot merged commit a177aa9 into openshift:master May 11, 2024
23 of 24 checks passed
@openshift-ci-robot
Copy link

@adambkaplan: Jira Issue OCPBUGS-33378: All pull requests linked via external trackers have merged:

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

In response to this:

Updating the build suite test to verify the unautenticated build webhook behavior on upgrade. For clusters upgrading from v4.15 or earlier to v4.16, unauthenticated webhooks should continue to be allowed. For clusters that upgrade from v4.16 to a later version, unauthenticated webhooks should be denied by default.

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

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202405111718.p0.ga177aa9.assembly.stream.el9 for distgit openshift-enterprise-tests.
All builds following this will include this PR.

@adambkaplan adambkaplan deleted the unauth-webhook-on-upgrade branch May 13, 2024 15:00
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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants