Bug 1577334
Summary: | oc run panic: .../vendor/k8s.io/kubernetes/pkg/kubectl/cmd.RunRun | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Chris Evich <cevich> |
Component: | Node | Assignee: | Seth Jennings <sjenning> |
Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas, wmeng |
Target Milestone: | --- | ||
Target Release: | 3.10.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-30 19:15:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Evich
2018-05-11 18:19:12 UTC
Fixed here upstream: https://github.com/kubernetes/kubernetes/pull/61713 Bug introduced by PR in 1.10: https://github.com/kubernetes/kubernetes/commit/6dfe3cb04f4230b38cd51742435cf9203253a34d Thus GAed versions of OCP are not effected. Origin PR: https://github.com/openshift/origin/pull/19693 Reproduced with oc v3.10.0-0.27.0 with steps: $ oc run --image=alpine hello -- sleep 1d deploymentconfig "hello" created $ oc run --image=alpine --stdin --tty --attach hello -- /bin/sh panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x17ebd26] ... Verified with v3.10.0-0.46.0: $ oc run --image=alpine hello -- sleep 1d deploymentconfig "hello" created $ oc run --image=alpine --stdin --tty --attach hello -- /bin/sh Error from server (AlreadyExists): deploymentconfigs.apps.openshift.io "hello" already exists Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1816 |