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

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

Is this related to the newer fog?

This is with only Satellite6.1.3 no fog libs updated.

Created redmine issue http://projects.theforeman.org/issues/12652 from this bug

From upstream bug. Kedar, can you check into this:

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".

For reference, go to: https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.hostclient.doc/GUID-2CFBCCD5-B53D-42CD-AECD-FBC46AAC4AC5.html?resultof=%2522%2568%2561%2572%2564%2522%2520%2522%2564%2569%2573%256b%2522%2520

Ok, let's update this bug as per the suggestion.

Upstream bug component is Compute Resources - VMWare

Upstream bug component is Compute Resources

Upstream bug component is Compute Resources - VMWare

Created PR

https://github.com/theforeman/foreman/pull/4252

The fix to this bug will be delivered with release 6.3 of Satellite.