Skip to content

Conversation

@liouk
Copy link
Member

@liouk liouk commented Sep 13, 2023

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 13, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 13, 2023

@liouk: This pull request references AUTH-428 which is a valid jira issue.

In response to this:

Adds e2e tests for the behavior added here:

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/test-infra repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 13, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 13, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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

@liouk liouk force-pushed the psalabelsyncer-managed-labels branch 3 times, most recently from cb80df0 to 49d0add Compare September 13, 2023 14:56
@liouk liouk force-pushed the psalabelsyncer-managed-labels branch from 49d0add to 776c4bb Compare September 21, 2023 10:07
@liouk liouk changed the title WIP: AUTH-428: add PSa labelsyncer managed labels e2e tests AUTH-428: add PSa labelsyncer managed labels e2e tests Sep 21, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 21, 2023
@liouk
Copy link
Member Author

liouk commented Sep 21, 2023

/retest

@liouk
Copy link
Member Author

liouk commented Sep 25, 2023

/retest-required

}

func waitAndGetNamespace(ctx context.Context, oc *exutil.CLI, nsName string) (*corev1.Namespace, error) {
time.Sleep(2 * time.Second)
Copy link
Contributor

Choose a reason for hiding this comment

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

Wait until something happens is always better.

A hardcoded timelimit is always the worst case. It can also introduce a spiral of longer and longer test durations. If the cluster is slow, it will cause flakiness, which will then lead to an increase of the static sleep in all cases.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've added a generic polling function that waits for the namespace object to be updated by the labelsyncer after the original create/update, in 9418921.

I chose a generic equality condition, as what the labelsyncer is expected to do varies per test and test case (and in some cases no change is expected at all).

Copy link
Contributor

@ibihim ibihim Jan 25, 2024

Choose a reason for hiding this comment

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

A polling function is a great idea.

Test frameworks that offer a "wait" function are doing exactly that.

@liouk
Copy link
Member Author

liouk commented Oct 18, 2023

added review fixes as fixups for clarity; will squash once reviewed
/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 Oct 18, 2023
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 17, 2024
@liouk
Copy link
Member Author

liouk commented Jan 24, 2024

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 24, 2024
@liouk
Copy link
Member Author

liouk commented Jan 25, 2024

/retest

@liouk liouk force-pushed the psalabelsyncer-managed-labels branch from 9418921 to 2649633 Compare January 25, 2024 12:31
@liouk
Copy link
Member Author

liouk commented Jan 30, 2024

/retest

@liouk liouk force-pushed the psalabelsyncer-managed-labels branch from 2649633 to b0021c5 Compare January 31, 2024 10:34
@liouk
Copy link
Member Author

liouk commented Jan 31, 2024

/hold cancel
all fixups squashed

@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 Jan 31, 2024
@liouk
Copy link
Member Author

liouk commented Feb 8, 2024

/retest

@liouk
Copy link
Member Author

liouk commented Feb 8, 2024

/hold
test is failing

@liouk liouk force-pushed the psalabelsyncer-managed-labels branch from 20e5af0 to 5486b12 Compare February 8, 2024 14:54
@liouk liouk force-pushed the psalabelsyncer-managed-labels branch from 5486b12 to ea0c6cd Compare February 9, 2024 10:12
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 4, 2024
@liouk
Copy link
Member Author

liouk commented Jun 4, 2024

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 4, 2024
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 3, 2024
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 1, 2024
@liouk
Copy link
Member Author

liouk commented Nov 1, 2024

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 1, 2024
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2025
@liouk
Copy link
Member Author

liouk commented Jan 30, 2025

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2025
@openshift-trt
Copy link

openshift-trt bot commented Feb 28, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: ea0c6cd

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-gcp-ovn High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-gcp-ovn High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-vsphere-ovn High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-main-e2e-vsphere-ovn High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-master-e2e-vsphere-ovn High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit
pull-ci-openshift-origin-master-e2e-vsphere-ovn High - "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" is a new test that failed 1 time(s) against the current commit

New tests seen in this PR at sha: ea0c6cd

  • "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer] updating PSa labels [Suite:openshift/conformance/parallel]" [Total: 6, Pass: 0, Fail: 6, Flake: 0]
  • "[sig-auth][Feature:PodSecurity][Feature:LabelSyncer][Feature:ForceHistoricalOwnership] forcing PSa label historical ownership [Suite:openshift/conformance/parallel]" [Total: 6, Pass: 0, Fail: 6, Flake: 0]

@openshift-trt openshift-trt bot deleted a comment from openshift-trt-bot Feb 28, 2025
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 2, 2025
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 1, 2025
@liouk
Copy link
Member Author

liouk commented Sep 2, 2025

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 2, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 3, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@liouk: 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-ovn-fips ea0c6cd link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-cgroupsv2 ea0c6cd link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-gcp-ovn ea0c6cd link true /test e2e-gcp-ovn
ci/prow/e2e-openstack-ovn ea0c6cd link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade ea0c6cd link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node ea0c6cd link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial ea0c6cd link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-sdn ea0c6cd link false /test e2e-metal-ipi-sdn
ci/prow/e2e-gcp-ovn-builds ea0c6cd link true /test e2e-gcp-ovn-builds
ci/prow/e2e-vsphere-ovn-upi ea0c6cd link true /test e2e-vsphere-ovn-upi
ci/prow/e2e-vsphere-ovn ea0c6cd link true /test e2e-vsphere-ovn
ci/prow/e2e-aws-csi ea0c6cd link true /test e2e-aws-csi
ci/prow/e2e-gcp-csi ea0c6cd link true /test e2e-gcp-csi
ci/prow/go-verify-deps ea0c6cd link true /test go-verify-deps
ci/prow/e2e-aws-ovn-microshift ea0c6cd link true /test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-microshift-serial ea0c6cd link true /test e2e-aws-ovn-microshift-serial
ci/prow/e2e-metal-ipi-ovn-ipv6 ea0c6cd link true /test e2e-metal-ipi-ovn-ipv6

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.

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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants