Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1364792

Summary: [downstream clone - 3.6] [Disk profile] Cannot add VM. Disk Profile YYY with id XXX is not assigned to Storage Domain ZZZ
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Yanir Quinn <yquinn>
Status: CLOSED ERRATA QA Contact: Israel Pinto <ipinto>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: bugs, dfediuck, eshenitz, gklein, ipinto, lsurette, mavital, mgoldboi, ratamir, rbalakri, Rhev-m-bugs, srevivo, ykaul, yquinn
Target Milestone: ovirt-3.6.10Keywords: AutomationBlocker, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1361838 Environment:
Last Closed: 2017-01-17 18:03:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1361838    
Bug Blocks:    

Comment 3 Roy Golan 2016-09-06 10:33:41 UTC 
removing the blocker since this scenario happens when one of the storage domains is in maintenance and that scrambles the order of storage domains list and profiles and reveals this bug.
Comment 4 Israel Pinto 2016-11-16 15:38:23 UTC 
Verify:
Engine: RHEVM Version: 3.6.10-0.1.el6
Host: 
OS Version:RHEL - 7.2 - 13.0.el7ev
Kernel Version:3.10.0 - 327.36.1.el7.x86_64
KVM Version:2.3.0 - 31.el7_2.23
LIBVIRT Version:libvirt-1.2.17-13.el7_2.6
VDSM Version:vdsm-4.17.36-1.el7ev

Steps:
1. Create template with disk on master storage domain and copy it's disk to more then one storage domain
2. Put Master storage domain to maintenance  
3. Create VM from template from UI
4. Create VM from template via REST without setting disk profile 

Results:
VM is created on both scenarios - PASS
Comment 6 errata-xmlrpc 2017-01-17 18:03:50 UTC 
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://rhn.redhat.com/errata/RHEA-2017-0108.html