OVF does not read user-data if vmware IMC is used.

This bug was originally filed in Launchpad as [LP: #1806133](https://bugs.launchpad.net/cloud-init/+bug/1806133)

Launchpad details

affected_projects = ['cloud-init (Ubuntu)']

assignee = None

assignee_name = None

date_closed = None

date_created = 2018-11-30T22:04:17.905136+00:00

date_fix_committed = None

date_fix_released = None

id = 1806133

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1806133

milestone = None

owner = smoser

owner_name = Scott Moser

private = False

status = confirmed

submitter = smoser

submitter_name = Scott Moser

tags = ['amd64', 'apport-bug', 'disco', 'uec-images']

duplicates = []

_Launchpad user **Scott Moser(smoser)** wrote on 2018-11-30T22:04:17.905136+00:00_

As currently implemented, cloud-init will read either OVF CDrom *or* the vmware IMC data.

That means if user-data is provided in the OVF environment file then it will not be consumed at all by cloud-init.

It seems we need to either:
a.) support reading and merging these two sources of information
b.) provide some way to feed user-data through the IMC path separately.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cloud-init 18.4-24-g8f812a15-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
CloudName: LXD
Date: Fri Nov 30 21:56:38 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
user_data.txt:
#cloud-config
{}