Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

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

Open
zlangi opened this issue Nov 2, 2018 · 0 comments

Comments

@zlangi
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

Bug

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"
ID=coreos
VERSION=1855.5.0
VERSION_ID=1855.5.0
BUILD_ID=2018-10-22-2305
PRETTY_NAME="Container Linux by CoreOS 1855.5.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant