Bug 2055346

Summary:	Fedora IoT 36 /etc/os-release shows incomplete VERSION and PRETTY_NAME
Product:	[Fedora] Fedora	Reporter:	Geoffrey Marr <gmarr>
Component:	IoT	Assignee:	Peter Robinson <pbrobinson>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	awilliam, dustymabe, gmarr, jonathan, lucab, miabbott, robatino, robertthomasfairley, travier, walters
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	RejectedBlocker
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-02 17:26:42 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1269538

Description Geoffrey Marr 2022-02-16 18:12:39 UTC

Description of problem:
As found in OpenQA [0][1], /etc/os-release VERSION and PRETTY_NAME do not include the date after "36".

[0] https://openqa.fedoraproject.org/tests/1129446#step/os_release/32
[1] https://openqa.fedoraproject.org/tests/1132002#step/os_release/32


Version-Release number of selected component (if applicable):
Fedora-IoT-36-20220214.0
Fedora-IoT-36-20220216.0

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora-IoT-36-20220214.0 or Fedora-IoT-36-20220216.0, any arch.
2. 'cat /etc/os-release'
3. View VERSION and PRETTY_NAME

Comment 1 Fedora Blocker Bugs Application 2022-02-16 20:36:46 UTC

Proposed as a Blocker for 36-final by Fedora user coremodule using the blocker tracking app because:

 Proposing as a potential violation of the following F36 Final criterion [0]:

"For each Edition... the relevant fields in /etc/os-release must include the correct Edition name."

[0] https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Self-identification

Comment 2 Adam Williamson 2022-02-18 20:28:43 UTC

Yeah, I wasn't actually sure whether this was an intentional change or not, but I forgot to file it - thanks for doing so, Geoff.

Comment 3 Geoffrey Marr 2022-02-21 16:36:42 UTC

The decision to classify this bug as a "RejectedBlocker (Final)" was made based off votes here: [0]

https://pagure.io/fedora-qa/blocker-review/issue/615

Comment 4 Luca BRUNO 2022-02-22 09:06:03 UTC

Moving to fedora-iot, I think it's the treefile at https://pagure.io/fedora-iot/ostree/blob/f36/f/fedora-iot-base.json which has not been updated for F36.

Comment 5 Peter Robinson 2022-02-23 20:24:11 UTC

So I think this should be fixed with 36.20220223.0 when it's finished shortly can you verify.

Comment 6 Geoffrey Marr 2022-03-02 17:26:42 UTC

Looks good to me, checked on 20220302.0 and looks as it should. Thanks pbrobinson.