Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 2243303 - /etc/os-release shows wrong release on x86_64 IoT
Summary: /etc/os-release shows wrong release on x86_64 IoT
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 39
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
Reported: 2023-10-11 17:01 UTC by Geoffrey Marr
Modified: 2023-10-20 08:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-10-20 08:59:32 UTC
Type: ---

Attachments (Terms of Use)

Description Geoffrey Marr 2023-10-11 17:01:58 UTC
Booted Fedora-IoT-ostree-x86_64-39-20231010.0.iso on baremetal. Ran through installer process like normal using defaults and making both a root and user account. Boot into installed system and noticed that the entry in grub showed 20231006 instead of 20231010. Checked /etc/os-release and PRETTY_NAME field shows "Fedora Linux 39.20231006.0 (IoT Edition Prerelease)".

Reproducible: Always

Steps to Reproduce:
1. Install Fedora-IoT-ostree-x86_64-39-20231010.0.iso.
2. Run "cat /etc/os-release"
3. View PRETTY_NAME field.
Actual Results:  
PRETTY_NAME field shows "Fedora Linux 39.20231006.0 (IoT Edition Prerelease)".

Expected Results:  
PRETTY_NAME field shows "Fedora Linux 39.20231010.0 (IoT Edition Prerelease)"

Comment 1 David Tardon 2023-10-20 08:59:32 UTC
/etc/os-release is part of fedora-release package and it's created when the package is built. Hence, the values in os-release are relevant to the date of the last build of fedora-release, not to the date of production of an ostree ISO (which, I assume, happens more often).

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