Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

customization fails when CoreOS is being deployed by terraform leads network interface disconnected #2521

zlangi opened this Issue Nov 2, 2018 · 0 comments


None yet
1 participant
Copy link

zlangi commented Nov 2, 2018

Issue Report

We have an issue with the latest CoreOS image when deploying it to vcenter using terraform.

The deployment succeeds, terraform then starts to customize the newly created vm pushing customization to it. The process fails leaving the vm in a bad state and the network interface disconnected. It makes the automation of the process impossible.
This could be caused by the open-vm-tools version on coreos.
Everything was working fine before 1800.x.x


The customization process fails with the following message (you can see it in vcenter in the event log):
The customization component failed to set the required parameters inside the guest operating system

Container Linux Version

$ cat /etc/os-release 
NAME="Container Linux by CoreOS"
PRETTY_NAME="Container Linux by CoreOS 1855.5.0 (Rhyolite)"


What hardware/cloud provider/hypervisor is being used to run Container Linux?
ESXi 6.7u1 and vcenter 6.7u1.

Expected Behavior

Customization succeeds, vm boots up

Actual Behavior

Customization fails, vm boots up leaving the network interface disconnected

Reproduction Steps

  1. Create a new vm using terraform
  2. Push customization on the vm

Other Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.