Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRichard 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"
(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 3Richard 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.