Bug 2281464

(In reply to Christoph Karl from comment #0)
> It seems that the file
> /boot/grub2/grub.cfg
> hat other access rights than in the rpm database (stemming from grub2.spec
> file) defined.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Fresh fc40 installation

I launched a VM with this image http://download.eng.bos.redhat.com/released/fedora/F-40/Gold/Everything/x86_64/os/ then I installed grub2-pc

> 2. rpm -Vq grub2-pc
> .M.......  c /boot/grub2/grub.cfg

in my case there is no output

[root@fedora ~]# rpm -Vq grub2-pc

> 
> 3.
> Actual Results:  
> rpm -Vqa is complaining about this file
> 

[root@fedora ~]# rpm -Vqa
.M.......  c /etc/audit/rules.d/audit.rules
.....UG..  g /var/run/avahi-daemon
S.5....T.  c /etc/ssh/sshd_config


> Expected Results:  
> no complains

I recently worked on a similar issue (https://issues.redhat.com/browse/RHEL-16478) which I strongly believe is the same issue as the one discuss here and the fix has been ported to fedora-rawhide (not yet merged) https://src.fedoraproject.org/rpms/grub2/pull-request/84

It's OK for me to wait for this pull request and I will check it after merge again.
Thank you for taking care.

(In reply to Christoph Karl from comment #2)
> It's OK for me to wait for this pull request and I will check it after merge
> again.

PR is targeted for rawhide, I believe this is fine for you.
Also, I am not sure why I am not seeing the same log as you, any idea why?

> Thank you for taking care.

Just rerun once more.
I am using the following kickstart file: See attached.
virt-install \
  --name fedora40 \
  --vcpus 2 \
  --memory 4096 \
  --disk vol=m2ssd/fedora40 \
  --os-variant fedora39 \
  --network bridge=virbr0 \
  --mac=52:54:00:13:9d:9d \
  --graphics vnc,listen=127.0.0.1,port=5940 \
  --location /mnt/lager/ARCHIVE/DATEN-MD5/Fedora-Everything-netinst-x86_64-40-1.14.iso \
  --noautoconsole \
  --initrd-inject=./fedora40-ks.cfg \
  --extra-args "inst.ks=file:/fedora40-ks.cfg"

My output is:
[ckarl@fc40 ~]$ sudo rpm -Vaq
.....UG..  g /var/run/avahi-daemon
.M.......  c /etc/audit/rules.d/audit.rules
.M.......  c /boot/grub2/grub.cfg

Created attachment 2034718 [details]
kickstart file used

(In reply to Christoph Karl from comment #4)
> Just rerun once more.
> I am using the following kickstart file: See attached.
> virt-install \
>   --name fedora40 \
>   --vcpus 2 \
>   --memory 4096 \
>   --disk vol=m2ssd/fedora40 \
>   --os-variant fedora39 \
>   --network bridge=virbr0 \
>   --mac=52:54:00:13:9d:9d \
>   --graphics vnc,listen=127.0.0.1,port=5940 \
>   --location
> /mnt/lager/ARCHIVE/DATEN-MD5/Fedora-Everything-netinst-x86_64-40-1.14.iso \
>   --noautoconsole \
>   --initrd-inject=./fedora40-ks.cfg \
>   --extra-args "inst.ks=file:/fedora40-ks.cfg"
> 
> My output is:
> [ckarl@fc40 ~]$ sudo rpm -Vaq
> .....UG..  g /var/run/avahi-daemon
> .M.......  c /etc/audit/rules.d/audit.rules
> .M.......  c /boot/grub2/grub.cfg

I was booting through UEFI and your boot is through BIOS and this is why your/mine output differed. 

I have now tested a VM with BIOS F40 with with this PR https://src.fedoraproject.org/rpms/grub2/pull-request/90 and I am not seeing anymore the problem reported. In case you want to try it yourself, here are the RPM files https://koji.fedoraproject.org/koji/taskinfo?taskID=118051103

(In reply to Leo Sandoval from comment #6)
> (In reply to Christoph Karl from comment #4)
> > Just rerun once more.
> > I am using the following kickstart file: See attached.
> > virt-install \
> >   --name fedora40 \
> >   --vcpus 2 \
> >   --memory 4096 \
> >   --disk vol=m2ssd/fedora40 \
> >   --os-variant fedora39 \
> >   --network bridge=virbr0 \
> >   --mac=52:54:00:13:9d:9d \
> >   --graphics vnc,listen=127.0.0.1,port=5940 \
> >   --location
> > /mnt/lager/ARCHIVE/DATEN-MD5/Fedora-Everything-netinst-x86_64-40-1.14.iso \
> >   --noautoconsole \
> >   --initrd-inject=./fedora40-ks.cfg \
> >   --extra-args "inst.ks=file:/fedora40-ks.cfg"
> > 
> > My output is:
> > [ckarl@fc40 ~]$ sudo rpm -Vaq
> > .....UG..  g /var/run/avahi-daemon
> > .M.......  c /etc/audit/rules.d/audit.rules
> > .M.......  c /boot/grub2/grub.cfg
> 
> I was booting through UEFI and your boot is through BIOS and this is why
> your/mine output differed. 
> 
> I have now tested a VM with BIOS F40 with with this PR
> https://src.fedoraproject.org/rpms/grub2/pull-request/90 and I am not seeing

I meant https://src.fedoraproject.org/rpms/grub2/pull-request/87 (I closed 88, 89 and 90 PRs; for some reason I created one PR (87) and 3 more were created..)

> anymore the problem reported. In case you want to try it yourself, here are
> the RPM files https://koji.fedoraproject.org/koji/taskinfo?taskID=118051103

FEDORA-2024-a7983d1f0a (grub2-2.06-123.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-a7983d1f0a

FEDORA-2024-a7983d1f0a has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-a7983d1f0a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-a7983d1f0a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Works for me in fc40. Thank you

FEDORA-2024-a7983d1f0a (grub2-2.06-123.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.