Bug 1484532

Summary:	[RFE] Deployment via Satellite
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ryan Barry <rbarry>
Component:	rhev-hypervisor-ng	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED ERRATA	QA Contact:	Qin Yuan <qiyuan>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	cshao, dfediuck, eheftman, huzhao, mgoldboi, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, ylavi, yzhao
Target Milestone:	ovirt-4.2.4	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Starting from version 4.0, Red Hat Virtualization Hosts could not be deployed from Satellite, and therefore could not take advantage of Satellite's tooling features. In this release, Red Hat Virtualization Hosts can now be deployed from Satellite 6.3.2 and later.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-27 10:04:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1186915
Bug Blocks:

Description Ryan Barry 2017-08-23 19:35:20 UTC

Description of problem:
Currently, RHV-H cannot be deployed via Satellite, as Satellite does not support liveimg deployments.

This bug is to track that inclusion from the RHV side.

Comment 2 Yaniv Kaul 2017-11-28 19:28:18 UTC

That clearly missed 4.2.0, moving to 4.2.1

Comment 3 Qin Yuan 2018-05-24 08:09:41 UTC

Follow the steps in https://bugzilla.redhat.com/show_bug.cgi?id=1186915#c23, can deploy RHVH via satellite now.

Used Versions:
satellite-6.3.1-3.el7sat.noarch
foreman-1.15.6.38-1.el7sat.noarch
tfm-rubygem-katello-3.4.5.64.2-1.el7sat.noarch
RHVH-4.2-20180518.5-RHVH-x86_64-dvd1.iso

Comment 4 Qin Yuan 2018-05-31 06:21:12 UTC

According to comment #3, change the status to VERIFIED.

Comment 6 errata-xmlrpc 2018-06-27 10:04:47 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, 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/RHSA-2018:2079

Comment 7 Franta Kust 2019-05-16 13:04:14 UTC

BZ<2>Jira Resync