Bug 1398502 - Prompt info is not suitable when scale rc with dc
Summary: Prompt info is not suitable when scale rc with dc
Keywords:
Status: CLOSED DUPLICATE of bug 1398504
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-25 03:33 UTC by Yanping Zhang
Modified: 2017-01-30 19:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-30 19:33:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Yanping Zhang 2016-11-25 03:33:29 UTC
Description of problem:
Now scale a rc with dc is not supported, but when scale a rc with dc, it prompts info that the rc is scaled, in fact it doesn't.

Version-Release number of selected component (if applicable):
oc v3.4.0.29+ca980ba


How reproducible:
Always

Steps to Reproduce:
1.Create rc with dc.
# oc run testdc --image=aosqe/hello-openshift 
deploymentconfig "testdc" created
# oc get pod 
NAME             READY     STATUS      RESTARTS   AGE
testdc-1-pliqq   1/1       Running     0          15s

2.Scale the rc
# oc scale rc/testdc-1 --replicas=2 
replicationcontroller "testdc-1" scaled

3.Check the pod and rc.
# oc get pod
NAME             READY     STATUS      RESTARTS   AGE
testdc-1-pliqq   1/1       Running     0          46s
# oc get rc -n prozyp
NAME       DESIRED   CURRENT   READY     AGE
testdc-1   1         1         1         1m

Actual results:
2. It prompts info that the rc is scaled.
3. The rc is not scaled and pod number is not increased.

Expected results:
2.Should show proper info that the rc can not be scaled.

Additional info:

Comment 1 Juan Vallejo 2017-01-30 19:33:03 UTC
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1398504 closing.

*** This bug has been marked as a duplicate of bug 1398504 ***


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