Bug 1421276 - [API] Fusor API allows the deployment name to be edited after deployment starts
Summary: [API] Fusor API allows the deployment name to be edited after deployment starts
Keywords:
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-server
Version: 1.1
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Sudhir Mallamprabhakara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-10 20:05 UTC by Landon LaSmith
Modified: 2017-02-10 20:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Landon LaSmith 2017-02-10 20:05:14 UTC 
Description of problem: After a deployment is started, the deployment name can be edited which will split the logs across separate root directories. The same functionality is disabled in the webui

QCI Media Version: QCI-1.1-RHEL-7-20170209.t.1

How reproducible: 100%

Steps to Reproduce:
1. Install QCI from iso
2. Create any type of deployment
3. Start the deployment
4. Attempt to change the name of the deployment using the fusor rest api

PUT https://<fusor ip>/fusor/api/v21/deployments/<deployment id>
json: {'deployment':{'name', 'newdeploymentname'}}

Actual results: Request returns HTTP 200 and a newdeploymentname folder is created in the foreman directory on satellite (/var/log/foreman/deployments/<newdeploymentname>-<deployment id>

Expected results: Request returns a 400 error and the deployment name change is not allowed
Note You need to log in before you can comment on or make changes to this bug.