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

Bug 2055116

Summary: "Thin provisioned template disks can not be defined as Raw" error despite preallocate disk
Product: [oVirt] ovirt-engine Reporter: harj.bo
Component: RestAPIAssignee: Arik <ahadas>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.4.9.5CC: bugs, mperina
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-17 11:13:11 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:

Description harj.bo 2022-02-16 10:27:26 UTC 
Description of problem:
with the aim of automating the increase of the vm of the pool, using a template with preallocated disk I get the error in question
I tried with API via curl and with ansible-playbook getting the same error

Version-Release number of selected component (if applicable):


How reproducible:
data in curl:
<vm_pool>
  <name>VM_Pool_B</name>
  <description>Virtual Machine Pool B</description>
  <size>3</size>
  <prestarted_vms>1</prestarted_vms>
  <max_user_vms>2</max_user_vm>
</vm_pool>
(there is an error in the manuals cap. 6.254.4. update PUT)

Steps to Reproduce:
use curl to "PUT /ovirt-engine/api/vmpools/[vmpool id]"
with the data field 
<vm_pool>
  <name>VM_Pool_B</name>
  <description>Virtual Machine Pool B</description>
  <size>13</size>
  <prestarted_vms>1</prestarted_vms>
  <max_user_vms>2</max_user_vm>
</vm_pool>
Actual results:
"Thin provisioned template disks can not be defined as Raw"

Expected results:
if I had 10 vm in my pool, this should add 3 vm

Additional info:
With ansible playbook I get the same error
Comment 1 Arik 2022-02-17 11:13:11 UTC 

*** This bug has been marked as a duplicate of bug 1952502 ***