Bug 2277235 - Fedora 43 missing from Operating System list
Summary: Fedora 43 missing from Operating System list
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: osinfo-db
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-25 22:07 UTC by Sergio Belkin
Modified: 2026-02-23 17:13 UTC (History)
10 users (show)

Fixed In Version: osinfo-db-20251212-1.fc43
Clone Of:
Environment:
Last Closed: 2026-02-18 04:24:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sergio Belkin 2024-04-25 22:07:55 UTC
Fedora 40 release is missing from de Operating System List on Virtual Machine dialog box.

Reproducible: Always

Steps to Reproduce:
1.Logon Cockpit
2.Go to Virtual Machines
3.Go to Create a VM
4. Search for Fedora 40 on Operating System combo box
Actual Results:  
Fedora 40 is missing

Expected Results:  
Fedora 40 to be available

Comment 1 Martin Pitt 2024-04-26 04:56:22 UTC
This is taken from libosinfo, so reassigning. It's indeed missing in

   osinfo-query os vendor="Fedora Project"

Comment 2 Aoife Moloney 2024-11-13 12:28:38 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
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 '39'.

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 39 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.

Comment 3 Martin Pitt 2024-11-13 12:52:30 UTC
The same problem still exists in spirit. On current F41 with libosinfo-1.11.0-7.fc41.x86_64, `osinfo-query os vendor="Fedora Project"` has Fedora 40, but not 41.

Comment 4 Adam Williamson 2025-12-02 01:14:46 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
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 '41'.

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 41 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.

Comment 5 Edgar Hoch 2025-12-02 01:24:36 UTC
The problem still exists in Fedora 43. Neither Fedora 42 nor Fedora 43 are listed in "osinfo-query os vendor="Fedora Project".

Please update the Fedora version, and fix this bug. I think is should be simple to add the missing entries. Please also include the next Fedora version.

Comment 6 Samyak Jain (RedHat) 2025-12-16 17:07:39 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 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.

Comment 7 Edgar Hoch 2025-12-16 19:32:23 UTC
Why is this closed? The problem still exists on Fedora 43. See comment 5.

Comment 8 Cole Robinson 2025-12-18 20:30:22 UTC
Autoclosed by bot, reopening

Comment 9 pgaltieri 2025-12-19 19:43:43 UTC
Additionally neither fedora 42 nor fedora 43 is included in osinfo-db on fedora 42.  This makes it inconsistent if one wants to create a fedora 43 VM on fedora 42. I would have to point to a fedora 43 iso and specify an os-variant of fedora41.

virt-install --osinfo list | grep fedora
fedora41
fedora40

Paolo

Comment 10 Fedora Update System 2026-02-02 18:35:04 UTC
FEDORA-2026-130c70f802 (osinfo-db-20251212-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-130c70f802

Comment 11 Fedora Update System 2026-02-03 03:14:08 UTC
FEDORA-2026-130c70f802 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-130c70f802`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-130c70f802

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

Comment 12 Fedora Update System 2026-02-18 04:24:21 UTC
FEDORA-2026-130c70f802 (osinfo-db-20251212-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 pgaltieri 2026-02-23 17:13:01 UTC
I tested it out. The bug is resolved you can close it.


Note You need to log in before you can comment on or make changes to this bug.