15:06:09 <jednorozec> #startmeeting RELENG (2021-08-24)
15:06:09 <zodbot> Meeting started Tue Aug 24 15:06:09 2021 UTC.
15:06:09 <zodbot> This meeting is logged and archived in a public location.
15:06:09 <zodbot> The chair is jednorozec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:06:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:06:09 <zodbot> The meeting name has been set to 'releng_(2021-08-24)'
15:06:14 <jednorozec> #meetingname releng
15:06:14 <zodbot> The meeting name has been set to 'releng'
15:06:27 <jednorozec> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
15:06:27 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
15:06:27 <jednorozec> #topic init process
15:06:48 <nirik> morning
15:07:21 <jednorozec> morning
15:07:36 <jednorozec> I did not look at the tracker today
15:08:03 <jednorozec> but there is this
15:08:09 <jednorozec> .releng 10280
15:08:11 <zodbot> jednorozec: Issue #10280: fas configured bugzilla email doesn't get picked up by repo-request - releng - Pagure.io - https://pagure.io/releng/issue/10280
15:08:29 <jednorozec> it requires some changes in fedscm_admin
15:08:39 <nirik> well, and noggin
15:08:47 <jednorozec> really?
15:09:17 <nirik> we currently do not use the bugzilla email for anything. It was waiting for a way to verify the email address before bugzilla admins would let us use it.
15:09:37 <nirik> I think thats landed, but we need to now tell bz admins about that make sure it's good and enable it.
15:09:59 <jednorozec> hmm
15:10:12 <nirik> so I mean fedscm changes could be seperate I suppose.
15:10:46 <jednorozec> maybe I misunderstood the issue. But there is already RHBZ field in my account. And I think they are asking about checking that email with BZ
15:10:50 <nirik> but if the verify isn't in place anyone could put anything in there.
15:10:58 <jednorozec> ahh
15:11:00 <jednorozec> I see
15:11:51 <jednorozec> But from fedcm_admin point of view
15:12:27 <nirik> yeah, it could be ok from there...
15:12:43 <jednorozec> I dont care about what user inserted there. If the requester has RHBZ email in fas
15:12:59 <jednorozec> We should check the account email and rhbz email
15:13:25 <jednorozec> But I see the point anyone can insert anything inthere
15:13:49 <nirik> well, for accounts that field would also be sent to bz when you login with fedora saml2...
15:13:56 <nirik> which is a good deal more important to get right.
15:14:33 <nirik> anyhow, yeah, we could do the fedscm changes now... it should look for a rhbz email, if it's not set default to main email
15:14:56 <jednorozec> ack
15:16:07 <nirik> I'm trying to change my bz email now, and it's just hanging. ;)
15:17:25 <jednorozec> wrote comment there, since we are in freeze I will work on new reelase of fedscm_admin that will be released after
15:17:35 <jednorozec> .releng 10278
15:17:37 <zodbot> jednorozec: Issue #10278: Fedora release EOL badges tasks lost in migration to new docs - releng - Pagure.io - https://pagure.io/releng/issue/10278
15:18:09 <nirik> I guess we can add that not to our sop... but it seems like something badges people should do. ;)
15:19:39 <jednorozec> I think this should be done by badges maintainers
15:21:45 <jednorozec> .releng 10264
15:21:45 <zodbot> jednorozec: Issue #10264: New Repo for "rpms/pypy3.7" incompletely created - releng - Pagure.io - https://pagure.io/releng/issue/10264
15:22:03 <jednorozec> this will be addressed in the above mentioned release
15:22:42 <jednorozec> I am not sure it will work 100% it needs testing
15:25:07 <jednorozec> I have no more tickets to discuss
15:25:13 <jednorozec> But
15:25:29 <jednorozec> #info Bodhi is now active for Fedora 35
15:26:01 <nirik> cool, was going to ask the status. ;)
15:26:07 <jednorozec> all done
15:26:08 <jednorozec> but
15:26:18 <jednorozec> I got this when running the autosign play book
15:26:19 <jednorozec> autosign01.iad2.fedoraproject.org : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0
15:26:29 <nirik> ah yeah, sshd has to be started. ;)
15:26:36 * nirik can do so for you
15:26:44 <jednorozec> nirik, pretty please
15:26:59 <jednorozec> I will rerun it promptly and we are done with the freeze
15:27:00 <nirik> will be a few tho... my session was killed with the network switch issue this morning. ;(
15:27:10 <jednorozec> no wories.
15:28:38 * jednorozec just rechecked the koji tags and bodhi releases
15:28:45 <jednorozec> all seems to be set correctly
15:31:42 <nirik> sorry, got a phone call.
15:32:31 <nirik> ok, sshd is running playbook away. ;)
15:33:13 <jednorozec> it is running
15:34:09 <nirik> I restarted rawhide eariler... I didn't restart branched because I wasn't sure what state bodhi enablement was in. ;)
15:34:27 <nirik> we really need to find that kernel-core scriptlet cause
15:34:39 <jednorozec> any clues?
15:35:08 <nirik> https://bugzilla.redhat.com/show_bug.cgi?id=1993505 is the bug
15:38:03 <jednorozec> I have noticed the issue
15:38:37 <jednorozec> do we have the -v output
15:38:38 <jednorozec> ?
15:39:09 <jednorozec> ok it should be in this build https://koji.fedoraproject.org/koji/buildinfo?buildID=1822771
15:39:47 <nirik> yes, just adding it to the bug
15:39:53 <nirik> unfortunately it's pretty useless.
15:39:59 <jednorozec> :/
16:23:18 <nirik> #endmeeting