<@jnsamyak:matrix.org>
16:00:06
!startmeeting RELENG (2025-03-17)
<@meetbot:fedora.im>
16:00:15
Meeting started at 2025-03-17 16:00:06 UTC
<@meetbot:fedora.im>
16:00:15
The Meeting name is 'RELENG (2025-03-17)'
<@smilner:fedora.im>
16:00:18
!hi
<@zodbot:fedora.im>
16:00:19
None (smilner)
<@patrikp:matrix.org>
16:00:24
Hello. 👋
<@jnsamyak:matrix.org>
16:00:32
!meetingname releng
<@meetbot:fedora.im>
16:00:33
The Meeting Name is now releng
<@jnsamyak:matrix.org>
16:00:39
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@jnsamyak:matrix.org>
16:00:39
!chair nirik jnsamyak patrikp amedvede
<@jnsamyak:matrix.org>
16:00:39
!info Meeting is 60 minutes MAX. At the end of 60, it stops.
<@jnsamyak:matrix.org>
16:00:56
Hello everyone, how is power rangers doing today?
<@patrikp:matrix.org>
16:01:23
Could be worse.
<@smilner:fedora.im>
16:02:42
I can't find where I parked the Mega Dragonzord.
<@jnsamyak:matrix.org>
16:03:16
⚔️
<@jnsamyak:matrix.org>
16:03:26
!topic Init process.
<@jnsamyak:matrix.org>
16:03:32
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@jnsamyak:matrix.org>
16:03:43
!info Fedora 42 Beta will be released tomorrow!
<@patrikp:matrix.org>
16:04:48
I wanted to ask about this in the next section but I guess now is as good a time as any... What are the tasks that will have to be done tomorrow, on Release Day? We went over pretty much the entire "Beta Release SOP" on Friday and I can't see another SOP about next steps.
<@nirik:matrix.scrye.com>
16:05:15
morning
<@jnsamyak:matrix.org>
16:05:24
The steps left are to make the beta publicly available
<@patrikp:matrix.org>
16:05:24
!link https://docs.fedoraproject.org/en-US/infra/release_guide/beta_release/
<@nirik:matrix.scrye.com>
16:05:33
we need to do torrents today!
<@jnsamyak:matrix.org>
16:06:04
that means check about the directory permissions, and make beta torrents and publish them at torrents fpo
<@jnsamyak:matrix.org>
16:06:13
And finally we send an email!
<@nirik:matrix.scrye.com>
16:06:13
The only other thing is opening permissions late tonight. (or early depending on where you are I guess)
<@jnsamyak:matrix.org>
16:07:00
yes I guess my afternoon, patriks morning, and your late night :P
<@patrikp:matrix.org>
16:07:04
!link https://docs.fedoraproject.org/en-US/infra/release_guide/torrentrelease/
<@jnsamyak:matrix.org>
16:07:22
yes
<@jnsamyak:matrix.org>
16:09:26
Anything else? I suppose the openh264 bits are sorted iirc?
<@patrikp:matrix.org>
16:10:15
More or less, yes. But that is a topic for another time.
<@patrikp:matrix.org>
16:10:39
If we want to do the ticket triage today.
<@nirik:matrix.scrye.com>
16:10:52
Did we finish up the retro stuff?
<@patrikp:matrix.org>
16:10:59
I think retro is done.
<@jnsamyak:matrix.org>
16:11:14
Is something else left, if not, we should document the SOP for it?
<@jnsamyak:matrix.org>
16:11:48
nirik: it's done, I'll send out the discussion, and the changes done for it along with the retro document later this week
<@nirik:matrix.scrye.com>
16:11:52
I wasn't sure... we ran out of time last week. ;)
<@nirik:matrix.scrye.com>
16:11:59
ok, great!
<@jnsamyak:matrix.org>
16:11:59
hopefully tomorrow 0/
<@jnsamyak:matrix.org>
16:12:31
Let's move on to the next topic
<@jnsamyak:matrix.org>
16:12:38
!topic Scheduled actions coming up in the next week.
<@jnsamyak:matrix.org>
16:12:48
!info Here we list/discuss anything about items that are due to be done in the next week.
<@jnsamyak:matrix.org>
16:12:55
!link https://fedorapeople.org/groups/schedule/f-43/f-43-releng-tasks.html
<@jnsamyak:matrix.org>
16:12:55
!link https://fedorapeople.org/groups/schedule/f-42/f-42-releng-tasks.html
<@jnsamyak:matrix.org>
16:13:19
We discussed these already
<@jnsamyak:matrix.org>
16:13:32
Beta Torrents needs to go out tomorrow
<@jnsamyak:matrix.org>
16:13:44
and we need to open up beta directory for everyone
<@jnsamyak:matrix.org>
16:13:53
anything else for this topic?
<@nirik:matrix.scrye.com>
16:13:55
torrents today. ;)
<@jnsamyak:matrix.org>
16:14:13
Beta Torrents needs to go out today
<@jnsamyak:matrix.org>
16:14:16
fixed :D
<@nirik:matrix.scrye.com>
16:14:19
but yeah, nothing else
<@patrikp:matrix.org>
16:14:24
And tomorrow we just change permissions on 2 directories?
<@patrikp:matrix.org>
16:14:29
And that's it?
<@jnsamyak:matrix.org>
16:14:35
yes
<@nirik:matrix.scrye.com>
16:16:04
well, 3 directories.
<@nirik:matrix.scrye.com>
16:16:09
and... that reminds me.
<@nirik:matrix.scrye.com>
16:16:55
https://dl.fedoraproject.org/pub/alt/releases/test/
<@nirik:matrix.scrye.com>
16:17:11
that needs cleaning up... we don't need all the old betas there.
<@nirik:matrix.scrye.com>
16:17:16
I think thats missing from the SOP?
<@jnsamyak:matrix.org>
16:17:22
We need to clear out these, after checking with QA?
<@jnsamyak:matrix.org>
16:17:38
I have this added, in the post release clean up
<@nirik:matrix.scrye.com>
16:17:44
they should have been removed at the same time the other ones were, but our SOP doesn't mention that dir...
<@jnsamyak:matrix.org>
16:17:48
but we can do these now as well, not a biggie
<@nirik:matrix.scrye.com>
16:18:04
https://docs.fedoraproject.org/en-US/infra/release_guide/beta_release/#_beta_installation_and_cleanup
<@patrikp:matrix.org>
16:18:06
The SOP could use some touchups.
<@nirik:matrix.scrye.com>
16:18:07
yeah.
<@jnsamyak:matrix.org>
16:18:08
I'll update it
<@nirik:matrix.scrye.com>
16:18:17
thats also the other dir that needs opening. ;)
<@jnsamyak:matrix.org>
16:19:10
patrikp: since you did the staging, would you make the sop changes? I saw there were some changes to be done from the chats on friday for staging mirror?
<@patrikp:matrix.org>
16:19:42
jnsamyak: Yeah, I can take a look... One question. Do you know off the top of your head what group membership is needed for this step in SOP? "Set release in Bodhi to pending"
<@jnsamyak:matrix.org>
16:19:43
if not, i can update it with other doc processes
<@patrikp:matrix.org>
16:19:56
I'm in bodhiadmin and sysadmin-bodhi but it wouldn't run due to permission issues.
<@jnsamyak:matrix.org>
16:20:23
yep that would work!
<@jnsamyak:matrix.org>
16:20:40
Were you running it from a root user?
<@jnsamyak:matrix.org>
16:20:43
or your own?
<@patrikp:matrix.org>
16:21:03
From my local machine...
<@jnsamyak:matrix.org>
16:21:30
it should be done from bodhi-backend machinbe
<@jnsamyak:matrix.org>
16:21:32
it should be done from bodhi-backend machine
<@nirik:matrix.scrye.com>
16:21:40
yeah, puzzling. Also, I ran into problems trying to add patrikp in sigul. ;( I can try and figure that out this week... but we need better docs there for sure.
<@patrikp:matrix.org>
16:21:57
This specific step should? Why?
<@nirik:matrix.scrye.com>
16:22:00
jnsamyak: it should be doable from anywhere. ;) I did it from my laptop
<@jnsamyak:matrix.org>
16:22:40
locally we need to have our client configured no?
<@patrikp:matrix.org>
16:23:32
It's like with Koji, no? Configured how? You have the kerberos ticket and the group membership, is there more that is needed?
<@nirik:matrix.scrye.com>
16:24:01
you need to be logged in with the bodhi cli
<@patrikp:matrix.org>
16:24:20
Ah, maybe I skipped a login step then?
<@jnsamyak:matrix.org>
16:24:22
it was usually annoying for me in the starting since, my user name and hostname so i need to authenticate it using bodhi command line, but I just find it easier
<@jnsamyak:matrix.org>
16:24:25
to do it from machine
<@nirik:matrix.scrye.com>
16:24:34
it should ask if it needs anything to log you in
<@jnsamyak:matrix.org>
16:24:48
maybe if you could set it to pending from the machine, you have the right ACLs
<@patrikp:matrix.org>
16:24:51
And I think it explicitly said "Login successful!" in the output.
<@jnsamyak:matrix.org>
16:24:57
and locally something should be missing
<@patrikp:matrix.org>
16:25:00
I.e. it just logs you in automatically when you run the command.
<@jnsamyak:matrix.org>
16:25:06
so try checki\ng there
<@nirik:matrix.scrye.com>
16:26:19
I'm not sure it would even work right from a remote machine... how would it log you in there?
<@nirik:matrix.scrye.com>
16:26:36
perhaps running with --debug would say more...
<@patrikp:matrix.org>
16:26:36
Yeah, I ran the command and I got this output:
<@patrikp:matrix.org>
16:26:36
Login successful!
<@patrikp:matrix.org>
16:26:36
<@patrikp:matrix.org>
16:26:36
{"status": "error", "errors": [{"location": "body", "name": "HTTPForbidden", "description": "Unauthorized: save_release__POST failed permission check"}]}
<@patrikp:matrix.org>
16:26:42
So it did log me in.
<@nirik:matrix.scrye.com>
16:28:30
and you did try moving ~/.config/bodhi/client.json aside and got the same thing right?
<@patrikp:matrix.org>
16:28:47
Yes.
<@patrikp:matrix.org>
16:29:11
It created a new config file, another login successful and permissions denied.
<@patrikp:matrix.org>
16:30:24
Ideally we'd have the group membership in the SOP too, for future reference, so it'd be good to figure it out.
<@patrikp:matrix.org>
16:30:42
One more question about the checksums. We skipped the step but we should still do it at some point, right?
<@nirik:matrix.scrye.com>
16:31:03
patrikp: can you try making a new user, then logging in from there?
<@nirik:matrix.scrye.com>
16:32:17
Nope, we can just drop that. That step was moving the signed versions of that from the newly copied release (thats closed until tuesday) to the stage area so they could be checked before release, but they no longer need that and can do that checking release morning.
<@patrikp:matrix.org>
16:33:18
How long does it usually take for services (in this case Bodhi) to sync the group membership in some way? It's instantaneous? I get added and it should work instantly? Or is it necessary to wait some period of time?
<@nirik:matrix.scrye.com>
16:33:47
I think it happens on login. So thats what makes me think the problem is that you need to login again somehow to get the new group
<@patrikp:matrix.org>
16:34:08
But I forced a new login by removing the config file, right?
<@nirik:matrix.scrye.com>
16:34:24
yeah, I would have thought so.
<@nirik:matrix.scrye.com>
16:34:44
running it with --debug might show any other files it's reading there?
<@patrikp:matrix.org>
16:35:46
What would be a good command to play around with? I obviously don't want to mess with the F42 release.
<@patrikp:matrix.org>
16:36:14
`$ bodhi releases edit --name F42 --state pending`
<@patrikp:matrix.org>
16:36:14
For reference this is the command that failed for me on Friday:
<@nirik:matrix.scrye.com>
16:37:04
try using F40C (and try and revert / not make major changes) :)
<@nirik:matrix.scrye.com>
16:37:16
its not actually used for anything anymore
<@patrikp:matrix.org>
16:37:26
What's the C stand for?
<@nirik:matrix.scrye.com>
16:37:37
containers.
<@jnsamyak:matrix.org>
16:37:42
nirik: can't we do these change in staging?
<@nirik:matrix.scrye.com>
16:38:00
thats another option, but... might not help since the problem is auth in prod.
<@jnsamyak:matrix.org>
16:38:01
i mean test these changes
<@jnsamyak:matrix.org>
16:38:12
oh yeah makes sense
<@patrikp:matrix.org>
16:38:55
That, and doing things in staging is boring... Let's get the adrenaline going by playing around with prod.
<@patrikp:matrix.org>
16:39:07
I joke.
<@nirik:matrix.scrye.com>
16:39:20
ha
<@jnsamyak:matrix.org>
16:39:55
hehe can we should take this to the channel
<@jnsamyak:matrix.org>
16:40:26
and not hijack meeting for the permissions :P
<@jnsamyak:matrix.org>
16:40:26
Anything else for the release process?
<@patrikp:matrix.org>
16:41:40
Let's do the old tickets triage?
<@jnsamyak:matrix.org>
16:41:43
hehe can we should take this to the releng channel
<@jnsamyak:matrix.org>
16:41:51
!topic Tickets that need attention.
<@nirik:matrix.scrye.com>
16:41:55
sure
<@jnsamyak:matrix.org>
16:41:59
!info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.
<@patrikp:matrix.org>
16:42:37
!link https://pagure.io/releng/issues?status=Open&order_key=date_created&order=asc
<@jnsamyak:matrix.org>
16:42:44
But we decided to go and triage old tickets, so if folks have nothing to important to bring on we will go from bottom to top
<@jnsamyak:matrix.org>
16:43:19
!releng 7083
<@zodbot:fedora.im>
16:43:20
<@zodbot:fedora.im>
16:43:20
● **Assignee:** humaton
<@zodbot:fedora.im>
16:43:20
● **Last Updated:** 2 weeks ago
<@zodbot:fedora.im>
16:43:20
● **Opened:** 7 years ago by till
<@zodbot:fedora.im>
16:43:20
**releng #7083** (https://pagure.io/releng/issue/7083):**orphan-all-packages.py should remove bugzilla_contact entries from fedora-scm-requests as well**
<@patrikp:matrix.org>
16:43:52
No fear, no mercy...
<@nirik:matrix.scrye.com>
16:44:19
close, ask interested people to reopen if it's still wanted.
<@jnsamyak:matrix.org>
16:45:01
I was going through the script 🫠
<@jnsamyak:matrix.org>
16:45:22
we should just open this request to toddlers instead, and ask them to triage it
<@jnsamyak:matrix.org>
16:45:27
if it's relevant
<@jnsamyak:matrix.org>
16:45:29
no?
<@nirik:matrix.scrye.com>
16:46:19
I'm trying to recall what this was for...
<@patrikp:matrix.org>
16:46:42
Same for this one?
<@patrikp:matrix.org>
16:46:49
!releng 8478
<@nirik:matrix.scrye.com>
16:46:53
we are using neither of those tools anymore
<@jnsamyak:matrix.org>
16:47:01
I think it's bugzilla reset asignee which we add in the ui for each package
<@zodbot:fedora.im>
16:47:02
● **Last Updated:** a year ago
<@zodbot:fedora.im>
16:47:02
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:47:02
**releng #8478** (https://pagure.io/releng/issue/8478):**Retired packages should close rawhide bugzilla as WONTFIX or EOL**
<@zodbot:fedora.im>
16:47:02
● **Opened:** 5 years ago by churchyard
<@zodbot:fedora.im>
16:47:02
<@patrikp:matrix.org>
16:47:45
As in, it's a toddlers thing, right?
<@jnsamyak:matrix.org>
16:48:00
let's go one by one in the ticket
<@nirik:matrix.scrye.com>
16:48:10
IMHO on this one I think the idea is overcomplex...
<@jnsamyak:matrix.org>
16:48:18
but yes
<@nirik:matrix.scrye.com>
16:48:22
I guess if someone wanted to work on it, they could...
<@nirik:matrix.scrye.com>
16:48:30
but it would have to:
<@nirik:matrix.scrye.com>
16:49:10
close bugs at retirement and somehow mark them that they were closed for retirememnt, on unretire it would have to find that list, parse it and mail the new maintainer some kind of email with the list.
<@jnsamyak:matrix.org>
16:49:14
Let me close it with the comment if they are interested they should go to toddlers repository for this, and if no one is bothered, perhaps it will be going to grave for good :)
<@nirik:matrix.scrye.com>
16:49:52
sure
<@jnsamyak:matrix.org>
16:51:28
!releng 7520
<@zodbot:fedora.im>
16:51:30
● **Opened:** 6 years ago by till
<@zodbot:fedora.im>
16:51:30
**releng #7520** (https://pagure.io/releng/issue/7520):**Provide stable names for images**
<@zodbot:fedora.im>
16:51:30
<@zodbot:fedora.im>
16:51:30
● **Last Updated:** a month ago
<@zodbot:fedora.im>
16:51:30
● **Assignee:** Not Assigned
<@jnsamyak:matrix.org>
16:52:22
patrikp: i see your last comment, were there any findings?
<@patrikp:matrix.org>
16:52:38
Look above that.
<@patrikp:matrix.org>
16:53:02
`Issue close_status updated to: Can't Fix`
<@patrikp:matrix.org>
16:53:15
I did that perhaps prematurely but it's not something I looked into.
<@smilner:fedora.im>
16:53:18
Looks like the last update was 4 years before where nirik asked Adam and Brian but it stalled.
<@jnsamyak:matrix.org>
16:53:41
:)
<@nirik:matrix.scrye.com>
16:53:57
so yeah, I understand the desire here... but not sure how best to implement it.
<@smilner:fedora.im>
16:54:03
If it's lasted 6 years without movement, is it really that helpful or important? I really don't know :-/
<@nirik:matrix.scrye.com>
16:54:26
yeah, I would think after this time the folks needing it would have figured out workarounds.
<@nirik:matrix.scrye.com>
16:55:25
but perhaps they just don't test those daily images
<@jnsamyak:matrix.org>
16:55:30
nirik: would you be kind and summarise the requirement here please?
<@nirik:matrix.scrye.com>
16:57:06
some CI/testing setups would like to test against rawhide. For this they need to fetch the latest rawhide image(s). But those images change every day, ie, https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Cloud/x86_64/images/Fedora-Cloud-Base-AmazonEC2-Rawhide-20250317.n.0.x86_64.raw.xz with the date in them. So, they want us to provide some way they can just get a 'latest' version to download and use to test with
<@nirik:matrix.scrye.com>
16:57:19
I didn't see much answer about using fedfind.
<@patrikp:matrix.org>
16:57:59
We could try tagging Adam again as he's still around, see what he has to say. And revisit if/when we get a reply.
<@patrikp:matrix.org>
16:58:13
It's entirely possible he just missed the tag years ago.
<@nirik:matrix.scrye.com>
16:58:19
Any hard/soft links would have downsides, and also would need to be done in pungi.
<@jnsamyak:matrix.org>
16:58:26
I will try to look into it
<@jnsamyak:matrix.org>
16:58:50
and share my findings in next weekly
<@nirik:matrix.scrye.com>
16:58:51
mirrormanager could work, but it would mean changing a redirect every day for lots of them, so not sure how practical that is.
<@jnsamyak:matrix.org>
16:59:11
not saying I can implement it but can help groom it
<@nirik:matrix.scrye.com>
16:59:28
also, making a latest could confuse QE efforts.
<@nirik:matrix.scrye.com>
16:59:39
"I downloaded the latest image" "which latest?"
<@jnsamyak:matrix.org>
16:59:53
that's truee
<@nirik:matrix.scrye.com>
17:00:16
anyhow, it would be nice to have, but not sure how we can do it. ;)
<@nirik:matrix.scrye.com>
17:00:18
and we are out of time
<@patrikp:matrix.org>
17:00:45
I would say don't close yet and tag Adam. And we revisit during next triage.
<@jnsamyak:matrix.org>
17:01:02
yeah I will chair next week saves time
<@jnsamyak:matrix.org>
17:01:04
for that
<@jnsamyak:matrix.org>
17:01:17
!topic Choose next chair.
<@jnsamyak:matrix.org>
17:01:17
!info Next chair March 24: Samyak
<@jnsamyak:matrix.org>
17:01:24
!info Thank you all for coming!
<@jnsamyak:matrix.org>
17:01:24
!endmeeting