+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1679039 +++ ====================================================================== Description of problem: When trying to upload a disk-image to Storage-Domain via Menu Storage->Domain->'<my-storage-domain>'->disks->upload the wrong DC is selected and the upload will fail. Version-Release number of selected component (if applicable): ovirt-engine-4.2.8.2-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Create RHV environment with two Datacenter 2. Select Storage-Domain of second Datacenter 3. Try uploading a disk image Actual results: The wrong Datacenter is shown and the upload will fail Expected results: The correct DC should be selected and the upload into the selected storage-domain should succeed Additional info: Using Menu 'Storage->Disk->upload', you're able to select the right DC and Storagedomain and the upload will succeed. (Originally by Steffen Froemer)
Created attachment 1536604 [details] Screenshot of Uploadmenu of disk-menu (Originally by Steffen Froemer)
Created attachment 1536605 [details] Screenshot of Uploadmenu of storage-domain->disk-menu I've added two screenshots. One from Storage-Domain menu, where wrong DC is pre-selected and unable to change. Second the Menu from Storage->Disk-menu, where I'm able to change the DC and also the hosts are correctly selected. (Originally by Steffen Froemer)
Bug verified in: ovirt-engine-4.3.5.2-0.1.el7.noarch scenario checked (according to the steps in the description): Created RHV environment with two data centers. Attached 2 different storage domains to 2 different data centers. Tried to upload disk image on each of the storage domains and checked that the correct data center is picked. Moving to VERIFIED
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-2019:2431
sync2jira