-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[Feature:DeploymentConfig] deploymentconfigs won't deploy RC with unresolved images [Conformance] when patched with empty image #18982
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
Comments
/cc @bparees |
@simo5 please link the job when reporting flakes. @stevekuznetsov this is either a bad deploymentconfig test case that is creating bad bindings, or something fundamental in cluster setup creating bad bindings. Either way it's master team. |
Another one that failed the same way, also in deploymentconfigs, but not exactly the same test: |
|
seems like an issue w/ the SA creation/permission bindings being performed multiple times? or a race condition in the creation logic? |
The title certainly makes it look suspicious. |
/assign @deads2k |
Automatic merge from submit-queue. Handle role binding AlreadyExists errors on project creation This change correctly allows AlreadyExists errors for the default role bindings during project creation (which is race between the API master and the default role binding controller). However, it does not generically ignore these errors. Signed-off-by: Monis Khan <[email protected]> Fixes #18982 Alternative to #18994 /kind bug /assign @simo5 @deads2k @openshift/sig-master
seeing this in RedHat OCP 3.7 terrible. its on new-project instruction! |
ok after sometime i understood why its happenning. it is still poor that it cannot be dealt since solution is so easy - but it is a kubernetes thing. not openshift :( |
Sound slike a flake:
The text was updated successfully, but these errors were encountered: