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.
Bug 2035202 - vm starts network disconnected
Summary: vm starts network disconnected
Keywords:
Status: CLOSED DUPLICATE of bug 1358108
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: open-vm-tools
Version: 8.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-23 09:24 UTC by Ilkka Tengvall
Modified: 2024-08-07 04:25 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-04 19:03:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-106494 0 None None None 2021-12-23 09:27:10 UTC

Description Ilkka Tengvall 2021-12-23 09:24:04 UTC 
Description of problem:

RHEL vm in vmware always starts network disconnected. I need to manually go and start the network from vmware gui.


Version-Release number of selected component (if applicable):


open-vm-tools-11.2.5-2.el8.x86_64
vSphere Client version 7.0.3.00100


How reproducible:

Every time. I have created template several times, and new VMs from that, always happens.


Steps to Reproduce:
1. create template
   I create the template using this playbook:
   https://github.com/RedHatNordicsSA/cool-lab/blob/packer/build-rhel-template-packer-vmware.yml
   which uses this packer ansibles:
   https://github.com/ikke-t/ansible-packer/blob/master/templates/build-vmware.json.j2

2. And I start the vm like this from the template:
https://github.com/RedHatNordicsSA/cool-lab/blob/main/ensure-vm-state.yml


Actual results:

Network adapter 1 	
RH-seg-2991 (disconnected) | 00:50:56:be:eb:7b 


Expected results:

VM to boot and get dhcp ip address, and accept ssh.

Additional info:

https://github.com/ansible-collections/community.vmware/issues/1109

I have this in our demo lab, and I'm happy to work with you solving it. I can do screen share any time. And all the steps to reproduce this are in the ansible playbooks.
Comment 1 Ilkka Tengvall 2021-12-23 09:38:37 UTC 
there is one error in logs:

[root@localhost ~]# grep -i error -A5 -B5 /var/log/vmware-vmsvc-root.log
[2021-12-22T15:08:29.346Z] [ message] [vmtoolsd] Plugin 'guestInfo' initialized.
[2021-12-22T15:08:29.346Z] [ message] [vmtoolsd] Plugin 'powerops' initialized.
[2021-12-22T15:08:29.346Z] [ message] [vmtoolsd] Plugin 'timeSync' initialized.
[2021-12-22T15:08:29.346Z] [ message] [vmtoolsd] Plugin 'vmbackup' initialized.
[2021-12-22T15:08:29.368Z] [ message] [powerops] Executing script: '/etc/vmware-tools/poweron-vm-default'
[2021-12-22T15:08:29.466Z] [ warning] [deployPkg] DeployPkgInGuest failed, error = 5
[2021-12-22T15:08:29.478Z] [ message] [vix] VixTools_ProcessVixCommand: command 62
[2021-12-22T15:08:29.507Z] [ message] [powerops] Script exit code: 0, success = 1
[2021-12-22T15:08:59.357Z] [ warning] [vmsvc] SlashProcNet_GetRoute6: open(/proc/net/ipv6_route): No such file or directory
[2021-12-22T15:08:59.357Z] [ warning] [vmsvc] RecordRoutingInfo: Unable to collect IPv6 routing table.
[2021-12-22T15:09:29.354Z] [ warning] [vmsvc] SlashProcNet_GetRoute6: open(/proc/net/ipv6_route): No such file or directory
--
[2021-12-23T08:43:22.053Z] [ message] [vmtoolsd] Plugin 'powerops' initialized.
[2021-12-23T08:43:22.053Z] [ message] [vmtoolsd] Plugin 'timeSync' initialized.
[2021-12-23T08:43:22.053Z] [ message] [vmtoolsd] Plugin 'vmbackup' initialized.
[2021-12-23T08:43:22.065Z] [ message] [powerops] Executing script: '/etc/vmware-tools/poweron-vm-default'
[2021-12-23T08:43:22.133Z] [ message] [vix] VixTools_ProcessVixCommand: command 62
[2021-12-23T08:43:22.139Z] [ message] [vix] ToolsDaemonTcloReceiveVixCommand: command 62, additionalError = 17
[2021-12-23T08:43:22.139Z] [ message] [powerops] Script exit code: 0, success = 1
[2021-12-23T08:43:52.066Z] [ warning] [vmsvc] SlashProcNet_GetRoute6: open(/proc/net/ipv6_route): No such file or directory
[2021-12-23T08:43:52.066Z] [ warning] [vmsvc] RecordRoutingInfo: Unable to collect IPv6 routing table.
[2021-12-23T08:44:22.060Z] [ warning] [vmsvc] SlashProcNet_GetRoute6: open(/proc/net/ipv6_route): No such file or directory
[2021-12-23T08:44:22.061Z] [ warning] [vmsvc] RecordRoutingInfo: Unable to collect IPv6 routing table.
Comment 2 Ilkka Tengvall 2021-12-23 09:41:45 UTC 
I've also tried to add dbus requirement into vmtools service file. This came up from some github issues some years back:

[Unit]
Description=Service for virtual machines hosted on VMware
Documentation=http://github.com/vmware/open-vm-tools
ConditionVirtualization=vmware
Requires=vgauthd.service
After=dbus.service
After=vgauthd.service
DefaultDependencies=no
Before=cloud-init-local.service

[Service]
ExecStart=/usr/bin/vmtoolsd
TimeoutStopSec=5

[Install]
WantedBy=multi-user.target
Also=vgauthd.service


I added After=dbus.service, no difference
Comment 3 Ilkka Tengvall 2021-12-23 09:57:28 UTC 
Some logs:

network manager sees it disconnected too at boot:


-- Unit NetworkManager-dispatcher.service has begun starting up.
Dec 23 11:44:15 localhost.localdomain NetworkManager[948]: <info>  [1640252655.0621] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.32.10-4.el8/libnm-settings-plugin-ifcfg-rh.so")
Dec 23 11:44:15 localhost.localdomain NetworkManager[948]: <info>  [1640252655.0622] settings: Loaded settings plugin: keyfile (internal)
Dec 23 11:44:15 localhost.localdomain NetworkManager[948]: <info>  [1640252655.0690] device (lo): carrier: link connected
Dec 23 11:44:15 localhost.localdomain NetworkManager[948]: <info>  [1640252655.0693] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Dec 23 11:44:15 localhost.localdomain NetworkManager[948]: <info>  [1640252655.0708] manager: (net0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 23 11:44:15 localhost.localdomain NetworkManager[948]: <info>  [1640252655.0723] device (net0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 23 11:44:15 localhost.localdomain kernel: vmxnet3 0000:0b:00.0 net0: intr type 3, mode 0, 3 vectors allocated
Dec 23 11:44:15 localhost.localdomain kernel: vmxnet3 0000:0b:00.0 net0: NIC Link is Down
Dec 23 11:44:15 localhost.localdomain dbus-daemon[874]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 23 11:44:15 localhost.localdomain systemd[1]: Started Network Manager Script Dispatcher Service.


After pressing connect in vmware, so network manager picks it up ok:


-- The start-up result is done.
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0779] device (net0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'man
aged')
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0780] device (net0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'ma
naged')
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0784] manager: NetworkManager state is now CONNECTED_LOCAL
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0787] manager: NetworkManager state is now CONNECTED_SITE
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0788] policy: set 'System net0' (net0) as default for IPv4 routing and DNS
Dec 23 11:44:56 localhost.localdomain dbus-daemon[874]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.5' (uid=0 pid=948 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Dec 23 11:44:56 localhost.localdomain dbus-daemon[874]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0846] device (net0): Activation: successful, device activated.
Dec 23 11:44:56 localhost.localdomain NetworkManager[948]: <info>  [1640252696.0853] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 23 11:44:59 localhost.localdomain sshd[1571]: Accepted publickey for root from 10.254.254.10 port 40528 ssh2: ED25519 SHA256:VGmwHwATXldoaoEQBt9xy2oFbAcbK5gp6pQo3CdVBsI
Dec 23 11:44:59 localhost.localdomain systemd[1]: Created slice User Slice of UID 0.


