+++ This bug was initially created as a clone of Bug #1839619 +++

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.

--- Additional comment from RHEL Program Management on 2020-05-25 04:06:10 UTC ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from ldu on 2020-05-26 00:28:05 UTC ---

Test this issue on RHEL7.8 guest with cloud-init-19.4-7.el7.x86_64, still meet this issue, so this bug should not related to open-vm-tools version.

--- Additional comment from Rick Barry on 2020-06-24 19:01:57 UTC ---

This is a batch update to clean-up back-log RHEL 7.9 Virt team BZs:

RHEL 7.9 is the last minor release for RHEL 7. Only High/Urgent and CVE BZs will be approved for z-stream updates going forward.

This BZ is a candidate to be closed or moved to RHEL 8 because its priority is one of (unspecified, low, medium), was created before RHEL 7.9 bug freeze (June 8, 2020) and is not a CVE.

Please review and take one of these actions before July 3:

1. If there are no plans to fix this BZ, set status to CLOSED.
2. If you plan to fix this BZ in a RHEL 7.9.z batch update, set Priority to High.
3. Otherwise:
   - If there is already a RHEL/RHEL-AV 8 BZ for this issue, then set this BZ to CLOSE/DEFFERED.
   - Move this BZ to RHEL/RHEL-AV 8 (or clone the BZ to RHEL/RHEL-AV 8 and set status for this BZ to CLOSED/DEFERRED, whichever your standard process is for moving BZs from RHEL 7 to 8).

If no action is taken by July 3, this BZ will be set to CLOSED/WONTFIX.

--- Additional comment from Rick Barry on 2020-07-03 18:55:07 UTC ---

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.

--- Additional comment from Eduardo Otubo on 2020-07-10 09:10:04 UTC ---

(In reply to Rick Barry from comment #3)
> This is a batch update to clean-up back-log RHEL 7.9 Virt team BZs:
> 
> RHEL 7.9 is the last minor release for RHEL 7. Only High/Urgent and CVE BZs
> will be approved for z-stream updates going forward.
> 
> This BZ is a candidate to be closed or moved to RHEL 8 because its priority
> is one of (unspecified, low, medium), was created before RHEL 7.9 bug freeze
> (June 8, 2020) and is not a CVE.
> 
> Please review and take one of these actions before July 3:
> 
> 1. If there are no plans to fix this BZ, set status to CLOSED.
> 2. If you plan to fix this BZ in a RHEL 7.9.z batch update, set Priority to
> High.

Setting priority to high for fix in RHEL-7.9.z batch update and ASSIGNED.

This issue is fixed in commit:

  commit c6d09af67626c2f2241c64c10c9e27e8752ba87b
  Author: chengcheng-chcheng <63850735+chengcheng-chcheng.github.com>
  Date:   Wed Jun 10 00:20:47 2020 +0800

      When tools.conf does not exist, running cmd "vmware-toolbox-cmd config get
      deployPkg enable-custom-scripts", the return code will be EX_UNAVAILABLE(69)
      on this condition, it should not take it as error. (#413)

I'll backport to rhel-7.9.z and all other 19.4 branches.

> 3. Otherwise:
>    - If there is already a RHEL/RHEL-AV 8 BZ for this issue, then set this
> BZ to CLOSE/DEFFERED.
>    - Move this BZ to RHEL/RHEL-AV 8 (or clone the BZ to RHEL/RHEL-AV 8 and
> set status for this BZ to CLOSED/DEFERRED, whichever your standard process
> is for moving BZs from RHEL 7 to 8).
> 
> If no action is taken by July 3, this BZ will be set to CLOSED/WONTFIX.