Description of problem: During RBD creation it's possible to choose EC pool as the one on which the rados block device will be. It will fail because ceph does not support this. However UI should not offer creating RBD on EC pool at all. Version-Release number of selected component (if applicable): rhscon-ui-0.0.34-1.el7scon.noarch rhscon-ceph-0.0.20-1.el7scon.x86_64 rhscon-core-0.0.21-1.el7scon.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create some EC pool 2. Try to create rados block device Actual results: It's possible to choose created EC pool as the one on which the RBD should be. Moreover if an option about creating a new pool is checked, it's possible to choose that an EC pool should be created. Expected results: RBD creation should not offer any EC pool. Additional info:
Looks like this is a matter of not exposing pools that are erasure coded in the existing pools selection, and only showing the standard/replicated pools.
Created attachment 1174054 [details] screenshot of "Add Block Storage" page Checking with: ~~~ # rpm -qa rhscon* rhscon-ui-0.0.42-1.el7scon.noarch rhscon-core-0.0.28-1.el7scon.x86_64 rhscon-ceph-0.0.27-1.el7scon.x86_64 rhscon-core-selinux-0.0.28-1.el7scon.noarch ~~~ And I see that Erasure Coded type is still available in "Add Block Storage" wizard when one selects "Create new pool". => MODIFIED
grep 's/MODIFIED/ASSIGNED/' comment 2 Setting this BZ back into ASSIGNED state based on verification fail as explained in comment 2.
Testing with: rhscon-ui-0.0.48-1.el7scon.noarch I see no change compared to rhscon-ui-0.0.42-1.el7scon.noarch (as described in comment 2): I can still select EC pool with "Create new pool" RBD option. Moving back to MODIFIED
ah, grep 's/MODIFIED/ASSIGNED/' (again)
Tested with ceph-ansible-1.0.5-31.el7scon.noarch ceph-installer-1.0.14-1.el7scon.noarch rhscon-ceph-0.0.39-1.el7scon.x86_64 rhscon-core-0.0.39-1.el7scon.x86_64 rhscon-core-selinux-0.0.39-1.el7scon.noarch rhscon-ui-0.0.51-1.el7scon.noarch and it works.
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