Some errors in open-vm-tools install log:
[root@localhost vmware-imc]# cat toolsDeployPkg.log 
[2021-12-22T15:08:29.408Z] [   debug] ## Starting deploy pkg operation
[2021-12-22T15:08:29.408Z] [   debug] Deploying /var/run/92667602/imcf-ZQnNNM
[2021-12-22T15:08:29.408Z] [    info] Initializing deployment module.
[2021-12-22T15:08:29.408Z] [    info] Cleaning old state files.
[2021-12-22T15:08:29.408Z] [    info] EXIT STATE 'INPROGRESS'.
[2021-12-22T15:08:29.409Z] [   debug] Setting deploy error: 'Error removing lock '/var/log/.vmware-deploy.INPROGRESS'.(No such file or directory)'.
[2021-12-22T15:08:29.409Z] [    info] EXIT STATE 'Done'.
[2021-12-22T15:08:29.409Z] [   debug] Setting deploy error: 'Error removing lock '/var/log/.vmware-deploy.Done'.(No such file or directory)'.
[2021-12-22T15:08:29.409Z] [    info] EXIT STATE 'ERRORED'.
[2021-12-22T15:08:29.409Z] [   debug] Setting deploy error: 'Error removing lock '/var/log/.vmware-deploy.ERRORED'.(No such file or directory)'.
[2021-12-22T15:08:29.409Z] [   debug] Setting deploy error: 'Success.'.
[2021-12-22T15:08:29.409Z] [    info] Deploying cabinet file '/var/run/92667602/imcf-ZQnNNM'.
[2021-12-22T15:08:29.409Z] [    info] Transitioning from state '(null)' to state 'INPROGRESS'.
[2021-12-22T15:08:29.409Z] [    info] ENTER STATE 'INPROGRESS'.
[2021-12-22T15:08:29.409Z] [    info] Reading cabinet file '/var/run/92667602/imcf-ZQnNNM' and will extract it to '/var/run/.vmware-imgcust-d1WuE8I'.
[2021-12-22T15:08:29.409Z] [    info] Flags in the header: 0.
[2021-12-22T15:08:29.409Z] [    info] Original deployment command: '/usr/bin/perl -I/tmp/.vmware/linux/deploy/scripts /tmp/.vmware/linux/deploy/scripts/Customize.pl /tmp/.vmware/linux/deploy/cust.cfg'.
[2021-12-22T15:08:29.409Z] [    info] Actual deployment command: '/usr/bin/perl -I/var/run/.vmware-imgcust-d1WuE8I/scripts /var/run/.vmware-imgcust-d1WuE8I/scripts/Customize.pl /var/run/.vmware-imgcust-d1WuE8I/cust.cfg'.
[2021-12-22T15:08:29.409Z] [    info] Extracting package files.
[2021-12-22T15:08:29.446Z] [   debug] Check if cust.cfg exists.
[2021-12-22T15:08:29.446Z] [    info] cust.cfg is found in '/var/run/.vmware-imgcust-d1WuE8I' directory.
[2021-12-22T15:08:29.446Z] [   debug] Command to exec : '/usr/bin/cloud-init'.
[2021-12-22T15:08:29.446Z] [    info] sizeof ProcessInternal is 56
[2021-12-22T15:08:29.446Z] [    info] Returning, pending output from stdout
[2021-12-22T15:08:29.446Z] [    info] Returning, pending output from stderr
[2021-12-22T15:08:29.447Z] [   error] execv failed to run (/usr/bin/cloud-init), errno=(2), error message:(No such file or directory)
[2021-12-22T15:08:29.451Z] [    info] Process exited normally after 0 seconds, returned 127
[2021-12-22T15:08:29.451Z] [    info] No more output from stdout
[2021-12-22T15:08:29.451Z] [    info] No more output from stderr
[2021-12-22T15:08:29.451Z] [    info] Customization command output:
''.
[2021-12-22T15:08:29.451Z] [   error] Customization command failed with exitcode: 127, stderr: ''.
[2021-12-22T15:08:29.451Z] [    info] cloud-init is not installed.
[2021-12-22T15:08:29.451Z] [    info] Executing traditional GOSC workflow.
[2021-12-22T15:08:29.451Z] [   debug] Command to exec : '/usr/bin/perl'.
[2021-12-22T15:08:29.451Z] [    info] sizeof ProcessInternal is 56
[2021-12-22T15:08:29.451Z] [    info] Returning, pending output from stdout
[2021-12-22T15:08:29.451Z] [    info] Returning, pending output from stderr
[2021-12-22T15:08:29.453Z] [   error] execv failed to run (/usr/bin/perl), errno=(2), error message:(No such file or directory)
[2021-12-22T15:08:29.456Z] [    info] Process exited normally after 0 seconds, returned 127
[2021-12-22T15:08:29.456Z] [    info] No more output from stdout
[2021-12-22T15:08:29.456Z] [    info] No more output from stderr
[2021-12-22T15:08:29.456Z] [    info] Customization command output:
=================== Perl script log start =================

