#meeting-3:fedoraproject.org log

<@jnsamyak:matrix.org>

17:01:58

!startmeeting RELENG (2024-02-06)

<@meetbot:fedora.im>

17:02:00

Meeting started at 2024-02-06 17:01:58 UTC

<@meetbot:fedora.im>

17:02:00

The Meeting name is 'RELENG (2024-02-06)'

<@jnsamyak:matrix.org>

17:02:10

!meetingname releng

<@jnsamyak:matrix.org>

17:02:16

!chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec jnsamyak patrikp

<@jnsamyak:matrix.org>

17:02:21

!info Meeting is 60 minutes MAX. At the end of 60, it stop

<@nirik:matrix.scrye.com>

17:02:23

morning

<@jnsamyak:matrix.org>

17:02:28

!info agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw

<@jnsamyak:matrix.org>

17:02:34

!topic init process

<@patrikp:matrix.org>

17:02:36

Hello to all.

<@jnsamyak:matrix.org>

17:02:50

So i came up with this agenda which is basically releng meeting template

<@nirik:matrix.scrye.com>

17:03:20

cool. ;)

<@jnsamyak:matrix.org>

17:03:32

so in case folks others want to run they can and changes are welcome

<@jnsamyak:matrix.org>

17:05:06

So last week we finally finished mass rebuild, and the branching is suppose to happen in Feb 20!

<@jnsamyak:matrix.org>

17:05:18

regarding release process^

<@nirik:matrix.scrye.com>

17:06:11

yeah. Time flys

<@jnsamyak:matrix.org>

17:06:30

:o hope the branching is not crazy as rebuild

<@nirik:matrix.scrye.com>

17:07:41

yeah, me too, but sadly, branching is where we hit the most problems it seems like.

<@jnsamyak:matrix.org>

17:07:48

nirik: do you have something to bring up specifically for the init process? Otherwise we can discuss onto the tickets item

<@jnsamyak:matrix.org>

17:08:01

yeah that's why I'm worried but as always we will get thru

<@nirik:matrix.scrye.com>

17:08:34

I plan after the mass updates/reboots tomorrow to start resigning everything with f41 key (so we are ready for branching). I think there's a schedule milestone for that...

<@jnsamyak:matrix.org>

17:10:14

okay I have one thing to ask, is there a process where we have to ask for key access to do &tuff? I remember vaguely but last time i found out people are added or given access in order to process some tasks

<@nirik:matrix.scrye.com>

17:11:14

you can just ask me, or I guess an infra ticket if you need access to do something...

<@jnsamyak:matrix.org>

17:12:25

Okay just wanted to know if there is a formal process to follow because i remeber we need to add the keys to ansible repo robosignotry files etc

<@jnsamyak:matrix.org>

17:12:49

that's all, we can move on to next topic if nothing else!

<@nirik:matrix.scrye.com>

17:14:41

ah, you mean signing keys?

<@jnsamyak:matrix.org>

17:14:48

yes :P

<@nirik:matrix.scrye.com>

17:15:08

I can get you setup there if you aren't already, but yeah...

<@jnsamyak:matrix.org>

17:16:05

yes pls, if there is anything to do on my side let me know and sounds good to me!

<@jnsamyak:matrix.org>

17:16:11

okay moving on

<@jnsamyak:matrix.org>

17:16:12

!topic Tickets needing attention

<@jnsamyak:matrix.org>

17:16:44

!info this is the time where you can bring releng tickets to discuss if there are blockers etc

<@nirik:matrix.scrye.com>

17:19:10

lets see...

<@jnsamyak:matrix.org>

17:19:19

I can start - I have one from my assigned ticket

<@jnsamyak:matrix.org>

17:19:25

!releng 11782

<@zodbot:fedora.im>

17:19:26

**releng #11782** (https://pagure.io/releng/issue/11782):**Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration** ● **Opened:** 3 months ago by raravind ● **Last Updated:** 3 months ago ● **Assignee:** jnsamyak

<@jnsamyak:matrix.org>

17:20:17

So here the request was to create a dedicated fas account, but fas account should be directed to a mailing list - bootloader-eng-team@redhat.com

<@nirik:matrix.scrye.com>

17:20:21

um, ok...

<@nirik:matrix.scrye.com>

17:20:33

