Bug 1219851 - Same volume-id on all F22 ISOs
Summary: Same volume-id on all F22 ISOs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Václav Pavlín
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-08 13:23 UTC by Zeeshan Ali
Modified: 2016-09-20 01:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 14:02:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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