Bug 1314518 - Duplicate messages in oc get pod -w when deleting a dc
Summary: Duplicate messages in oc get pod -w when deleting a dc
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 19:59 UTC by Mike Fiedler
Modified: 2019-08-21 08:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-21 08:33:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Fiedler 2016-03-03 19:59:16 UTC
Description of problem:

Duplicate messages appear in oc get pod --show-all=false -w when deleting a dc.  Kind of a nit, but having to account for it in some automation.


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Create an application from the django-ex template
2. oc get pod -w to verify it builds/deploys/runs
3. In a separate shell session oc delete dc/django-example

Actual results:

test1     django-example-2-ec80m   1/1       Terminating   0         25m
test1     django-example-2-ec80m   1/1       Terminating   0         25m
test1     django-example-2-ec80m   0/1       Terminating   0         25m
test1     django-example-2-ec80m   0/1       Terminating   0         25m


Expected results:

2 lines of output - one for the start of termination and one for the completion.

kubectl get events --show-all=false -w for the same operation shows:

test1     2016-03-03 14:55:20 -0500 EST   2016-03-03 14:55:20 -0500 EST   1         django-example-2   ReplicationController             Normal    SuccessfulDelete   {replication-controller }   Deleted pod: django-example-2-ec80m

test1     2016-03-03 14:55:21 -0500 EST   2016-03-03 14:55:21 -0500 EST   1         django-example-2-ec80m   Pod       spec.containers{django-example}   Normal    Killing   {kubelet ip-172-31-45-250.us-west-2.compute.internal}   Killing container with docker id e38e37493ba3: Need to kill pod.


Additional info:

Comment 1 Maciej Szulik 2019-08-21 08:33:40 UTC
Closing due to age.


Note You need to log in before you can comment on or make changes to this bug.