Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
2020-05-22 11:31:53,934 - util.py[DEBUG]: Running command ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts'] with allowed return codes [0] (shell=False, capture=True)
2020-05-22 11:31:53,949 - guestcust_util.py[ERROR]: Failed running ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts'][69]
2020-05-22 11:31:53,950 - guestcust_util.py[ERROR]: Unexpected error while running command.
Command: ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts']
Exit code: 69
Reason: -
Stdout: [deployPkg] enable-custom-scripts UNSET
Stderr:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/cloudinit/sources/helpers/vmware/imc/guestcust_util.py", line 140, in get_tools_config
(outText, _) = util.subp(cmd)
File "/usr/lib/python2.7/site-packages/cloudinit/util.py", line 2084, in subp
cmd=args)
ProcessExecutionError: Unexpected error while running command.
Command: ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts']
Exit code: 69
Reason: -
Stdout: [deployPkg] enable-custom-scripts UNSET
Version-Release number of selected components (if applicable):
RHEL-7.9
cloud-init-19.4-7.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Start a RHEL-7.9 VM in ESXi. Install cloud-init:
# yum install cloud-init
2. Confirm open-vm-tools installation and running in VM.
3. Create a customization specification with a new host name, domain name, timezone, Static IP settings in the Network settings.
4. Clone and customize the Guest with specification created at step 3
5. Power on the Guest cloned, check the new host name, domain name, timezone and network setting customized correct or not on the Guest cloned
6. Check Customization log from /var/log/cloud-init.log
Actual results:
There are error messages in /var/log/cloud-init.log
Expected results:
No error message
Additional info:
- It's a regression issue. It doesn't exist in RHEL7.8 cloud-init-18.5-6.el7.
This BZ is being auto-closed as CLOSED/WONTFIX. If this is not appropriate and a fix is critical for RHEL 7, please re-open.
Note that RHEL 7.9 is the last minor release for RHEL 7. Security and critical bug-fixes will continue to be delivered via RHEL 7 batch updates.
We are running into this problem right now and it is a critical issue for us. We will use 7.x until end of Q1 2021 and need to deploy new VMs in our ESXi environments. We cannot due to this bug. We need either a solution to fix this problem ourselves or need a new version of cloud-init and/or open-vm-tools. It's a regression issue. It doesn't exist in RHEL7.8 cloud-init-18.5-6.el7.
(In reply to Jason Friedrich from comment #20)
> We are running into this problem right now and it is a critical issue for
> us. We will use 7.x until end of Q1 2021 and need to deploy new VMs in our
> ESXi environments. We cannot due to this bug. We need either a solution to
> fix this problem ourselves or need a new version of cloud-init and/or
> open-vm-tools. It's a regression issue. It doesn't exist in RHEL7.8
> cloud-init-18.5-6.el7.
Hi Jason,
This bug had fixed on latest cloud-init, you can update to RHEL7.9 and use the cloud-init-19.4-el7_9.1.
Thanks,
Lili Du
(In reply to Jason Friedrich from comment #20)
> We are running into this problem right now and it is a critical issue for
> us. We will use 7.x until end of Q1 2021 and need to deploy new VMs in our
> ESXi environments. We cannot due to this bug. We need either a solution to
> fix this problem ourselves or need a new version of cloud-init and/or
> open-vm-tools. It's a regression issue. It doesn't exist in RHEL7.8
> cloud-init-18.5-6.el7.
Hi Jason, the fix will soon be released in RHEL 7.9 update (expected within this week), you can try when it is available. We will also let you know when it is released, you can also know the status by checking this bug's statue(closed errata)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (cloud-init bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:5043
Description: 2020-05-22 11:31:53,934 - util.py[DEBUG]: Running command ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts'] with allowed return codes [0] (shell=False, capture=True) 2020-05-22 11:31:53,949 - guestcust_util.py[ERROR]: Failed running ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts'][69] 2020-05-22 11:31:53,950 - guestcust_util.py[ERROR]: Unexpected error while running command. Command: ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts'] Exit code: 69 Reason: - Stdout: [deployPkg] enable-custom-scripts UNSET Stderr: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cloudinit/sources/helpers/vmware/imc/guestcust_util.py", line 140, in get_tools_config (outText, _) = util.subp(cmd) File "/usr/lib/python2.7/site-packages/cloudinit/util.py", line 2084, in subp cmd=args) ProcessExecutionError: Unexpected error while running command. Command: ['vmware-toolbox-cmd', 'config', 'get', 'deployPkg', 'enable-custom-scripts'] Exit code: 69 Reason: - Stdout: [deployPkg] enable-custom-scripts UNSET Version-Release number of selected components (if applicable): RHEL-7.9 cloud-init-19.4-7.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start a RHEL-7.9 VM in ESXi. Install cloud-init: # yum install cloud-init 2. Confirm open-vm-tools installation and running in VM. 3. Create a customization specification with a new host name, domain name, timezone, Static IP settings in the Network settings. 4. Clone and customize the Guest with specification created at step 3 5. Power on the Guest cloned, check the new host name, domain name, timezone and network setting customized correct or not on the Guest cloned 6. Check Customization log from /var/log/cloud-init.log Actual results: There are error messages in /var/log/cloud-init.log Expected results: No error message Additional info: - It's a regression issue. It doesn't exist in RHEL7.8 cloud-init-18.5-6.el7.