Bug 1891923

@demeng , hi dehan, does x86 also have this bug?

(In reply to bfu from comment #1)
> @demeng , hi dehan, does x86 also have this bug?

We hit it before as Bug-1845127, but it has been fixed and automated yet.

It's a bit hard to see what could be arch-specific about the fix for bug 1845127.

Hi david,
this bug also occurred with qemu_version:qemu-kvm-4.2.0-34.module+el8.3.0+7976+077be4ec.ppc64le, so this seems not a regression bug

The only way I can reproduce this bug is when I don't update the guest QGA to
the 5.1 version. Which makes sense, given that the fix was in QGA code.

bfu, can you please check the qemu-ga version you're using? I was using:

[root@localhost ~]# /usr/bin/qemu-ga --version
QEMU Guest Agent 4.2.0


And I got the exact behavior you described. When I updated the qemu-guest-agent
package - inside the guest - to the RHEL-AV version, the bug didn't occur:

# qemu-ga --version
QEMU Guest Agent 5.1.0

This is a series of commands changing the hostname in the guest:

[root@newhostname ~]# hostnamectl set-hostname newhostname && cat /etc/hostname
newhostname
[root@newhostname ~]# hostnamectl set-hostname newhostname2 && cat /etc/hostname 
newhostname2
[root@newhostname ~]# hostnamectl set-hostname newhostname-qga5.1


This is the output from the QGA socket:

[danielhb@ltc-boston115 ~]$ sudo nc -U /tmp/qga.sock
[sudo] password for danielhb: 
{"execute":"guest-get-host-name"}
{"return": {"host-name": "newhostname"}}
{"execute":"guest-get-host-name"}
{"return": {"host-name": "newhostname2"}}
{"execute":"guest-get-host-name"}
{"return": {"host-name": "newhostname-qga5.1"}}

(In reply to Daniel Henrique Barboza from comment #5)
> The only way I can reproduce this bug is when I don't update the guest QGA to
> the 5.1 version. Which makes sense, given that the fix was in QGA code.
> 
> bfu, can you please check the qemu-ga version you're using? I was using:
> 
> [root@localhost ~]# /usr/bin/qemu-ga --version
> QEMU Guest Agent 4.2.0
> 
> 
> And I got the exact behavior you described. When I updated the
> qemu-guest-agent
> package - inside the guest - to the RHEL-AV version, the bug didn't occur:
> 
> # qemu-ga --version
> QEMU Guest Agent 5.1.0
> 
> This is a series of commands changing the hostname in the guest:
> 
> [root@newhostname ~]# hostnamectl set-hostname newhostname && cat
> /etc/hostname
> newhostname
> [root@newhostname ~]# hostnamectl set-hostname newhostname2 && cat
> /etc/hostname 
> newhostname2
> [root@newhostname ~]# hostnamectl set-hostname newhostname-qga5.1
> 
> 
> This is the output from the QGA socket:
> 
> [danielhb@ltc-boston115 ~]$ sudo nc -U /tmp/qga.sock
> [sudo] password for danielhb: 
> {"execute":"guest-get-host-name"}
> {"return": {"host-name": "newhostname"}}
> {"execute":"guest-get-host-name"}
> {"return": {"host-name": "newhostname2"}}
> {"execute":"guest-get-host-name"}
> {"return": {"host-name": "newhostname-qga5.1"}}

Hi david,
   I checked with the qemu-ga version and it's QEMU Guest Agent 4.2.0 indeed, by the way how could I upgrade it?

(In reply to bfu from comment #6)
> (In reply to Daniel Henrique Barboza from comment #5)

[...]

> 
> Hi david,
>    I checked with the qemu-ga version and it's QEMU Guest Agent 4.2.0
> indeed, by the way how could I upgrade it?

Inside the guest, I added an ADVANCED-VIRT 8.3 repo in /etc/yum.repos.d,
then:

$ dnf module disable virt:rhel -y
$ dnf module enable virt:8.3 -y
$ dnf update qemu-guest-agent


This updated qemu-guest-agent to the AV version (5.1).

(In reply to Daniel Henrique Barboza from comment #8)
> (In reply to bfu from comment #6)
> > (In reply to Daniel Henrique Barboza from comment #5)
> 
> [...]
> 
> > 
> > Hi david,
> >    I checked with the qemu-ga version and it's QEMU Guest Agent 4.2.0
> > indeed, by the way how could I upgrade it?
> 
> Inside the guest, I added an ADVANCED-VIRT 8.3 repo in /etc/yum.repos.d,
> then:
> 
> $ dnf module disable virt:rhel -y
> $ dnf module enable virt:8.3 -y
> $ dnf update qemu-guest-agent
> 
> 
> This updated qemu-guest-agent to the AV version (5.1).

Hi Daniel,
 I try to use dnf update and seems it works but qga in guest could not be updated automatically also seems a problem, will you fix this ?

(In reply to bfu from comment #9)
> (In reply to Daniel Henrique Barboza from comment #8)

[...]

> Hi Daniel,
>  I try to use dnf update and seems it works but qga in guest could not be
> updated automatically also seems a problem, will you fix this ?

We can't do that. There is no guarantee that the user/sysadm wants to
automatically update packages on the guest (or the host, for that matter).

As state in comment #2, https://bugzilla.redhat.com/show_bug.cgi?id=1845127
fixed this issue for the RHEL-AV 8.3 package. A guest using QGA 4.2.0 will
need to update QGA to the AV version 5.1, and we can't automate that.

(In reply to Daniel Henrique Barboza from comment #10)
> (In reply to bfu from comment #9)
> > (In reply to Daniel Henrique Barboza from comment #8)
> 
> [...]
> 
> > Hi Daniel,
> >  I try to use dnf update and seems it works but qga in guest could not be
> > updated automatically also seems a problem, will you fix this ?
> 
> We can't do that. There is no guarantee that the user/sysadm wants to
> automatically update packages on the guest (or the host, for that matter).
> 
> As state in comment #2, https://bugzilla.redhat.com/show_bug.cgi?id=1845127
> fixed this issue for the RHEL-AV 8.3 package. A guest using QGA 4.2.0 will
> need to update QGA to the AV version 5.1, and we can't automate that.

followed with https://bugzilla.redhat.com/show_bug.cgi?id=1845127 in comment8
I could only check with this bug after qemu5.1 released so that I won't need to update qga in guest automatically cause it becomes the default qga version right?

Hi Daniel,
    I've changed this bug to rhel8 and are you going to fix it within qemu4.2? If not  maybe you could close it

@dbarboza

(In reply to bfu from comment #12)
> Hi Daniel,
>     I've changed this bug to rhel8 and are you going to fix it within
> qemu4.2? If not  maybe you could close it

In my opinion this doesn't look like the type of bug that warrants a backport.
However I'm also aware that the fix is in QEMU 5.1, and the non-AV QEMU
packages will stick with QEMU 4.2 for awhile.

I'll need some advice on what to do with this one. If the resolution "just tell
users to use QGA from RHEL-AV" is acceptable, then we can close it.

"just tell users to use QGA from RHEL-AV" doesn't quite work, because presumably people are using the non-AV versions because they don't have an AV entitlement.

That said, this is a fairly cosmetic problem, particularly with non-AV (no layered product) where we're probably dealing with a fairly basic management layer, and managing the hostname from within the guest is more likely.

Given that, I'm closing as WONTFIX.  We'll revisit this if a customer encounters the problem in the wild.