yeah, it really should be a group I think

<@jnsamyak:matrix.org>

17:20:54

I guess so as well but then they pointed out to an example which is this

<@jnsamyak:matrix.org>

17:21:01

https://src.fedoraproject.org/rpms/anaconda

<@nirik:matrix.scrye.com>

17:21:07

https://docs.fedoraproject.org/en-US/infra/howtos/groups_in_fedora/

<@jnsamyak:matrix.org>

17:21:27

(anaconda-maint) <<<< is the mailing list assigned

<@nirik:matrix.scrye.com>

17:21:43

yeah... this I think it's a holdover from the old fas days...

<@jnsamyak:matrix.org>

17:22:12

also this needs to be in sysadmin-main correct inorder to create an user or group to get accerss IPA?

<@nirik:matrix.scrye.com>

17:23:16

ah... I see... ok.

<@nirik:matrix.scrye.com>

17:24:56

well, anyone could create the initial account, but then needs someone to add it to packager and change the address on it to the list, then login once to src.fedoraproject.org with it so it knows it's in packager and exists and finally give those packages to it.

<@nirik:matrix.scrye.com>

17:25:09

so, it's complicated sadly.

<@nirik:matrix.scrye.com>

17:26:04

so, perhaps we could both do it? if you can make the account initially with some email, I can add it to packager and change the address and you can then loign to src and reassign the packages?

<@jnsamyak:matrix.org>

17:27:12

ok i'll follow up with you on that

<@jnsamyak:matrix.org>

17:27:23

thanks that's all from my list of tickets

<@nirik:matrix.scrye.com>

17:27:39

ok, I have a few I think...

<@jnsamyak:matrix.org>

17:27:47

shooooot :D

<@nirik:matrix.scrye.com>

17:27:57

Well, there's a pile of unretires waiting. ;(

<@nirik:matrix.scrye.com>

17:28:05

I have had 0 time to look at them even

<@jnsamyak:matrix.org>

17:28:59

nirik: yeah so i am disabled in that matter, can we soooner rather than later set me up with pdc token and database so i can learn processing them?

<@jnsamyak:matrix.org>

17:29:22

I have 1:1 with jednorozec tomorrow i can ask him for his secret script :3

<@nirik:matrix.scrye.com>

17:29:25

Yep. Happy to do so... just let me know when

<@jnsamyak:matrix.org>

17:29:58

also Anton Medvedev was/is working on automating this but i guess that needs some changes and testing; lies in staging atm

<@nirik:matrix.scrye.com>

17:30:13

There is a SOP I think. Just check that the package has been retired less than 8 weeks or has a re-review, then run the pdc script, give the package on src and unblock in koji.

<@nirik:matrix.scrye.com>

17:30:35

yeah, I think the automation was getting close, will be nice when thats there.

<@jnsamyak:matrix.org>

17:30:55

here's the sop: https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/sop_unretire/#_unretiring_a_package_branch

<@nirik:matrix.scrye.com>

17:31:13

I think you should have perms for the unblocking and reassigning, just missing the pdc token? or ?

<@jnsamyak:matrix.org>

17:31:55

nirik: I hopefully will be awake for sometime after the meeting so i can start looking into it

<@jnsamyak:matrix.org>

17:32:10

yep i guess just the pdc token

<@jnsamyak:matrix.org>

17:32:52

but i can take one less impact ticket as my guinea pig

<@jnsamyak:matrix.org>

17:33:04

and figure out from there

<@nirik:matrix.scrye.com>

17:33:21

So, for the pdc token, I think it explains there how to get it?

<@nirik:matrix.scrye.com>

17:33:31

once you have one, I can give it perms in the db.

<@jnsamyak:matrix.org>

17:33:45

done will try it out

<@jnsamyak:matrix.org>

17:33:54

https://pagure.io/releng/issues?status=Open&search_pattern=unretire&close_status= 12 tickets almost

<@nirik:matrix.scrye.com>

17:34:02

or any sysadmin-mainer can via: https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/pdc/#_adding_superusers

<@nirik:matrix.scrye.com>

17:34:39

yeah, they are piling up. ;) Also... if someone files one and needs to do a re-review... IMHO we should close those... ask them to refile or reopen when the review is done.

<@nirik:matrix.scrye.com>

17:35:15

!releng 11932

