Created attachment 1161373 [details] storage profile list Description of problem: A new storage profile created during cluster creation is not displayed in 'Storage Profile:' drop down list on host OSDs tab. Version-Release number of selected component (if applicable): rhscon-core-0.0.19-1.el7scon.x86_64 rhscon-ceph-0.0.18-1.el7scon.x86_64 rhscon-ui-0.0.34-1.el7scon.noarch How reproducible: 100% Steps to Reproduce: 1. Create some cluster, during that create a new storage profile, add some OSDs to the new profile 2. Open the OSDs page for some host which is part of the cluster 3. Check the 'Storage Profile:' drop down list Actual results: A newly created storage profile is not part of the list Expected results: All storage profiles are listed there, or at least those related with OSDs on the host. Additional info:
Does this storage profile successfully created in the backend? Can I have access to the system where this can be reproduced?
(In reply to Nishanth Thomas from comment #1) > Does this storage profile successfully created in the backend? Can I have > access to the system where this can be reproduced? The new profile is listed correctly on backend.
Need retest with latest build and publish the results
Re-test on rhscon-core-selinux-0.0.26-1.el7scon.noarch rhscon-ui-0.0.41-1.el7scon.noarch rhscon-core-0.0.26-1.el7scon.x86_64 rhscon-ceph-0.0.26-1.el7scon.x86_64 still valid
Tested on: rhscon-core-0.0.38-1.el7scon.x86_64 rhscon-ceph-0.0.38-1.el7scon.x86_64 rhscon-core-selinux-0.0.38-1.el7scon.noarch rhscon-ui-0.0.51-1.el7scon.noarch I still cannot see any storage profile defined by user in the drop down list on Host - OSDs tab.
Created attachment 1187099 [details] host OSDs tab user defined test1 profile is missing in the drop down list
Tested with ceph-ansible-1.0.5-32.el7scon.noarch ceph-installer-1.0.14-1.el7scon.noarch rhscon-ceph-0.0.40-1.el7scon.x86_64 rhscon-core-0.0.41-1.el7scon.x86_64 rhscon-core-selinux-0.0.41-1.el7scon.noarch rhscon-ui-0.0.52-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