Bug 1521135

Summary: Storage domains don't get automatically imported/ appear in the storage tab after deployment
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Dave <dfitzpat>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED DUPLICATE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhi-1.1CC: asriram, dfitzpat, rhs-bugs, sasundar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-08 10:30:35 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: 1724792    
Attachments:
Description Flags
Screenshot of the page in question
none
Screenshot of the default volumes the deployment gives the user none

Description Dave 2017-12-05 20:48:30 UTC 
Description of problem:
Storage doesn't get imported automatically even though the defaults for gluster are given to you (and are the recommended way to deploy rh-hi) after going through deployment. 

The document states after Chapter 8's title "It also configures a Default cluster comprised of the three physical machines, and enables Red Hat Gluster Storage functionality and the virtual-host tuned performance profile for each machine in the cluster." 

Reading this as an user would lead me to believe that the storage that was deployed/configured should be shown in the dashboard with no further user input. As it stands now the "data" storage domain never gets imported and the user is never instructed to do so. It should just be in the storage domain without issues or user input. Note: There were issues importing the 'data' storage domain too.


This would lead to a better UX experience and prevent user confusion. Documentation should reflect this as well.


Additional info:
Chaper 8 Documentation:
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure/1.0/html/deploying_red_hat_hyperconverged_infrastructure/deploy-he-cockpit
Section: title paragraph

Chapter 9 Documentation:
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure/1.0/html/deploying_red_hat_hyperconverged_infrastructure/configure-gluster-rhv-manager#create_the_master_storage_domain
Section 9.2
Comment 2 SATHEESARAN 2017-12-06 02:52:55 UTC 
In actual, it configures the cluster with one host.

When we say 'it enables Red Hat Gluster Storage functionality'. It does translate to 'enabling gluster cluster capability on the cluster', which enables the cluster to manage gluster (RHGS) functionality as well.

I too admit with Dave, that this would cause ambiguity. There are high chances that user might expect the Storage Domain also available.

We should add clarity
Comment 3 SATHEESARAN 2017-12-06 02:56:57 UTC 
Dave,

I read comment0 once again, where you said

"Note: There were issues importing the 'data' storage domain too."

You should be creating the first Storage Domain with 'vmstore' volume as described in the doc ( chapter 9.2 in deployment guide )

If that is done, then the hosted-engine storage will be imported automagically.

Let me know, if that doesn't work or doc is not clear to do the same.
Comment 4 Dave 2017-12-06 13:12:59 UTC 
Satheesaran & others,
Correct we followed those steps and only hosted engine was imported when vmstore was added manually. We will be rerunning today to confirm this (Ethel has been down for us).

The bigger question I'll ask is why aren't vmstore, hosted engine, and data automatically pulled into the storage tab (as well as hosts to the hosts tab <-- other bug filed)? The user will be expecting that after they go through deployment that they can hit the ground running and deploy vms right away without having to added storage (and hosts). 


Note: Moved from doc to rhhi component as I believe this should be implemented differently for usability and customer experience.
Comment 6 Dave 2017-12-06 15:45:53 UTC 
Created attachment 1363718 [details]
Screenshot of the page in question
Comment 7 Dave 2017-12-06 15:55:40 UTC 
Created attachment 1363721 [details]
Screenshot of the default volumes the deployment gives the user

These all should be automatically imported to the storage tab post deployment with no user intervention.
Comment 8 Sahina Bose 2017-12-08 10:30:35 UTC 
There's already an RFE to track this in oVirt, which I've cloned now to target for next release - Bug 1523568.

Hence closing this dupe

*** This bug has been marked as a duplicate of bug 1523568 ***