Bug #12652
Cannot change the disk name when provisioning a VMware host
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1273947
Description of problem:
cannot change the HardDisk name when provisioning a vm for vmware compute resource.
Version-Release number of selected component (if applicable):
Sat6.1.3
How reproducible:
Steps to Reproduce:
1. add a vmware compute resource
2. provision a host on this compute resource with a custom HD name
3. Unable to see the custom HD name at vmware end
Actual results:
Unable to see the custom HD name in the vmware
Expected results:
Should be able to see the custom HD name at the vmware side.
Additional info:
Associated revisions
History
#1
Updated by Dominic Cleal over 6 years ago
- Subject changed from cannot change the HardDisk name when provisioning a vm for vmware compute resource to Cannot change the disk name when provisioning a VMware host
- Category changed from Compute resources to Compute resources - VMware
Using image or network provisioning? The two methods create VMs in very different ways.
#2
Updated by Angelo Lisco over 6 years ago
Working in a big vmware environment, I can tell you that there is no way to customize the HDD name of a VM on the VMware side.
I know this is possible in RHEV/Ovirt (and maybe other CR managed by fog) but not in VMware.
So, this bug should be modified to something like "Disable volume name customization when a VMware CR is choosen".
#3
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to Chris Roberts
- Pull request https://github.com/theforeman/foreman/pull/4252 added
#4
Updated by Chris Roberts over 5 years ago
- Target version set to 163
#5
Updated by Anonymous over 5 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset a3213b1b4571f26a7427e3d43223cc696c3f0bf9.
#7
Updated by Dominic Cleal over 5 years ago
- Legacy Backlogs Release (now unused) set to 209
Fixes #12652 - VMware Volume name is readonly