Bug 1319817

Summary: Create object storage summary
Product: [Red Hat Storage] Red Hat Storage Console Reporter: Lubos Trilety <ltrilety>
Component: UIAssignee: Karnan <kchidamb>
Status: CLOSED ERRATA QA Contact: Lubos Trilety <ltrilety>
Severity: low Docs Contact:
Priority: medium    
Version: 2CC: mkudlej, nthomas, sankarshan, vsarmila
Target Milestone: ---   
Target Release: 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhscon-core-0.0.34-1.el7scon.x86_64 rhscon-ceph-0.0.33-1.el7scon.x86_64 rhscon-ui-0.0.47-1.el7scon.noarch Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:48:47 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:
Bug Depends On:    
Bug Blocks: 1344195    

Description Lubos Trilety 2016-03-21 15:20:36 UTC
Description of problem:
In object storage summary the pool name always starts with capital, even if it's not true.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.8-14.el7.x86_64
rhscon-ui-0.0.23-1.el7.noarch
rhscon-ceph-0.0.6-14.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start with pool creation, type some name starting with lower case letter
2. Fill all required information and click on next
3. Check summary page

Actual results:
The name starts with capital instead of lower case. However created pool has correct name with lower case initial.

Expected results:
The name is correct, the same as it was provided.

Additional info:

Comment 4 Lubos Trilety 2016-07-21 11:52:52 UTC
Tested on:
rhscon-ceph-0.0.33-1.el7scon.x86_64
rhscon-core-selinux-0.0.34-1.el7scon.noarch
rhscon-core-0.0.34-1.el7scon.x86_64
rhscon-ui-0.0.48-1.el7scon.noarch

correct name was displayed on the summary page

Comment 6 errata-xmlrpc 2016-08-23 19:48:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2016:1754