Project

General

Profile

Actions
Copy link

Bug #12487

open

Provisioning with Templates causes new VM to use Template Disk

Added by Michael Speth about 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
1.10.0
Red Hat JIRA:

Description

Foreman 1.10 is using a Template's Disk for provisioned VMs disk.

Environment
  • Server OS: Ubuntu 14.04
  • Foreman: 1.10.0-RC2
  • Web Server: Apache + Passenger
  • vSphere: 5.0.0

Workflow
  • Kick off provision from templates (same with either thin provision or not)
  • Foreman Creates and Copies Template's Disk to the correct location on vSphere
  • Boots VM using Template's Disk NOT new Disk
  • Template is locked because new VM is using the disk

Output
This section contains supporting information.

Provision Log
I have attached foreman.log which contains a provision log for the foreman-test-16 host.

Foreman Error
The following is the error from foreman in an attempt to provision a 2nd vm.
Failed to create a compute vSphere-PN (VMware) instance foreman-test-11.config.landcareresearch.co.nz: FileLocked: Unable to access file [PN_IBM_SAN_VM02] Ubuntu 14.04.1 Template/Ubuntu 14.04.1 Template.vmdk since it is locked

vSphere
  • The tempaltes.jpg file shows the Ubuntu 14.04 Template and that is locked
  • wrongdrive.jpg shows that vSphere is using the template disk and not the newly provisioned disk

Files

templates.jpg View templates.jpg 22.4 KB Michael Speth, 11/15/2015 07:35 PM
wrongdrive.jpg View wrongdrive.jpg 48.1 KB Michael Speth, 11/15/2015 07:35 PM
foreman.log foreman.log 151 KB Log File Containing Provision Michael Speth, 11/15/2015 07:53 PM

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #9705: Disk sizes specified not used in VMware image provisioningClosedIvan Necas03/10/2015Actions
Actions
Copy link

Also available in: Atom PDF