Bug 1095382
| Summary: | [RHEVH] Unable to define custom path for data domain and unable to create ISO domain on Local DC host | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Beňas <pbenas> | ||||
| Component: | vdsm | Assignee: | Maor <mlipchuk> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Aharon Canan <acanan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.4.0 | CC: | acanan, amureini, bazulay, ecohen, fdeutsch, gklein, jbelka, juwu, lpeer, lsurette, mlipchuk, pstehlik, rbalakri, Rhev-m-bugs, scohen, tnisan, ycui, yeylon, ylavi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-10-22 08:25:04 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
It seems problem is with RHEVH, not RHEVM version. It works with RHEL on RHEVM 3.4, but it does not work with RHEVH on RHEVM 3.4. pbenas@ said he was using RHEVH when he faced this issue. So the problem is: * when using RHEVH it can be add as Local storage host * in 'Configure Local Storage' dialog, the path is pre-edited (gray), cannot be changed but the dialog itself can be confirmed with 'OK' button * the master Local storage domain would be successfully created * it's impossible to create any other domain on Local DC/Cluster/Host. this is design flaw, one needs usually ISO domain for his VMs. (I think this is because RHEVH image is "read-only", and /data is separate LV. # mount /dev/mapper/live-rw on / type ext2 (ro,noatime) /dev/mapper/HostVG-Config on /config type ext4 (rw,noatime) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /data/images on /var/lib/libvirt/images type none (rw,bind) /data/core on /var/log/core type none (rw,bind) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) # lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert Config HostVG -wi-ao---- 8.00m Data HostVG -wi-ao---- 222.27g Logging HostVG -wi-ao---- 2.00g Swap HostVG -wi-ao---- 7.83g Great obsfucation! # df -h /data Filesystem Size Used Avail Use% Mounted on /data/core 219G 190M 208G 1% /var/log/core I'm changing to 3.4 as it would need to be solved in 3.4/3.5 first before backporting. Steps to reproduce: 1. rhevh host 2. local dc/cluster 3. rhevh in maintenance -> configure local storage - define custom path for data domain 4. try to add iso domain 5. try to ad another data domain Now: 3. impossible, pre-defined 4. 'Create operation failed. Domain dell-r210ii-03-Local already exists in the system.' error in 'New domain dialog' 5. 'Create operation failed. Domain dell-r210ii-03-Local already exists in the system.' error in 'New domain dialog' What we would like: 3. to be able to define custom path (nitpickers) 4. to be able to define and create iso domain on local host 5. having multiple data domains on local host can be handy, more important VMs on SSD disks, test/dev VMs on HDDs for example I wonder if this is more a problem in the storage part of vdsm, what do you think Alon? (In reply to Fabian Deutsch from comment #5) > I wonder if this is more a problem in the storage part of vdsm, what do you > think Alon? I'm trying to make sense of these line: (In reply to Jiri Belka from comment #3) > Steps to reproduce: > > 1. rhevh host > 2. local dc/cluster > 3. rhevh in maintenance -> configure local storage - define custom path for > data domain > Now: > > 3. impossible, pre-defined A "plain" VDSM would allow you to configure the local storage's path. Jiri - Where is this blocked? in the GUI? Does it produce an error when you try? UI does block it, the field is gray as it is visible in screenshot. Hi Maor, This bug has been flagged for release notes. Please select the correct Doc Type and provide the doc text ASAP for this bugs to make it in the 3.5 Beta Manager Release Notes. Please set the require_release_note flag to - if no doc text is required. Cheers, Julie Re-targeting for 3.6 It is intended that you can not set a custom storage path on RHEV-H. The paths for the local storage domain are predefined in the RHEV-H case, so there should be no need to change. Using the supported ways (using the RHEV-H TUI) it's not even possible to make a different part writable on RHEV-H, thus it does not make sense to set the local storage path to anything else then the predefined path. Please reopen if you think that this should be possible. I don't think such scenario should be possible, but there's still room for improvement. It confused two QE engineers so I think it might confuse a customer as well. In this case, when there's only one rhev-h host in the setup with local master storage domain, it shouldn't be possible to attempt to create another local storage domain on the host. Ideally by disabling the possibility to select the local storage type from the selectbox. Exactly, if it is not possible on RHEVH side, it should be disabled on RHEVM side. (In reply to Julie from comment #8) > Hi Maor, > This bug has been flagged for release notes. Please select the correct Doc > Type and provide the doc text ASAP for this bugs to make it in the 3.5 Beta > Manager Release Notes. Please set the require_release_note flag to - if no > doc text is required. > > Cheers, > Julie Still consolidate the correct solution, I'm not sure yet if the solution should be on RHEV-H or RHEV-M Too late in the game for 3.5.0, pushing out. |
Created attachment 893325 [details] screenshot Description of problem: Version-Release number of selected component (if applicable): is36 How reproducible: 100% Steps to Reproduce: 1. Create a local storage domain 2. Storage -> New Domain 3. Attempt to create additional local domain Actual results: Path cannot be edited, resulting to an error Expected results: Path can be edited. This is the way it works in 3.4. Or if we don't want to support multiple local storage domains, then the creation of storage domains should be disabled when there's local storage domain already configured. Additional info: