Bug 1219851

Summary:	Same volume-id on all F22 ISOs
Product:	[Fedora] Fedora	Reporter:	Zeeshan Ali <zeenix>
Component:	distribution	Assignee:	Václav Pavlín <vpavlin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	dennis, mattdm, mclasen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 14:02:06 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:

Description Zeeshan Ali 2015-05-08 13:23:33 UTC

While I was crying about same volume-id on full DVD and netinst (bug#1180269) in F21, it seems things have turned towards worse for me than better since *all* F22 ISOs share the same volume-id. While we now have means to differentiate ISOs based on size of the volume in libosinfo (and therefore Boxes/virt-manager), I can't already use that mechanism since the volume-size of final ISOs will most certainly be different than Beta ones.

Fortunately it seems the release is happening soon but I would have prefered to add support for F22 before its released, not after.

Comment 1 Matthew Miller 2015-05-08 13:56:59 UTC

See releng ticket https://fedorahosted.org/rel-eng/ticket/6173

Comment 2 Zeeshan Ali 2015-10-24 13:47:09 UTC

Still the same in F23. :(

Comment 3 Fedora End Of Life 2016-07-19 14:02:06 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.