Bug 1341655

Summary: pool cannot be updated
Product: [Red Hat Storage] Red Hat Storage Console Reporter: Lubos Trilety <ltrilety>
Component: UIAssignee: Karnan <kchidamb>
Status: CLOSED ERRATA QA Contact: Martin Kudlej <mkudlej>
Severity: unspecified Docs Contact:
Priority: high    
Version: 2CC: mkudlej, nthomas, sankarshan, shtripat, vsarmila
Target Milestone: ---   
Target Release: 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhscon-ceph-0.0.29-1.el7scon Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:53:25 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: 1344192, 1344195    

Description Lubos Trilety 2016-06-01 12:31:21 UTC
Description of problem:
Pool edit always fails. Moreover a task with poll update is not displayed properly. The icon with tasks doesn't show that a new task was created and user is not notified about the task result.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.21-1.el7scon.x86_64
rhscon-ceph-0.0.20-1.el7scon.x86_64
rhscon-ui-0.0.34-1.el7scon.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create some pool
2. Open Pools page, click on Edit action for the pool
3. Make some changes and try to save them

Actual results:
Nothing seems to happen even the edit sub-menu is not closed, but there's a new failed task in tasks list.

Expected results:
Update should succeeded and user should be notified about that.

Additional info:

Comment 2 Martin Kudlej 2016-07-08 11:28:46 UTC
Tested with:
ceph-ansible-1.0.5-23.el7scon.noarch
ceph-installer-1.0.12-3.el7scon.noarch
rhscon-ceph-0.0.29-1.el7scon.x86_64
rhscon-core-0.0.29-1.el7scon.x86_64
rhscon-core-selinux-0.0.29-1.el7scon.noarch
rhscon-ui-0.0.43-1.el7scon.noarch
and it works. --> Verified

Comment 4 errata-xmlrpc 2016-08-23 19:53:25 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