Bug 2144105

This iso is created by pungi, so moving there. 

Added Adam to CC since I think this is something we tested?

Well, I'm not sure exactly what Leon's doing here. What's the significance of the `isoinfo` command? Is this something `virt-install` runs? What are the exact actual `virt-install` commands being used here?

We don't test virt-install using the ISO image, no. We use virt-install to create the base disk images openQA uses for testing - this isn't really a "test" per se, but I would probably notice if that broke (although if it fails we just keep using the old image, so I might not notice for a while...). However, that doesn't use ISOs as a base, we use `--location` and point it to an install tree for the release. So if this is specific to using virt-install with an ISO there's nothing we do that would necessarily catch that, no.

The most likely cause of this is https://fedoraproject.org/wiki/Changes/BIOSBootISOWithGrub2 , btw, but I thought we already fixed virt-install's issues with this in https://bugzilla.redhat.com/show_bug.cgi?id=2103835 . maybe there's a path we missed there.

Forget to mention that the environment is a RHEL8 Workstation ... not sure if that is fixed there.

- isoinfo apparently used by virt-install as above showed by the output of virt-install. 

- virt-install used with "--location /srv/pool/Distros/Fedora-Server-dvd-x86_64-37-1.7.iso".
  This has worked for me with F28-36 isos. Did a F36 vm kickstart install right now.

It looks like the problem is caused by missing Joliet tree on the DVD.
Xorriso does not create it automatically and the option for it was not used.
The fix is rather straighforward: https://pagure.io/pungi/pull-request/1642

Ah, hmm. Well, that will fix it for future releases, but it of course will not fix it for the F37 release images, which will be around for some time. We might need to see if virt-install can come up with some kind of workaround for those images, I suppose.

Thanks. What about the second part of the ticket. 

 ERROR    Couldn't find kernel for install tree.

The same virt-install cli line works with F36 but with F37 the above aborting error appears. 

Does this have to do with a dropped Bios boot support? I do not see any isolinux directory in the F37 image anymore.

I tried to add "--boot uefi" but the same error message. So, quite confusing. Any hints?

The pungi release containing the fix is waiting in the Bodhi:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-7129e598e3
https://bodhi.fedoraproject.org/updates/FEDORA-2022-4ef522eb04

(In reply to Leon Fauster from comment #7)
> Thanks. What about the second part of the ticket. 
> 
>  ERROR    Couldn't find kernel for install tree.
> 
> The same virt-install cli line works with F36 but with F37 the above
> aborting error appears. 
> 
> Does this have to do with a dropped Bios boot support? I do not see any
> isolinux directory in the F37 image anymore.
> 
> I tried to add "--boot uefi" but the same error message. So, quite
> confusing. Any hints?

I think the problem here is that the Fedora-Server-netinst-x86_64-37-1.7.iso doesn't have a .treeinfo file embedded in it. This wouldn't matter if libosinfo had the right location for the kernel and initrd but it doesn't (it needs to be fixed): https://gitlab.com/libosinfo/osinfo-db/-/blob/5b7bb778fb076ea1e9e76e2c89fd587669c71ff3/data/os/fedoraproject.org/fedora-37.xml.in#L66

Try specifying directly where to find the kernel and initrd:

```
--location /path/to/Fedora-Server-netinst-x86_64-37-1.7.iso,kernel=images/pxeboot/vmlinuz,initrd=images/pxeboot/initrd.img
```

This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.