Prior to Enterprise Linux 9, it seems some Red Hat based distros returned
"redhat-based" for inspect-get-distro
This allowed things like "virt-customize --firstboot-command" to work as this
matched the supported distro list, e.g.
|
"fedora"|"rhel"|"centos"|"scientificlinux"|"oraclelinux"|"redhat-based"
However, it seems some distros, e.g. Rocky9 and AlmaLinux9 are now returning
"rocky"/"almalinux" for inspect-get-distro
When using virt-install and then virt-customize, I am seeing issues like the following:
[Rocky9]$ virt-customize -a disk.qcow2 --firstboot-command /tmp/bootstrap
[ 0.0] Examining the guest ...
[ 17.1] Setting a random seed
[ 17.3] Installing firstboot command: /tmp/bootstrap
virt-customize: error: guest type rocky is not supported
Is there some way to return "redhat-based" again for inspect-get-distro or does
the distro list matching need to be updated?
I possibly updated the OS database (osinfo-query os) to support newer OS - is this related
to this problem?
Harry
Harry Bryson | Software Engineer
Harry.Bryson(a)corero.com <mailto:Harry.Bryson@corero.com>
53 Hanover Street, Edinburgh, EH2 2PJ United Kingdom
Access Corero Network Security?s Privacy Policy here <
www.corero.com/privacy>.
We are Corero Network Security plc (?Corero?), registered in England and Wales, with
registered company number 02662978, registered office address Regus House Highbridge,
Oxford Road, Uxbridge, Middlesex, UB8 1HR. Corero is the parent company for Corero Network
Security, Inc. and Corero Network Security (UK) Ltd (a company registered in England and
Wales with registered number 04047090, with the same registered office address as above)
For information about how we process your data, or to manage your data preferences, click
here <
info.corero.com/data-preferences.html>.