Bug 1871184

Summary:	osbuild-composer produced vmdk images cannot be uploaded to vCenter
Product:	Red Hat Enterprise Linux 8	Reporter:	Tom Gundersen <tgunders>
Component:	osbuild-composer	Assignee:	Image Builder team <osbuilders>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	atodorov
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 02:52:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tom Gundersen 2020-08-21 14:07:19 UTC

Description of problem:

The vmdk images produced by osbuild-composer are not compatible with vCenter.

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

osbuild-composer-19

How reproducible:

Always.


Steps to Reproduce:
1. produce a vmdk image using composer-cli compose
2. push to vCenter

Actual results:

Image is declined as the format is not streamOptimized

Expected results:

Image is accepted and can be booted.

Additional info:

Proposed fix in https://github.com/osbuild/osbuild-composer/pull/934

Comment 2 Tom Gundersen 2020-08-25 12:26:59 UTC

Fixed in osbuild-composer-20 or before.

Comment 3 Tom Gundersen 2020-08-25 12:34:29 UTC

This bz was not added to errata by mistake before internal development deadlines. However, the change landed well before any freeze, so we are attempting now to just reflect reality in the bz.

Comment 9 errata-xmlrpc 2020-11-04 02:52:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (osbuild, cockpit-composer and osbuild composer bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4674