Description of problem:
The hosted_storage is currently acts as a regular storage domain in a HE environment except the fact it cannot be removed because of the 'HostedEngine' VM.
This storage domain shouldn't be as regular data storage domain, but a system data domain
* This proposed solution might be good fix for bug #1309150
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Might be also a good solution for bug #1315074
Are we considering this? Is this a real solution for any bugs?
I think the intention of this bug is to have distinction between data domains to the data domain of the hosted engine. Not a bad idea by itself and might help clarify desgined behaviours like mentioned in Bug 1315074. BUT, implementation wise I'm not considering changing the underlying data type and introduce another one. This is risky and opened the door to lots of bugs and corner cases I believe.
The bug should really express the desired behaviour, and not what the implementation should be. Raz can you please change the subject to better express that? (and maybe chat with ydary on it before hand)
Changed it, let me know what you think.
We have decided in the recent discussion on this subject we will aim to make the HE storage domain similar as much as possible to any other storage domain. We wan to validate this doesn't have major issues and request you try to use this storage domain as SPM and a VM disk store.
If stress testing is done, please configure SLA since we don't expect users to do such things without this and we will warn to not stress this storage in the docs.
*** Bug 1309150 has been marked as a duplicate of this bug. ***
Currently, this  bug is delays our testing
Changing the summary to a correct one
Re-open this bug because bug https://bugzilla.redhat.com/show_bug.cgi?id=1397189
(In reply to Raz Tamir from comment #9)
> Re-open this bug because bug
That bug was closed - move back to ON_QA.
I'm still having issue with this "bug".
The summery is outdated and there are many bugs revealed lately related to HE storage domain that basically caused this bug to 'FailedQA' everytime