Hide Forgot
Description of problem: When running a self hosted engine in RHV4 the storage domain, hosted engine is running on, is selectable also for other VMs to serve as SD which should - at least to my understanding - not be possible as this is error prone and leads to trouble since this could fill up the hosted engine storage domain which leads to engine hanging and being fenced or get frozen. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create new disk for VM 2. select hosted storage as storage pool 3. goto 1. 4. see how self hosted storage becomes filled and finally bring engine to become frozen Actual results: - hosted engine becomes frozen in case hosted storage is filled with disks from other VMs Expected results: hosted storage should not be selectable as SD for other VMs Additional info: also see https://bugzilla.redhat.com/show_bug.cgi?id=1320126 which should also not be possible
As long as the admin is aware of his choices (keeps enough space and proper SLA for the manager) there is no known issues with using the hosted engine storage for VMs. We are not planning to block this. Therefore closing.