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