| Summary: | Outdated OS versions for new virtual machines | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Audrey Yeena Toskin <audrey> |
| Component: | osinfo-db | Assignee: | Daniel Berrangé <berrange> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | berrange, cfergeau, crobinso, fidencio, virt-maint, zeeshanak |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-12-29 20:48:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Audrey Yeena Toskin
2016-10-24 21:54:32 UTC
This info comes from libosinfo. In fedora 25 and later the package has been split, so the library is decoupled from the OS database, making it easier to update the os info and keep it up to date. So this should be getting better with f25+, but we didn't build that new version for f24 yet The issue persists with libosinfo 1.0.0 (and virt-manager 1.4.0) on Fedora 25. Which distros exactly are missing? They have to be added manually, so yes, this tends to lag behind a bit. Ubuntu 16.10/Fedora 25 seem to be missing, are these the ones you noted? There's a build of osinfo-db that's still waiting to be pushed to stable that should cover all the missing distros: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ba3e72c511 This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Still doesn't list the latest stable Fedora (27) or Ubuntu (16.10) oops, I meant Ubuntu 17.10, obviously. This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'. Is there any way we could automate the list of available distro releases? (In reply to Andrew Toskin from comment #10) > Is there any way we could automate the list of available distro releases? Unfortunately no. May I close this bug as CURRENT_RELEASE? Both Fedora and Ubuntu info are up-to-date in the last few builds. We could possibly use release-monitoring.org to monitor distro releases? That's designed around watching releases for individual packages, though, and I'm not quite sure how we'd synthesize the information for osinfo-db... Maybe some kind of IfTTT.com script? If those don't work out, then I guess yeah, close this issue. |