19:04:01 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
19:04:01 <zodbot> Meeting started Tue Jan  7 19:04:01 2020 UTC.
19:04:01 <zodbot> This meeting is logged and archived in a public location.
19:04:01 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:04:01 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
19:04:19 <nirik> #chair smooge nirik relrod cverna
19:04:19 <zodbot> Current chairs: cverna nirik relrod smooge
19:04:35 <smooge> sorry my calendar is not alerting me
19:05:05 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
19:05:05 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
19:05:05 <nirik> #topic Tickets needing review
19:05:05 <nirik> #info https://pagure.io/fedora-infrastructure/issues
19:05:21 <nirik> ok, we have the outage tickets...
19:05:27 <nirik> .ticket 8504
19:05:28 <zodbot> nirik: Issue #8504: Planned Outage - Fedora Staging - 2020-01-13 21:00 UTC - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8504
19:06:06 <nirik> do we need a staging ticket? I guess it's good... but probibly only need to announce to infra list?
19:06:31 <smooge> nirik, I may have misinterpreted what you said
19:06:38 <nirik> looks ok to me. move to waiting on external?
19:06:40 <smooge> I thought you wanted a ticket for each outage
19:06:46 <nirik> sure, thats fine.
19:07:00 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8504 https://pagure.io/fedora-infrastructure/issue/8504
19:07:08 <nirik> .tiicket 8505
19:07:14 <nirik> .ticket 8505
19:07:15 <zodbot> nirik: Issue #8505: Planned Outage - Fedora Build Systems - 2020-01-14 21:00 UTC - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8505
19:07:35 <nirik> the date line has a different date in it?
19:08:07 <nirik> fix that and it looks good. announce to devel-announce and infra?
19:08:17 <nirik> .ticket 8506
19:08:18 <zodbot> nirik: Issue #8506: Planned Outage - Fedoraproject.org - 2020-01-15 21:00 UTC - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8506
19:08:56 <nirik> looks good to me. announce to announce list
19:09:05 <nirik> oh, and we should update the outage fedocal with them too.
19:09:34 <smooge> ok will do that
19:10:07 <nirik> .ticket 8507
19:10:08 <zodbot> nirik: Issue #8507: candidate-registry.fedoraproject.org seems to be down - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8507
19:10:26 <nirik> huh, does indeed seem down.
19:11:28 <nirik> looks like it's missing a mount.
19:11:43 <cverna> the registry itself works --> https://candidate-registry.stg.fedoraproject.org/v2/_catalog?n=200
19:11:51 <cverna> I think this is just the frontend
19:12:08 <nirik> but, the mount is wrong?
19:12:32 <nirik> it's trying to mount oci_registry (the same as the normal one) not the candidate one?
19:13:11 <cverna> hum the mount is for the containers storage ?
19:13:28 <nirik> yeah
19:13:42 <nirik> ntap-phx2-c01-fedora01-nfs.storage.phx2.redhat.com:/oci_registry /srv/registry
19:13:54 <nirik> but thats the same as the non candidate one? which seems wrong.
19:14:27 <cverna> yeah that should not be the same, except if they have 2 different directory there
19:14:28 <nirik> so anyhow, the frontend is made by reg... I don't know that we ever ran it on the candidate registry?
19:15:04 <cverna> yep not sure too
19:16:16 <nirik> so, what do we want to do with this one?
19:17:04 <nirik> I guess we could add our questions and move it to backlog/waiting on assignee?
19:17:13 <cverna> I can take a look, and will update the ticket with the /api link for now
19:18:06 <nirik> and no f30/f31/f32 ?
19:18:07 <fm-admin> pagure.issue.assigned.added -- cverna assigned ticket fedora-infrastructure#8507 to cverna https://pagure.io/fedora-infrastructure/issue/8507
19:18:26 <nirik> which I guess could be because all our container composes have been failing due to ppc
19:19:39 <cverna> the namespacing thing in the ticket is wrong
19:19:47 <nirik> https://bugzilla.redhat.com/show_bug.cgi?id=1784961
19:20:08 <cverna> the base container is just fedora, then you use tag to pick the version fedora:32 etc ..
19:20:25 <cverna> yeah but we have the base images just really old ones :(
19:20:49 <nirik> ok.
19:21:07 <nirik> idea: schedule a container day to try and clean up all these container related issues. ;)
19:22:03 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8507: "candidate-registry.fedoraproject.org seems to be down" https://pagure.io/fedora-infrastructure/issue/8507#comment-619433
19:22:05 <cverna> :-)
19:22:12 <fm-admin> pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#8507 https://pagure.io/fedora-infrastructure/issue/8507
19:22:32 <nirik> .ticket 8510
19:22:33 <zodbot> nirik: Issue #8510: which account for Libavatar? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8510
19:23:28 <cverna> we don't provide accounts for libravatar
19:23:40 <nirik> right, but it does do openid.
19:23:51 * nirik tests
19:24:52 <fm-admin> pagure.issue.comment.added -- cverna commented on ticket fedora-infrastructure#8507: "candidate-registry.fedoraproject.org seems to be down" https://pagure.io/fedora-infrastructure/issue/8507#comment-619435
19:24:57 <fm-admin> pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8510 https://pagure.io/fedora-infrastructure/issue/8510
19:24:58 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8510: "which account for Libavatar?" https://pagure.io/fedora-infrastructure/issue/8510#comment-619436
19:25:21 <nirik> closed. ;)
19:25:25 <nirik> ok, 5min left.
19:25:30 <nirik> any other bugs we want to discuss?
19:26:19 <smooge> not from me
19:26:45 <nirik> ok, thanks everyone!
19:26:48 <nirik> #endmeeting