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

TestAuthorizationRestrictedAccessForProjectAdmins flake #6173

Closed
0xmichalis opened this issue Dec 2, 2015 · 4 comments
Closed

TestAuthorizationRestrictedAccessForProjectAdmins flake #6173

0xmichalis opened this issue Dec 2, 2015 · 4 comments
Assignees
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2

Comments

@0xmichalis
Copy link
Contributor

--- FAIL: TestAuthorizationRestrictedAccessForProjectAdmins-4 (14.12s)
    authorization_test.go:45: unexpected error: policybinding ":default" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
FAIL

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/7608/consoleFull

@rhcarvalho
Copy link
Contributor

@danmcp danmcp added the kind/test-flake Categorizes issue or PR as related to test flakes. label Dec 4, 2015
@bparees
Copy link
Contributor

bparees commented Dec 17, 2015

I1216 23:46:18.431236   18818 create_dockercfg_secrets.go:163] View of ServiceAccount openshift/deployer is not up to date, skipping dockercfg creation
Could not add service accounts to the system:deployer role: policybinding ":default" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
--- FAIL: TestAuthorizationRestrictedAccessForProjectAdmins-4 (15.18s)
    authorization_test.go:45: unexpected error: policybinding ":default" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
FAIL

https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/4374/console

@liggitt
Copy link
Contributor

liggitt commented Dec 20, 2015

likely the same issue as #6065 (comment), still trying to figure out how we appear to have multiple etcd writers

@liggitt
Copy link
Contributor

liggitt commented Dec 22, 2015

Same cause as #6065 (failed etcd update). The issue is not specific to a test, it's a response to an etcd server error that is seen about 30-60 seconds into the integration tests. If a client request is in progress when that server error is received, the client gets a 500 error, and reacts by retrying the request. If the request is one that would fail on a retry (like a delete or a conditional update), the test fails.

@liggitt liggitt closed this as completed Dec 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2
Projects
None yet
Development

No branches or pull requests

6 participants