Provide a way to differentiate Beta vs RC compose in .composeinfo file #9841
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
release-process
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Depends on
Reference
releng/tickets#9841
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The .composeinfo file generated for the Beta and RC doesn't specify which is Beta and which is RC, for those who consume the content using the .composeinfo file, its harder to differentiate what is what.
It would be helpful to provide a way to identify these composes in .composeinfo file
When do you need this? (YYYY/MM/DD)
F34 Beta
If we cannot complete your request, what is the impact?
Its hard to consume the composes and differentiate between them
Metadata Update from @mohanboddu:
When the Beta is released and lands in each of RH Beaker labs it get imported to the pxe menu as 'fedora-33' since it uses .composeinfo for naming. When the GOLD is released it is ignored since it is also identified at 'fedora-33' in the .composeinfo. Someone will request GOLD be imported and that is handled manually. Problem occurs at this point at the pxe is already populated w/ the initrd and kernel from the Beta and is a mismatch w/ GOLD. pxe menu does not get updated as it sees fedora-33 already populated in the menu. The mismatch causes pxe installs / beaker jobs to fail. Clean up is required. This or something similar happens every fedora release. Many hours could be recovered if we only had a distinction in the .composeinfo for the 'name' for Beta and GOLD. Perhaps fedora-33-Beta and Fedora-33.
Safe to say this was not ready by F34 Beta. Is this still something that's needed? If not I recommend we close this.
We are still unable to differentiate the composes based on the .composeinfo file so this is useful feature.
Looking at and discussing this in the refinement call today, we discussed this that we need to update the composeinfo file to show which release it belong to, can work on the nomenclature. but something like below:
release_typefield to.composeinfoso we can tell Beta and Final releases apart. #13029release_typefield to.composeinfoso we can tell Beta and Final releases apart.I think we should try to match the format for RHEL composes here better, there are substantial discrepancies. RHers can access RHEL composes to compare, ping me if you don't know the URL (I'm not sure whether I'm allowed to post it publicly).
Sure thing!
Okay I did my due dilegence and talked over where were things, finally I come up with the workaround, and the output for filetype look like this
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20260710.n.0/compose/.composeinfo
release_typefield to.composeinfoso we can tell Beta and Final releases apart. #13029CC: @lsedlar^
The corresponding pr has been merged, closing this. The actua test in prod will be tested at the time of beta release!