Bug 1404339

Summary:	Adding new cloud volume size should be required in form
Product:	Red Hat CloudForms Management Engine	Reporter:	Matouš Mojžíš <mmojzis>
Component:	UI - OPS	Assignee:	Marek Aufart <maufart>
Status:	CLOSED WONTFIX	QA Contact:	Matouš Mojžíš <mmojzis>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	hkataria, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ui:cloud
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:

Description Matouš Mojžíš 2016-12-13 15:57:08 UTC

Description of problem:


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

How reproducible:
Always

Steps to Reproduce:
1. Go to Storage -> Volumes
2. Add a new volume
3. Fill name and tenant in (everything except size)

Actual results:
I can click on Add

Expected results:
Size should be required as name and tenant and without size filled in Add should be disabled, because I get error after add that size is required.

Additional info:

Comment 3 Josh Carter 2018-10-02 14:33:09 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 4 Josh Carter 2018-10-02 14:33:56 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 5 Josh Carter 2018-10-02 14:35:21 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!