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

Extended.deploymentconfigs with custom deployments [Conformance] should run the custom deployment steps #16023

Closed
bparees opened this issue Aug 28, 2017 · 10 comments
Assignees
Labels
component/containers kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@bparees
Copy link
Contributor

bparees commented Aug 28, 2017

/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:518
Expected error:
    <*errors.errorString | 0xc420ec3710>: {
        s: "deployment failed: config change",
    }
    deployment failed: config change
not to have occurred
/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:499

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/4987/

@bparees bparees added priority/P1 kind/test-flake Categorizes issue or PR as related to test flakes. component/apps labels Aug 28, 2017
@mfojtik mfojtik assigned tnozicka and unassigned mfojtik Aug 29, 2017
@tnozicka
Copy link
Contributor

Deployer pod failed because of infra:

containerStatuses:
  - containerID: docker://14c467bf179ec92bbb8294b364b9c516ca13f9a263cd5941af900878d7c6bf22
    image: openshift/origin-deployer:8453380
    imageID: docker://sha256:7abe0813c18a9d874d13d00201eb5c51e09f2ef23a72c249cbe3ad1fa8e18188
    lastState: {}
    name: deployment
    ready: false
    restartCount: 0
    state:
      terminated:
        containerID: docker://14c467bf179ec92bbb8294b364b9c516ca13f9a263cd5941af900878d7c6bf22
        exitCode: 128
        finishedAt: 2017-08-28T21:33:38Z
        message: 'invalid header field value "oci runtime error: container_linux.go:247:
          starting container process caused \"process_linux.go:258: applying cgroup
          configuration for process caused \\\"write /sys/fs/cgroup/pids/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod8cd1564c_8c38_11e7_8d0a_0e359e0baf04.slice/docker-14c467bf179ec92bbb8294b364b9c516ca13f9a263cd5941af900878d7c6bf22.scope/cgroup.procs:
          no such device\\\"\"\n"'
        reason: ContainerCannotRun
        startedAt: 2017-08-28T21:33:38Z

@mfojtik
Copy link
Contributor

mfojtik commented Aug 29, 2017

@sjenning PTAL

@sjenning
Copy link
Contributor

/sys/fs/cgroup/pids/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod8cd1564c_8c38_11e7_8d0a_0e359e0baf04.slice/docker-14c467bf179ec92bbb8294b364b9c516ca13f9a263cd5941af900878d7c6bf22.scope

Where would "pids" come from in this path? @derekwaynecarr any idea?

@sjenning
Copy link
Contributor

I can't find node logs for any of the occurrences. They seem to have been deleted.

@0xmichalis
Copy link
Contributor

@sjenning
Copy link
Contributor

sjenning commented Sep 15, 2017

@Kargakis that doesn't appear to be an occurence of this issue, characterized by deployment failed: config change and pids in the cgroup path. 7546 seems to be just a timeout.

@sjenning
Copy link
Contributor

@bparees I went looking through extended_conformance_gce failures for the past few days and can't find an occurrence. Please let me know if you see another so I can get the node logs before they disappear.

@sjenning
Copy link
Contributor

dup of #16246

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

No branches or pull requests

5 participants