Project

General

Profile

Actions
Copy link

Bug #4159

closed

Thin provisioning for VMware disks in compute profiles can't be saved

Added by Ewoud Kohl van Wijngaarden almost 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Martin Matuška
Category:
Compute resources
Target version:
1.4.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Steps to reproduce:
  • Create a VMware compute resource
  • Create a compute profile with thin provisioning checked
  • Save
  • Open compute profile again
Expected results:
  • when I open the compute profile, thin provisioning should be checked
  • When I create a new host based on the compute profile, thin provisioning should be checked
Actual results:
  • when I open the compute profile, thin provisioning is not checked.
  • When I create a new host based on the compute profile, thin provisioning is not checked

Related issues 5 (0 open — 5 closed)

Related to Foreman - Feature #3178: add ability to apply a virtual hardware template at hostgroup levelClosedJoseph Magen10/01/2013Actions
Related to Foreman - Feature #2168: provisioning vmware - datastore free spaceDuplicate02/01/2013Actions
Related to Foreman - Bug #5652: vmWare Compute Resources not being honored ClosedDominic Cleal05/09/2014Actions
Has duplicate Foreman - Bug #4236: Thin provision checkbox in compute profileDuplicate02/03/2014Actions
Has duplicate Foreman - Bug #4312: compute profiles do not store thick/thin setting for vSphere volumesDuplicate02/11/2014Actions
Actions
Copy link
 #1

Updated by Ewoud Kohl van Wijngaarden almost 11 years ago

  • Related to Feature #3178: add ability to apply a virtual hardware template at hostgroup level added
Actions
Copy link
 #2

Updated by Dominic Cleal almost 11 years ago

  • Translation missing: en.field_release deleted (2)
Actions
Copy link
 #3

Updated by Magnus Jernberg almost 11 years ago

I want to have thick provisioning, and in our tests the result is completely opposite to the scenarios described in this bug.

I guess the bottom line is that whatever we choose should stick.

Btw, the compute profiles is a really good feature!

Actions
Copy link
 #4

Updated by Magnus Jernberg almost 11 years ago

More testing done...
Regardless of checked or not checked, the update in the database always writes "thin"=>"true" in the yaml in the 'vm_attrs' of that compute_attributes

Actions
Copy link
 #5

Updated by Dominic Cleal almost 11 years ago

  • Has duplicate Bug #4236: Thin provision checkbox in compute profile added
Actions
Copy link
 #6

Updated by Dominic Cleal almost 11 years ago

  • Has duplicate Bug #4312: compute profiles do not store thick/thin setting for vSphere volumes added
Actions
Copy link
 #7

Updated by Dominic Cleal almost 11 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Martin Matuška
  • Target version set to 1.9.1
  • Translation missing: en.field_release set to 5
Actions
Copy link
 #8

Updated by Martin Matuška almost 11 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #9

Updated by Benjamin Papillon almost 11 years ago

  • Related to Feature #2168: provisioning vmware - datastore free space added
Actions
Copy link
 #10

Updated by Dominic Cleal over 10 years ago

  • Related to Bug #5652: vmWare Compute Resources not being honored added
Actions
Copy link

Also available in: Atom PDF