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
Bug 1820687: NS SCC annotations exist, else forbidden: unable to validate... #24828
Bug 1820687: NS SCC annotations exist, else forbidden: unable to validate... #24828
Conversation
@gabemontero: This pull request references Bugzilla bug 1820687, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
@gabemontero: This pull request references Bugzilla bug 1820687, which is valid. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
/test e2e-gcp-image-ecosystem |
/hold given the flake level of this @adambkaplan I am going to run a series of image ecos here to try and validate but please feel free to approve/lgtm in the interim |
initial image eco run good, along with a couple of other e2e suites /test unit |
Hah ... I didn't think the k8s 1.18 rebase landed anywhere in origin, but cmd/images are failing with
I'll rebase my branch ... perhaps something just merged. |
sure enough ... that was it ... rebase will be pushed momentarily |
4fa7746
to
3252a71
Compare
/retest |
/test e2e-cmd |
/test e2e-gcp-image-ecosystem |
have all green tests .... re-runnig image eco a bunch of times |
/test e2e-gcp-image-ecosystem |
So a promising sign, in the last run, there were a series of type errors in the cluster-policy-controller at the same time the SCL enabled Pod launch tests were going on, and we got no forbidden errors. I'm also seeing some test duration times that are a minute or two longer (even across the same language stack) that could indicate a wait/retry cycle waiting on the SCC annotations. |
Similar finding to #24828 (comment) in last run. Again encouraging. /test e2e-gcp-image-ecosystem |
@gabemontero to me this implies there is a product bug in the |
Don't necessarily share that opinion @adambkaplan and so no I've not opened a separate BZ at this time. I debated some changes to cluster-policy-controller in my original debug PR, but in the end I don't think they would amount to much. |
/test e2e-gcp-image-ecosystem |
2 similar comments
/test e2e-gcp-image-ecosystem |
/test e2e-gcp-image-ecosystem |
3252a71
to
84716d3
Compare
update for #24828 (comment) and #24828 (comment) pushed @adambkaplan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gabemontero comment nit, otherwise looks good.
2e58789
to
d82f949
Compare
suggestion accepted @adambkaplan commits squashed /hold cancel tag at your convenience - thanks !! |
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan, gabemontero 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
@gabemontero: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:
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 kubernetes/test-infra repository. |
/cherry-pick release-4.4 |
@soltysh: #24828 failed to apply on top of branch "release-4.4":
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 kubernetes/test-infra repository. |
Stems from debug in #24703
@openshift/openshift-team-developer-experience FYI
/assign @adambkaplan
(appears is in a sufficient OWNERS file)