18:00:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:00 Meeting started Tue Jul 21 18:00:00 2020 UTC. 18:00:00 This meeting is logged and archived in a public location. 18:00:00 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:01 #chair pingou mboddu nirik smooge 18:00:01 Current chairs: mboddu nirik pingou smooge 18:00:01 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:01 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:01 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:01 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:02 #topic Tickets needing review 18:00:03 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:38 anyone around today to stand up? 18:00:58 .ticket 9149 18:00:59 nirik: Issue #9149: registry tags not being generated - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9149 18:01:43 pagure.issue.tag.added -- kevin tagged ticket fedora-infrastructure#9149: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9149 18:01:44 pagure.issue.edit -- kevin edited the priority fields of ticket fedora-infrastructure#9149 https://pagure.io/fedora-infrastructure/issue/9149 18:01:58 .ticket 9152 18:01:59 nirik: Issue #9152: staging noggin deployment planning - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9152 18:02:11 * mboddu is here 18:02:21 nirik: I can update the tickets 18:02:22 abompard (and any others from noggin team) ^ please look when you get a chance. 18:02:26 mboddu: cool. 18:02:37 med/med/groomed/waiting ? 18:02:40 nirik: +1 18:02:42 nirik: currently replying :-) 18:02:51 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9152: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9152 18:02:52 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9152 https://pagure.io/fedora-infrastructure/issue/9152 18:03:00 abompard: awesome. 18:03:07 abompard++ 18:03:07 mboddu: Karma for abompard changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:03:17 .ticket 9153 18:03:17 nirik: Issue #9153: Combine uncombined http logs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9153 18:03:38 I think this one might have gotten opened by mistake? smooge: did you mean to reopen this one? 18:04:14 nirik: According to the comment "but a second part which extracts data needed to be run. " 18:04:17 ^ from smooge 18:04:44 ok. 18:04:47 Just add groomed and waiting on assignee? 18:04:51 yeah... 18:04:57 am in meeting will deal with later 18:05:03 pagure.issue.tag.removed -- abompard removed the groomed, medium-gain, and medium-trouble tags from ticket fedora-infrastructure#9152 https://pagure.io/fedora-infrastructure/issue/9152 18:05:04 pagure.issue.edit -- abompard edited the priority fields of ticket fedora-infrastructure#9152 https://pagure.io/fedora-infrastructure/issue/9152 18:05:05 pagure.issue.comment.added -- abompard commented on ticket fedora-infrastructure#9152: "staging noggin deployment planning" https://pagure.io/fedora-infrastructure/issue/9152#comment-666604 18:05:11 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9153: groomed https://pagure.io/fedora-infrastructure/issue/9153 18:05:12 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9153 https://pagure.io/fedora-infrastructure/issue/9153 18:05:27 that pagure thing is really starting to be anoying... 18:05:41 pagure.issue.tag.added -- abompard tagged ticket fedora-infrastructure#9152: groomed, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/9152 18:05:52 .ticket 9154 18:06:11 Seems like pagure is down 18:06:25 seems fine here 18:06:27 .headers pagure.io 18:06:28 .ticket 9154 18:06:29 mboddu: content-length: 57335, x-xss-protection: 1; mode=block, content-security-policy: default-src 'self';script-src 'self' 'nonce-N4ymBSKOWreXREUBV2e50ZG9Z'; style-src 'self' 'nonce-N4ymBSKOWreXREUBV2e50ZG9Z'; object-src 'none';base-uri 'self';img-src 'self' https:;connect-src 'self' https://pagure.io:8088;frame-src https://docs.pagure.org;frame-ancestors https://pagure.io;, x-content-type-options: nosniff, set-cookie: (2 more messages) 18:07:03 nirik: I think its back now 18:07:06 .ticket 9154 18:07:19 it wasn't down from here. ;) 18:07:28 nirik: Issue #9154: Wrong URL in fedpkg push notification email - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9154 18:07:31 nirik: Issue #9154: Wrong URL in fedpkg push notification email - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9154 18:07:34 mboddu: Issue #9154: Wrong URL in fedpkg push notification email - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9154 18:07:51 Now its back everywhere 18:07:56 right, so not sure on this one. 18:08:17 Close, get back later? 18:08:18 I guess close won't fix? but it would be fixed once we re-write FMN... 18:08:27 +2 18:08:29 +1 18:08:51 it also doesn't seem like it would be that bad to push a new fedmsg-meta... but meh 18:08:52 pagure.issue.edit -- mohanboddu edited the close_status and status fields of ticket fedora-infrastructure#9154 https://pagure.io/fedora-infrastructure/issue/9154 18:08:53 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#9154: "Wrong URL in fedpkg push notification email" https://pagure.io/fedora-infrastructure/issue/9154#comment-666608 18:09:00 .ticket 9156 18:09:01 nirik: Issue #9156: fedora-rawhide-pr-pipeline doesn't install BuildRequires when testing parted - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9156 18:09:12 I have no idea who should look at this one... 18:09:33 No idea 18:09:38 who did that setup in first place? 18:09:40 whoever 'owns' that rawhide-pr-pipeline 18:10:01 lets leave it alone and perhaps pingou knows who we can ping on it... 18:10:29 Maybe siddharthvipul would know? 18:10:40 But yeah, we can leave it as is 18:10:47 I have a couple of tickets in releng 18:11:02 so, go ahead that was the last need-review in infra 18:11:15 .releng 9614 18:11:16 mboddu: Issue #9614: Can't give karma to Bodhi update - releng - Pagure.io - https://pagure.io/releng/issue/9614 18:11:38 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8648 https://pagure.io/fedora-infrastructure/issue/8648 18:11:39 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8648: "Koji task info pages load very slowly" https://pagure.io/fedora-infrastructure/issue/8648#comment-666610 18:11:51 I dont know whats going on 18:11:57 med,med,groomed? 18:12:13 yeah, not sure either. I am not sure I want to give a karma to try it... 18:12:27 there is one +1 already. 18:12:33 I will test the update and give karma and see what happens 18:12:46 * mboddu dont want to to give the update a random karma 18:13:02 yeah 18:13:08 ack 18:13:43 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8667: "aws: assign permissions to allocate elastic IPs in AWS for aws-copr" https://pagure.io/fedora-infrastructure/issue/8667#comment-666614 18:13:55 .releng 9615 18:13:56 mboddu: Issue #9615: Can't push to sourcextractor++, branches f31 and f32 - releng - Pagure.io - https://pagure.io/releng/issue/9615 18:14:24 possibly a pdc thing? 18:14:56 nirik: Yeah, but I cant query pdc with '+' signs as well, iirc 18:14:59 But I will check 18:15:12 ha. ok. 18:15:21 med,med,groomed? 18:15:27 not sure how we would work around that if it's pdc... 18:15:29 sure 18:16:06 And thats it 18:16:37 cool. 18:17:25 any other bugs or prs or blockers anyone wants to discuss? 18:17:56 None from me 18:20:24 ok, lets get back at it then... 18:20:27 #endmeeting