Skip to content

Test flake: [Conformance] Ensure supplemental groups propagate to docker should propagate requested groups to the container #17359

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

Closed
sosiouxme opened this issue Nov 17, 2017 · 6 comments
Assignees
Labels
component/auth kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@sosiouxme
Copy link
Member

openshift/openshift-ansible#6150
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_openshift-ansible/6150/test_pull_request_openshift_ansible_extended_conformance_install/2386/

/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/security/supplemental_groups.go:72
Expected error:
    <*util.ExitError | 0xc420bb3530>: {
        Cmd: "oc adm --config=/etc/origin/master/admin.kubeconfig --namespace=extended-test-sup-groups-2dc4n-gfckg policy add-scc-to-user anyuid extended-test-sup-groups-2dc4n-gfckg-user",
        StdErr: "Error from server (Conflict): Operation cannot be fulfilled on securitycontextconstraints.security.openshift.io \"anyuid\": the object has been modified; please apply your changes to the latest version and try again",
        ExitError: {
            ProcessState: {
                pid: 7911,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 250029},
                    Stime: {Sec: 0, Usec: 35569},
                    Maxrss: 51860,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 13562,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 0,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 785,
                    Nivcsw: 283,
                },
            },
            Stderr: nil,
        },
    }
    exit status 1
not to have occurred
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/security/supplemental_groups.go:36
@simo5
Copy link
Contributor

simo5 commented Nov 21, 2017

/assign @adelton

@adelton
Copy link
Contributor

adelton commented Nov 22, 2017

@runcom, since you've been changing https://github.com/openshift/origin/blob/master/test/extended/security/supplemental_groups.go#L36 most recently, any idea from the top of your head what might be causing the error?

@enj
Copy link
Contributor

enj commented Nov 27, 2017

Looks like multiple calls are trying to mutate the same SCC object without doing conflict backoffs?

@runcom
Copy link
Member

runcom commented Nov 27, 2017

I basically need a way to exec in a pod and found that doing that (from another test) works. If this is causing issues, does anybody know how to achieve the same w/o playing with adm and scc?

@adelton
Copy link
Contributor

adelton commented Nov 29, 2017

@enj, have you got some example how similar situation got handled elsewhere?

openshift-merge-robot added a commit that referenced this issue Dec 7, 2017
Automatic merge from submit-queue (batch tested with PRs 17429, 17654, 17580).

Address oc adm conflict.

Resolve:
Error from server (Conflict): Operation cannot be fulfilled on securitycontextconstraints.security.openshift.io \"anyuid\": the object has been modified; please apply your changes to the latest version and try again

Fixes #17359.
@adelton
Copy link
Contributor

adelton commented Dec 18, 2017

By the way, how does one find out if the fix merged via #17580 actually addressed the fluke? Is there some statistics available?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/auth kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1
Projects
None yet
Development

No branches or pull requests

6 participants