RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
Guest customization without perl will fail

Version-Release number of selected component (if applicable):
open-vm-tools-10.1.5-3.el7.x86_64


How reproducible:
always.  Even easier with a looming deadline.

Steps to Reproduce:
1. follow process here for creating template:
https://github.com/chef-partners/knife-vsphere/wiki/Making-a-template-for-cloning
2. leave out perl
3. deploy from your template

Actual results:
NICs light up without config, customization fails, nerds cry

Expected results:
NICs get config, VM sees the world, angels sing

Additional info:
The perl dependency is well-known, if one knows where to look.  Until and unless one refers to the link above, early and often, the perl dependency isn't known -- and the package doesn't seem to pull it in for the DeployPkg piece.

bug 1509044 seems related.

bug 1358108 may be related, but we can't see it.

I think it's just a matter of letting %perl_findrequires run, or hard-setting the perl dep when DeployPkg is in the cpioball.  It could all be just.too.easy!

This is a duplicate of bug 1358108 and I'll make that other bug
public in just a minute.

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