#6173: Same volume-id on all F22 ISOs -----------------------------+------------------------ Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 22 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I was informed that this is where I need for file these bugs so I'll be filing issues for each of the "distribution" bugs I've filed on Fedora bz. This one if against:
https://bugzilla.redhat.com/show_bug.cgi?id=1219851
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.
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 22 Final | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by sgallagh):
To be clear, what you are asking for is that, when generating the ISO container file from the composed tree, we should be producing a unique volume-id for each of the editions and spins, correct?
What format would you want this string to take?
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+----------------------- Changes (by mattdm):
* milestone: Fedora 22 Final => Fedora 23 Alpha
Comment:
This seems reasonable, but I'm afraid we've probably missed the boat for Fedora 22 here. I know it's not ideal, but as https://bugzilla.redhat.com/show_bug.cgi?id=1180269#c4 notes, it's not an easy fix.
I'm going to target this at F23. And again referring back to the not- quite-an-easy-fix situation, if you have patches for Anaconda (or can convince an Anaconda developer of the importance) that'd probably significantly accelerate things.
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by mattdm):
It might also help to file a F23 change — https://fedoraproject.org/wiki/Changes/Policy
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by ausil):
this request is way too late to do anything about for F22. Tooling chnages now risk us having to slip the release. It may not be something that is changeable. you do not provide enopugh information as to what you are seeing. for one the boot.iso and install DVD have to have the same ID. the ID's on livecds should already be different and nothing changed in them in F22 from F21. as to the install media, we have a boot,iso for each of the 3 products, but only a install DVD for Server. I honestly am not 100% sure what Issues you are seeing. So I for one would appreciate some extra information.
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by zeenix):
In F21, we had at least different volume-id on different variants, server, workstation and cloud. The https://bugzilla.redhat.com/show_bug.cgi?id=1180269#c4 is about netiso vs full installer DVD so while I'd understand if things had remained the same, I'm puzzled as to why this problem is expanding to all ISOs now. Even microsoft ensures that there is a unique volume-id on each of their ISO.
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by zeenix):
Replying to [comment:4 ausil]:
you do not provide enopugh information as to what you are seeing.
I guess a look into F21 media info in our OS database might help you understand:
https://git.fedorahosted.org/cgit/libosinfo.git/tree/data/oses/fedora.xml.in... https://git.fedorahosted.org/cgit/libosinfo.git/tree/data/oses/fedora.xml.in... https://git.fedorahosted.org/cgit/libosinfo.git/tree/data/oses/fedora.xml.in...
Notice the different volume-id pattern for each of the ISO (except netiso and full installer)? That's what is missing in F22 ISOs.
#6173: Same volume-id on all F22 ISOs ------------------------------+----------------------- Reporter: zeenix | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Alpha | Component: koji Resolution: | Keywords: Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by ausil):
Replying to [comment:5 zeenix]:
In F21, we had at least different volume-id on different variants,
server, workstation and cloud. The https://bugzilla.redhat.com/show_bug.cgi?id=1180269#c4 is about netiso vs full installer DVD so while I'd understand if things had remained the same, I'm puzzled as to why this problem is expanding to all ISOs now. Even microsoft ensures that there is a unique volume-id on each of their ISO.
Workstation had no install isos in F21. they only had a live.
{{{ [ausil@compose-x86-01 ~]$ blkid /mnt/fedora_koji/compose/22_TC3/22_TC3/*/x86_64/iso/Fedora-*iso /mnt/fedora_koji/compose/22_TC3/22_TC3/Cloud_Atomic/x86_64/iso/Fedora- Cloud_Atomic-x86_64-22_TC3.iso: UUID="2015-05-08-02-24-09-00" LABEL="Fedora-22-x86_64" TYPE="iso9660" PTUUID="53968acb" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Cloud/x86_64/iso/Fedora-Cloud- netinst-x86_64-22_TC3.iso: UUID="2015-05-08-07-11-56-00" LABEL="Fedora- 22_T3-x86_64" TYPE="iso9660" PTUUID="2e553da7" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Server/x86_64/iso/Fedora-Server- DVD-x86_64-22_TC3.iso: UUID="2015-05-08-06-59-49-00" LABEL="Fedora- 22_T3-x86_64" TYPE="iso9660" PTUUID="11906394" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Server/x86_64/iso/Fedora-Server- netinst-x86_64-22_TC3.iso: UUID="2015-05-08-06-59-12-00" LABEL="Fedora- 22_T3-x86_64" TYPE="iso9660" PTUUID="36ef7148" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Workstation/x86_64/iso/Fedora-Live- Workstation-x86_64-22-TC3.iso: UUID="2015-05-08-02-27-29-00" LABEL ="Fedora-Live-WS-x86_64-22-T3" TYPE="iso9660" PTUUID="7ec4ab46" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Workstation/x86_64/iso/Fedora- Workstation-netinst-x86_64-22_TC3.iso: UUID="2015-05-08-06-49-14-00" LABEL ="Fedora-22_T3-x86_64" TYPE="iso9660" PTUUID="3bf61992" PTTYPE="dos" [ausil@compose-x86-01 ~]$ blkid /mnt/fedora_koji/compose/22_TC3/22_TC3/*/x86_64/Fedora-*iso /mnt/fedora_koji/compose/22_TC3/22_TC3/Live/x86_64/Fedora-Live-KDE- x86_64-22-TC3.iso: UUID="2015-05-08-02-22-48-00" LABEL="Fedora-Live-KDE- x86_64-22-T3" TYPE="iso9660" PTUUID="6ae4427b" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Live/x86_64/Fedora-Live-LXDE- x86_64-22-TC3.iso: UUID="2015-05-08-02-15-07-00" LABEL="Fedora-Live-LXDE- x86_64-22-T3" TYPE="iso9660" PTUUID="7bea4056" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Live/x86_64/Fedora-Live- MATE_Compiz-x86_64-22-TC3.iso: UUID="2015-05-08-02-17-58-00" LABEL ="Fedora-Live-MATE-x86_64-22-T3" TYPE="iso9660" PTUUID="20776222" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Live/x86_64/Fedora-Live-SoaS- x86_64-22-TC3.iso: UUID="2015-05-08-02-13-20-00" LABEL="Fedora-Live-SoaS- x86_64-22-T3" TYPE="iso9660" PTUUID="2c4d9655" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Live/x86_64/Fedora-Live-Xfce- x86_64-22-TC3.iso: UUID="2015-05-08-02-19-24-00" LABEL="Fedora-Live-Xfce- x86_64-22-T3" TYPE="iso9660" PTUUID="247c7cf7" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Spins/x86_64/Fedora-Live- Design_suite-x86_64-22-TC3.iso: UUID="2015-05-08-02-27-39-00" LABEL ="Fedora-Live-Dsgn-x86_64-22-T3" TYPE="iso9660" PTUUID="53e83304" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Spins/x86_64/Fedora-Live-Games- x86_64-22-TC3.iso: UUID="2015-05-08-02-55-19-00" LABEL="Fedora-Live-Game- x86_64-22-T3" TYPE="iso9660" PTUUID="78f3b5ed" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Spins/x86_64/Fedora-Live-Jam_KDE- x86_64-22-TC3.iso: UUID="2015-05-08-02-39-41-00" LABEL="Fedora-Live-Jam- x86_64-22-T3" TYPE="iso9660" PTUUID="663b35ef" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Spins/x86_64/Fedora-Live-Robotics- x86_64-22-TC3.iso: UUID="2015-05-08-02-28-57-00" LABEL="Fedora-Live-Robo- x86_64-22-T3" TYPE="iso9660" PTUUID="148bab0b" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Spins/x86_64/Fedora-Live- Scientific_KDE-x86_64-22-TC3.iso: UUID="2015-05-08-02-48-53-00" LABEL ="Fedora-Live-SciK-x86_64-22-T3" TYPE="iso9660" PTUUID="73c0f803" PTTYPE="dos" /mnt/fedora_koji/compose/22_TC3/22_TC3/Spins/x86_64/Fedora-Live-Security- x86_64-22-TC3.iso: UUID="2015-05-08-02-18-32-00" LABEL="Fedora-Live-Sec- x86_64-22-T3" TYPE="iso9660" PTUUID="156b3ce6" PTTYPE="dos" }}}
the installer trees I guess all have the same label. however it is too late to make changes to the tooling for f22. note that workstation and cloud only have a boot.iso so if it is a dvd then it is Server being installed. for Cloud and Workstation you have to do a network install using the boot.iso you are probably better off actually just grabbing the kernel and initrd and pointing it at the right install tree for the product you are installing.
rel-eng@lists.fedoraproject.org