<@zodbot:fedora.im>

17:35:16

**releng #11932** (https://pagure.io/releng/issue/11932):**dozens of f39 builds mis-tagged, getting ejected from f39-stable bodhi pushes** ● **Opened:** a day ago by decathorpe ● **Last Updated:** an hour ago ● **Assignee:** Not Assigned

<@jnsamyak:matrix.org>

17:35:31

+1; I need to check on sop once when they need to have a review or when it's fine

<@nirik:matrix.scrye.com>

17:35:36

I tried to fix this last night, but it didn't take. ;) Will try and figure it out today.

<@nirik:matrix.scrye.com>

17:36:14

Thats all off hand for tickets I think from me... there's some f40 changes we should look at sometime

<@jnsamyak:matrix.org>

17:37:35

okay I'll move on to the next topic we can discuss there

<@jnsamyak:matrix.org>

17:37:45

!topic Discussion / All other Business / Blockers

<@jnsamyak:matrix.org>

17:38:37

changes in the releng tracker are here: https://pagure.io/releng/issues?status=Open&tags=changes&tags=f40&close_status=

<@jnsamyak:matrix.org>

17:40:35

also nirik i remember you wanted to talk about "builders and new koji" we can take this now as well

<@nirik:matrix.scrye.com>

17:41:16

ok. The f40 mass rebuild tracker ticket can likely be closed?

<@jnsamyak:matrix.org>

17:41:27

<@nirik:matrix.scrye.com>

17:43:08

So, there's a new upstream version of koji (1.34). I am trying to get it rolled out in staging and keep hitting things. I was hoping to update production tomorrow in the mass update, but now I am not sure thats a good idea. ;) Also the builders are still on f38. we kept them on f38 because createrepo_c breaks epel7... but I have made a old createrepo_c package that overrides the f39 one... so I think it should be ok to move them to f39 tomorrow in the mass updates... or perhaps do some today and make sure they are ok first....

<@jnsamyak:matrix.org>

17:44:24

i guess now will be a good time to do it since we are finished with re building stuff?

<@amedvede:fedora.im>

17:45:40

Hello guys, I wanted to discuss one thing, correct me if I'm mistaking. Today I was testing the automation that was discussed here and noticed that staging server doesn't send messages, I don't see any of them in toddler logs for stg and in Datagrepper there is also no messages when I'm trying to check staging topic e.g.: https://apps.fedoraproject.org/datagrepper/v2/search?topic=io.pagure.stg.pagure.issue.new but if you'll change stg to prod it will show messages correctly

<@nirik:matrix.scrye.com>

17:47:02

could be something broken on pagure-stg... or... should you be looking in apps.stg.fedoraproject.org/datagrepper?

<@nirik:matrix.scrye.com>

17:49:15

I restarted things there, can you try a new test?

<@amedvede:fedora.im>

17:49:59

I tried to look in apps.stg.fedoraproject.org/datagrepper but it not working as well. for example here the latest messages were 17 hours ago https://apps.stg.fedoraproject.org/datagrepper/v2/search?rows_per_page=1

<@amedvede:fedora.im>

17:50:04

sure i will try it now

<@nirik:matrix.scrye.com>

17:51:28

huh... yeah, looking. perhaps my reboots messed up something there.

<@amedvede:fedora.im>

17:53:41

ticket was created but still no messages recieved( Anyway i already planned to finish work for today and go to read book, so we will fix it tomorrow

<@nirik:matrix.scrye.com>

17:55:01

yeah, it's hosed. ;) Looking more...

<@nirik:matrix.scrye.com>

17:55:11

hopefully I can get it working and you can look tomorrow

<@nirik:matrix.scrye.com>

17:56:11

it seems like datanommer isn't inserting into the db, but it's running... so weird.

<@nirik:matrix.scrye.com>

17:57:38

anyhow, I can look more after meeting. ;)

<@amedvede:fedora.im>

17:57:51

That would be great! see you tomorrow, take care ;)

<@nirik:matrix.scrye.com>

17:58:44

have a good one/book. ;)

<@jnsamyak:matrix.org>

18:00:18

folks we are almost at time

<@jnsamyak:matrix.org>

18:00:28

!info Thank you all for coming.

<@jnsamyak:matrix.org>

18:00:44

!endmeeting