18:00:38 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:38 <zodbot> Meeting started Mon Jul 27 18:00:38 2020 UTC.
18:00:38 <zodbot> This meeting is logged and archived in a public location.
18:00:38 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:38 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:38 <nirik> #chair mboddu nirik smooge pingou
18:00:38 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:38 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:38 <zodbot> Current chairs: mboddu nirik pingou smooge
18:00:38 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:39 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:40 <nirik> #topic Tickets needing review
18:00:41 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:43 * mboddu is here
18:00:47 <nirik> Smooge is out today.
18:00:52 <nirik> mboddu: want to adjust tickets?
18:01:05 <mboddu> Sure, I can do it
18:02:02 <nirik> so... we need to talk with our eariler compatrots. ;)
18:02:26 <nirik> they are triaging things (yea!) but they need to move them out of needs-review so they don't show up for us anymore.
18:02:38 <nirik> .ticket 9196
18:02:43 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information.
18:02:44 <nirik> just move to waiting on assignee
18:02:47 <nirik> .ticket 9196
18:02:51 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information.
18:02:57 <nirik> .ticket 9169
18:02:58 <zodbot> nirik: Issue #9169: Bodhi update not pushed to stable after "Auto-request stable based on time?" - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9169
18:03:06 <nirik> .ticket 9170
18:03:07 <zodbot> nirik: Issue #9170: Cleaning up temporary queues in /bodhi? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9170
18:03:08 <nirik> same here
18:03:10 <fm-admin> pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9169 https://pagure.io/fedora-infrastructure/issue/9169
18:03:25 <fm-admin> pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9170 https://pagure.io/fedora-infrastructure/issue/9170
18:03:45 <nirik> .ticket 9171
18:03:46 <zodbot> nirik: Issue #9171: src.fedoraproject.org Activity not displayed on user pages, unlike on pagure.io - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9171
18:03:47 <mboddu> Done and done
18:03:56 <nirik> no idea here, probibly something for pingou. ;)
18:04:03 <nirik> med/med/groomed/waiting?
18:04:17 <mboddu> Maybe a config or needs a new pagure deployed
18:04:19 <mboddu> +1
18:04:34 <fm-admin> pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9171: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9171
18:04:35 <fm-admin> pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9171 https://pagure.io/fedora-infrastructure/issue/9171
18:04:49 <mboddu> I guess thats it from infra?
18:04:51 <nirik> yeah, I think we hotfixed this on pagure.io, but perhaps not src?
18:04:57 <nirik> yep. anything on the releng side?
18:05:02 <mboddu> Yes
18:05:21 <mboddu> .releng 9629
18:05:22 <zodbot> mboddu: Issue #9629: PDC: do we want to store the EPEL compose? - releng - Pagure.io - https://pagure.io/releng/issue/9629
18:05:45 <nirik> right. I chimed in there and you did too. :)
18:05:46 <mboddu> low trouble as its just a opinion, high gain, groomed?
18:06:28 <mboddu> .releng 9630
18:06:29 <zodbot> mboddu: Issue #9630: openh264 debuginfo repo is broken - releng - Pagure.io - https://pagure.io/releng/issue/9630
18:06:50 <mboddu> This needs some investigation
18:06:51 <nirik> sure.
18:07:01 <nirik> yeah, that might be something on the cisco side. ;(
18:07:01 <mboddu> med,med,groomed?
18:07:17 <mboddu> Yeah, I am not 100% sure now
18:07:21 <nirik> I recall we asked them about debuginfo a while back... but I thought it was fixed.
18:07:25 <nirik> +1
18:08:01 <mboddu> .releng 9631
18:08:02 <zodbot> mboddu: Issue #9631: flatpaks: move from 'master' to 'stable' - releng - Pagure.io - https://pagure.io/releng/issue/9631
18:08:08 <mboddu> This is huge
18:08:15 <mboddu> high,high,groomed
18:08:32 <nirik> ack. Yeah, we can do it, will just take time...
18:09:03 <mboddu> Thats all I got
18:10:08 <nirik> #info mass rebuild has started and is churning away
18:10:20 <nirik> any other tickets to discuss / blockers / etc?
18:10:29 <mobrien[m]> I have a question
18:10:38 <nirik> fire away!
18:11:09 <mobrien[m]> Me and vipul were planning to work on a ticket tomorrow
18:11:13 <mobrien[m]> .ticket 9161
18:11:17 <zodbot> mobrien[m]: Issue #9161: Create ansible playbook to restart failed services on proxy hosts - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9161
18:11:57 <mobrien[m]> There has been some community contribution which is not quite the full solution, should we take it over and finish it or advise the community contributor and leave it to them?
18:12:05 <mobrien[m]> Not sure what the process is
18:12:19 <nirik> well, no set process...
18:12:44 <nirik> usually we want community folks to help us, so I'd say advise them and review and such?
18:12:58 <siddharthvipul> mobrien[m]: we have the answer ^-^
18:13:10 <nirik> unless they are fine with you taking over I suppose...
18:13:41 <mobrien[m]> Ok cool. There are some comments on the PR we'll see how they respond and take it from there I guess. One other related question to that.
18:14:14 <nirik> cool.
18:14:20 <mobrien[m]> If a new playbook is created do we raise a ticket to get rbac assigned to it or just ask someone on this channel?
18:14:55 <nirik> either way. If no one is around/everyone busy, go with the ticket... if not it could just be done out of hand...
18:15:27 <nirik> it's a pretty easy change... just a 2 liner... playbook and group
18:15:28 <mobrien[m]> ok cool. Thats all from me thanks
18:15:43 * mboddu needs to look at how to assign rbac access
18:16:13 <nirik> mobrien[m] / siddharthvipul: oh, did you see from the eariler standup... can you move things from 'needs review' to 'waiting on asignee' status? that will drop them off our radar here.
18:16:33 <nirik> mboddu: it's 2 lines in a config file in ansible-private.
18:16:43 <mobrien[m]> Ok will do
18:16:45 <mboddu> nirik: https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html#role-based-access-control-for-playbooks ?
18:17:09 <siddharthvipul> nirik: you mean on centos-infra?
18:17:14 <siddharthvipul> we can do that
18:17:29 <nirik> we may want to rework how all this flow works, but for now... yeah.
18:17:49 <siddharthvipul> nirik: yeah, I would also like to color match the tags, but too much?
18:17:50 <siddharthvipul> :P
18:18:03 <nirik> mboddu: yes, but there's a config file in ansible-private/files/rbac/ that is the config file that uses.
18:18:13 <siddharthvipul> anyway, you are right! the idea was to tag those tickets where we need input from Brian or Fabian
18:18:31 <mboddu> Thanks nirik
18:18:36 <nirik> once the board feature of pagure lands, we should revisit things.
18:18:54 <siddharthvipul> very soon ^-^
18:19:26 <nirik> 🎉🎉🎉
18:20:31 <nirik> mobrien[m]: oh, on that south ameria error... I bet we need to 'enable' that region... new ones aren't enabled by default.
18:20:41 <nirik> and how is the maintainer test stuff looking?
18:20:55 <mobrien[m]> That makes sense
18:22:59 <mobrien[m]> The maintainer stuff is frustrating me. I got an f31 up and ran the playbook succesfully then 10 mins later it became unreachable. The logind service is failing so won't allow any logins. If you already have an ssh session open it will stay open. I was hoping to get someone to look at it with me to figure out why the service is failing
18:23:13 <nirik> strange
18:23:26 <nirik> I could tomorrow? just drop a time on my calendar...
18:23:48 <nirik> hum, I see we already have south america enabled... not sure whats going on with it now.
18:24:24 <mobrien[m]> I'll put a calender invite in and hopefully we'll have time to look at both problems
18:24:44 <nirik> sounds good. :)
18:25:31 <nirik> FYI, I need to file a ticket sometime soon for grokmirror... it's failing in some cases and sending emails about it. Not sure what changed, but it needs looking into
18:25:57 <nirik> anyone have anything else they would like to discuss
18:25:58 <nirik> ?
18:27:04 <nirik> ok, thanks for coming everyone!
18:27:06 <nirik> #endmeeting