3:08 a.m.
On Mon, Oct 04, 2021 at 01:03:10PM +0000, Schreuders, Cliffe wrote:
Thank you. It does look like that bug could be related.
Is the problem just with the IP addresses? Do you see other guest
information or are those missing too?
Tomas
I had an earlier version of the VM template which continued to work correctly, and an
updated version (via apt-get dist-upgrade) that did not report IP addresses correctly.
I suspected that it might be related to the new ovirt/qemu user agent, so I hold/pinned
"ovirt-guest-agent" on the older template before re-running the software
updates.
This worked to create an updated Kali VM that reports it's IP address (albeit
more-or-less stuck with whatever dependencies the last ovirt-guest-agent has) so it seems
this is indeed an issue with qemu-guest-agent vs ovirt-guest-agent.
Cheers,
Cliffe.
________________________________
From: Arik Hadas <ahadas(a)redhat.com>
Sent: 03 October 2021 12:04
To: Schreuders, Cliffe <C.Schreuders(a)leedsbeckett.ac.uk>
Cc: users <users(a)ovirt.org>; Tomas Golembiovsky <tgolembi(a)redhat.com>
Subject: Re: [ovirt-users] qemu-guest-agent not reporting IP address on boot?
Caution External Mail: Do not click any links or open any attachments unless you trust
the sender and know that the content is safe.
On Fri, Oct 1, 2021 at 5:51 PM
<c.schreuders@leedsbeckett.ac.uk<mailto:c.schreuders@leedsbeckett.ac.uk>>
wrote:
Hi folks,
Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and instead package
qemu-guest-agent. However, since this upgrade VMs based on Kali no longer report their IP
address to oVirt (and therefore timeout during provisioning). If I interact with the VM
console, the VM does have an IP address, and the agent is running, yet oVirt reports N/A
IP address. I've tried restarting the agent, but that does not help. If I load the
console and use the VM it seems to increase the chances the IP address will eventually
makes it's way to oVirt, although I can't seem to reproduce an update, or get it
to provide the IP address on boot so that provisioning works reliably.
Any suggestions would be really appreciated.
Might be the same as/related to
https://bugzilla.redhat.com/show_bug.cgi?id=1981946<https://eur02.safe...
which is still being investigated
Thank you.
Cheers,
Cliffe.
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to
users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement:
https://www.ovirt.org/privacy-policy.html<https://eur02.safelinks.prot...
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/<https://eu...
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFINLLXPBRK...
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
--
Tomáš Golembiovský <tgolembi(a)redhat.com>
4:07 a.m.
New subject: qemu-guest-agent not reporting IP address on boot?
> Thank you. It does look like that bug could be related.
Is the problem just with the IP addresses? Do you see other guest
information or are those missing too?
Tomas
I've just been testing this further, as pinning the old package introduced some
dependency problems with other software. I would like to avoid manually compiling or
editing dependancies in packages, etc.
Some other live guest information does seem to partly populate correctly, most obvious
being free memory. However, the Guest Info tab in oVirt admin panel is showing
"Unknown" for Type, Architecture, etc. However, I've just checked a Kali VM
that has managed to report it's IP address to oVirt and that Guest Info is still
showing as Unknown.
I'm really hoping to find an action on the client that can force the information to
populate. It seemed as though connecting to the console and running "service qemu
restart; service networking restart" often does the trick when run manually, but my
hackish approach of having those happen at boot in the template don't seem to fix the
issue of the IP address being picked up automatically on boot.
Can you suggest any commands we could run on the client that could encourage the agent to
report the IP address?
Thank you.
Cheers,
Cliffe.
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
5:48 p.m.
New subject: qemu-guest-agent not reporting IP address on boot?
Following up on this, for the benefit of anyone else who faces the same problem, I'm
happy to say we have VMs reporting IP addresses with latest Kali now.
I've not managed to fix the fact that it is taking Kali a lot longer to report IP
address (compared to the last version that shipped with ovirt-guest-agent, which reports
IP addresses almost instantly on boot), but I extended the time out to give a lot more
time for the VM to get an IP address (it is taking around 5 minutes), and also needed to
add exception handling to the Vagrant oVirt plugin, around accessing the nics_service,
which was throwing an oVirt error after a few minutes "Can't send request: Failed
sending data to the peer", after allowing those errors to be ignored during the wait
for an IP to be reported, it does eventually report the IP address, and other guest
information. VMs are now reliably building again (albeit taking a little longer).
Thanks.
Cheers,
Cliffe.
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
931
days inactive
931
days old
2 comments
2 participants
participants (2)
-
Schreuders, Cliffe -
Tomáš Golembiovský