Bug 1463693

Summary:	RFE: virt-v2v should install RHEV guest agent
Product:	Red Hat Enterprise Linux 7	Reporter:	Richard W.M. Jones <rjones>
Component:	libguestfs	Assignee:	Richard W.M. Jones <rjones>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	cbolz, jcoscia, mxie, mzhan, ptoscano, tzheng
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	V2V
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-02 09:55:10 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 Richard W.M. Jones 2017-06-21 14:03:29 UTC

Description of problem:

Currently during conversions to RHEV, virt-v2v installs

  RHEV-Application-Provisioning-Tool.exe_4.12

However this turns out not to be the only useful tool that
we could install.  We could also install the RHEV guest agent,
which allows for "the manager to report the stats of the VM once
running in RHV already, it also reports the VM's IP, FQDN, etc"

See also:

https://access.redhat.com/solutions/261763
" How to install the RHEV Guest Agent in a virtual machine"

Comment 2 Pino Toscano 2017-08-14 16:30:05 UTC

(In reply to Richard W.M. Jones from comment #0)
> https://access.redhat.com/solutions/261763
> " How to install the RHEV Guest Agent in a virtual machine"

According to these instructions, the procedure is like the following:
1) make sure the VM is subscribed to a "common" channel (which I think is available for any customer)
2) install a package from there
3) enable the service of the agent

Random unordered thoughts I have about this:
a) this is specific for RHEL, so surely per-distro procedures (and for Windows too) will need to be implemented
b) the guest agent is composed by various files: Python sources, PAM configurations, oVirt/RHV hooks, udev rules, and so on; for this reason, copying it from the v2v conversion server is too unpractical, and anyway using distro packages on the guest gives the great benefit of automatic in-guest updates
c) I don't think doing the procedure during the conversion is the best idea, especially since v2v generally does not install new packages on Linux [1]; thus IMHO the best option is a firstboot script
d) there may be a number of failures during general distro installation, e.g. installation failing for some reason
e) in addition to (d), there may be a number of failures on RHEL, e.g. the guest not subscribed with subscription-manager, not attached to a valid pool, not able to subscribe to the "common" channel
f) Windows has a totally different procedure (as usual)

Anything I missed?  More thoughts on this?

[1] except when replacing old VMware tools RPMs which provide replacements for system libraries, but this is a very niche (and possibly no more happening) scenario

Comment 3 Richard W.M. Jones 2018-08-02 09:55:10 UTC

Closing as this is not a bug.  Installation of RHEV-APT should
be sufficient to install all the other stuff.