=================== Perl script log end =================
[2021-12-22T15:08:29.456Z] [   error] Customization command failed with exitcode: 127, stderr: ''.
[2021-12-22T15:08:29.456Z] [   error] Customization process returned with error.
[2021-12-22T15:08:29.456Z] [   debug] Deployment result = 127.
[2021-12-22T15:08:29.456Z] [    info] Setting 'unknown' error status in vmx.
[2021-12-22T15:08:29.457Z] [    info] Transitioning from state 'INPROGRESS' to state 'ERRORED'.
[2021-12-22T15:08:29.457Z] [    info] ENTER STATE 'ERRORED'.
[2021-12-22T15:08:29.457Z] [    info] EXIT STATE 'INPROGRESS'.
[2021-12-22T15:08:29.457Z] [   debug] Setting deploy error: 'Deployment failed.The forked off process returned error code.'.
[2021-12-22T15:08:29.457Z] [   error] Deployment failed.The forked off process returned error code.
[2021-12-22T15:08:29.457Z] [    info] Launching cleanup.
[2021-12-22T15:08:29.457Z] [   debug] Command to exec : '/bin/rm'.
[2021-12-22T15:08:29.457Z] [    info] sizeof ProcessInternal is 56
[2021-12-22T15:08:29.457Z] [    info] Returning, pending output from stdout
[2021-12-22T15:08:29.457Z] [    info] Returning, pending output from stderr
[2021-12-22T15:08:29.466Z] [    info] Process exited normally after 0 seconds, returned 0
[2021-12-22T15:08:29.466Z] [    info] No more output from stdout
[2021-12-22T15:08:29.466Z] [    info] No more output from stderr
[2021-12-22T15:08:29.466Z] [    info] Customization command output:
''.
[2021-12-22T15:08:29.466Z] [    info] sSkipReboot: 'false', forceSkipReboot 'false'.
[2021-12-22T15:08:29.466Z] [   error] Deploy error: 'Deployment failed.The forked off process returned error code.'.
[2021-12-22T15:08:29.466Z] [   error] Package deploy failed in DeployPkg_DeployPackageFromFile
[2021-12-22T15:08:29.466Z] [   debug] ## Closing log
Comment 4 Ilkka Tengvall 2021-12-23 10:14:15 UTC 
from the logs I see open-vm-tools tries to go for cloud-init and perl, which neither i have installed. So rpm is buggy if it lacks such dependency. If either is critical, it should require them. I try adding them into the template.
Comment 5 Ilkka Tengvall 2021-12-23 10:51:37 UTC 
Now it works. It is RPM error. If I add perl manually, the network starts to work, as the installer requires perl for initializations.

So the open-vm-tools needs to be fixed with perl as dependency.
Comment 6 Richard W.M. Jones 2021-12-23 11:26:14 UTC 
Cathy/Ravindra, a couple of bugs you might want to look at related to this:

https://bugzilla.redhat.com/show_bug.cgi?id=1358108
https://bugzilla.redhat.com/show_bug.cgi?id=1539802
Comment 7 Cathy Avery 2022-01-04 15:16:48 UTC 
Based on John's comment https://bugzilla.redhat.com/show_bug.cgi?id=1358108#c30

"We discussed the following on call this morning - The perl dependency comes from the deploypkg plug-in. There are three use cases for this plugin. First is to clone a template and customize guest on initial boot using vSphere’s customization feature. Second is to re-customize by SRM after a failover. Third is to re-customize the clone of a running VM using the instant clone feature.  In addition, if customer is using cloud-init to do customization, then there is a dependency on python  If they are using legacy customization method, then there is a dependency on perl.  Not all customers use the above features, so it is undesirable to force all users of OVT to install perl. Many security sensitive customer would not want to have perl installed. We don’t see a good solution to this. Would like to close this as Won’t Fix."


John has vmware's position on this issue changed? 

Thanks,

Cathy
Comment 8 John Savanyo 2022-01-04 16:24:43 UTC 
(In reply to Cathy Avery from comment #7)
> Based on John's comment
> https://bugzilla.redhat.com/show_bug.cgi?id=1358108#c30
> 
> "We discussed the following on call this morning - The perl dependency comes
> from the deploypkg plug-in. There are three use cases for this plugin. First
> is to clone a template and customize guest on initial boot using vSphere’s
> customization feature. Second is to re-customize by SRM after a failover.
> Third is to re-customize the clone of a running VM using the instant clone
> feature.  In addition, if customer is using cloud-init to do customization,
> then there is a dependency on python  If they are using legacy customization
> method, then there is a dependency on perl.  Not all customers use the above
> features, so it is undesirable to force all users of OVT to install perl.
> Many security sensitive customer would not want to have perl installed. We
> don’t see a good solution to this. Would like to close this as Won’t Fix."
> 
> 
> John has vmware's position on this issue changed? 
> 
> Thanks,
> 
> Cathy

Hi Cathy, 

Position is the same. We don't want to force all users to install perl.

Thanks,
John
Comment 9 Cathy Avery 2022-01-04 19:03:35 UTC 
OK so it looks like we will not be fixing this issue and we will be closing this BZ as a duplicate of 1358108. 

Thanks,

Cathy

*** This bug has been marked as a duplicate of bug 1358108 ***
Comment 10 Bozhan 2024-04-08 10:09:24 UTC 
Hello John Savanyo ,
It would be perfect if these dependencies are mentioned somewhere in the otherwise long and descriptive README https://github.com/vmware/open-vm-tools/blob/master/README.md

Thank you
Comment 11 Red Hat Bugzilla 2024-08-07 04:25:02 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.