Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1585450

Summary: Unable to perform scaling operation from director UI
Product: Red Hat OpenStack Reporter: MD Sufiyan <msufiyan>
Component: openstack-tripleo-uiAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED DUPLICATE QA Contact: Arik Chernetsky <achernet>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: beth.white, jjoyce, jrist, jschluet, mbarnett, slinaber, tvignaud
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-07 13:41:43 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:
Attachments:
Description Flags
deployment succeeded but there is no option to re-trigger the deployment for update purpose. none

Description MD Sufiyan 2018-06-03 05:15:46 UTC
Created attachment 1447142 [details]
deployment succeeded but there is no option to re-trigger the deployment for update purpose.

Description of problem:

Not able to perform any scaling operation after deploying the cloud using director UI. The only option which is visible is "Delete Deployment"

Plan >> Select Plan >> step 3 ( add the nodes with which you want to scale-up the environment. >> Step 4 "Deploy" ( here no option is available for re-triggering the stack deployment )



Version-Release number of selected component (if applicable):
OSP13 (Beta)
openstack-tripleo-ui-8.3.1-2.el7ost.noarch

How reproducible:
Every time, if you want to perform operation like adding/deleting or replacing a node then there is no option available for redeploying the stack like we use to do via command line. 


Additional info:

Refer the screen shot for same

Comment 2 Jiri Tomasek 2018-08-07 13:41:43 UTC

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