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

[Feature:DeploymentConfig] deploymentconfigs with failing hook [Conformance] should get all logs from retried hooks #18045

Closed
sosiouxme opened this issue Jan 10, 2018 · 6 comments
Assignees
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2 sig/pod

Comments

@sosiouxme
Copy link
Member

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17773/test_pull_request_origin_extended_conformance_gce/13954/ looks like it occurs in the same place as some earlier closed issues but for different reason. Hopefully not a dupe:


Command: go run hack/e2e.go -v -test --test_args='--ginkgo.focus=\[Feature\:DeploymentConfig\]\sdeploymentconfigs\swith\sfailing\shook\s\[Conformance\]\sshould\sget\sall\slogs\sfrom\sretried\shooks\s\[Suite\:openshift\/conformance\/parallel\]$'

/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:757
Expected error:
    <*util.ExitError | 0xc4214a3710>: {
        Cmd: "oc logs --config=/tmp/extended-test-cli-deployment-mkx97-9f4dz-user.kubeconfig --namespace=extended-test-cli-deployment-mkx97-9f4dz deploymentconfig/hook",
        StdErr: "Error from server: Get https://ci-prtest-5a37c28-13954-ig-n-3r64:10250/containerLogs/extended-test-cli-deployment-mkx97-9f4dz/hook-1-deploy/deployment: dial tcp 10.142.0.3:10250: getsockopt: connection refused",
        ExitError: {
            ProcessState: {
                pid: 29364,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 339109},
                    Stime: {Sec: 0, Usec: 67340},
                    Maxrss: 64360,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 16124,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 0,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 1692,
                    Nivcsw: 12,
                },
            },
            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/deployments/deployments.go:764
@sosiouxme sosiouxme added the kind/test-flake Categorizes issue or PR as related to test flakes. label Jan 10, 2018
@mfojtik
Copy link
Contributor

mfojtik commented Jan 11, 2018

@sjenning seems like getting logs from the node is broken here

@tnozicka
Copy link
Contributor

similar issue with logs from today #18061

@sjenning
Copy link
Contributor

@vikaschoudhary16 PTAL

@sjenning sjenning removed their assignment Jan 22, 2018
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 23, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2 sig/pod
Projects
None yet
Development

No branches or pull requests

7 participants