19:00:05 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:05 Meeting started Tue Feb 18 19:00:05 2020 UTC. 19:00:05 This meeting is logged and archived in a public location. 19:00:05 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:05 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:05 #chair cverna mboddu nirik relrod smooge 19:00:05 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:05 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:05 Current chairs: cverna mboddu nirik relrod smooge 19:00:06 #topic Tickets needing review 19:00:08 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:01:07 good morning. it is time for hte weekly standup 19:01:14 s/weekly/daily/ 19:01:14 indeedy 19:01:24 .ticket 8660 19:01:25 nirik: Issue #8660: ability to reclaim PVs in fedora infra openshift(s) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8660 19:01:47 move to waiting on asignee 19:01:53 ok swill do so 19:01:56 .ticket 8663 19:01:57 nirik: Issue #8663: https://communityblog.fedoraproject.org shows HTTP 403 Forbidden in Lynx (and it should not) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8663 19:02:05 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8660 https://pagure.io/fedora-infrastructure/issue/8660 19:02:24 this we no longer host... but I am not sure where to refer them. 19:02:29 i don't know who sets up/runs the wordpress 19:02:35 misc: thoughts ^ 19:02:39 close can't fix? 19:02:44 I thought it was misc 19:02:56 ah I knew fedoramagazine was misc. 19:03:31 I thought community blog was also... but perhaps I am wrong. 19:03:39 it would be good to know who 19:03:53 well ping @misc in ticket and set wait on assignee? 19:04:27 or ping and close won't fix. 19:04:39 I guess we can keep it open 19:04:41 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8663 https://pagure.io/fedora-infrastructure/issue/8663 19:04:42 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8663: "https://communityblog.fedoraproject.org shows HTTP 403 Forbidden in Lynx (and it should not)" https://pagure.io/fedora-infrastructure/issue/8663#comment-627187 19:04:43 just nothing we can do 19:04:58 .ticket 8664 19:04:59 nirik: Issue #8664: Please update kernels on Test Machine Resources For Package Maintainers - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8664 19:05:01 If misc says nope.. i will close it wont fix 19:05:18 I can look at this one, since I am dealing with those instances right now (moving them to aws) 19:05:39 wasn't sure if we wanted to move the aarch64's too, but we could 19:06:15 thats all the needs review 19:06:20 any others to discuss? 19:06:38 ok will reassign to you and wait on assignee 19:06:54 .ticket 8657 19:06:56 nirik: Issue #8657: `fedpkg module-build` fails with "The modulemd libreoffice.yaml is invalid. Please verify the syntax is correct." upon buildopts: arches: [x86_64] - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8657 19:07:01 might need input from modularity folks there... 19:07:08 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8664 to kevin https://pagure.io/fedora-infrastructure/issue/8664 19:07:09 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8664 https://pagure.io/fedora-infrastructure/issue/8664 19:08:07 so as far as I can tell after the current reorgs.. the modularity people are the koji people who would be mikem 19:08:18 anything new on 8607 19:08:21 .ticket 8607 19:08:22 nirik: Issue #8607: Renew Certificate for *.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8607 19:08:34 I have pinged several people... nothing 19:08:42 ok. 19:08:48 my guess is that there are 0 funds until Mar1 19:08:51 * mboddu is sorta here 19:08:56 on aarch64's... what are our chances to get more disks? 19:08:59 and they are waiting for their purse to come back 19:09:13 hey mboddu 19:09:29 nirik, if I had known 2-3 weeks ago, we had a good chance we would get them in March 19:09:43 yeah. ;( 19:09:50 now I think we are budget constrained until 2021 19:10:13 so I am looking for where i can find replacements 19:10:15 are there any ssds left in arm03 we could steal? 19:10:27 no those were all taken/used 19:10:37 well, there's 4 at least... 19:10:44 since we have 4 instances up on them 19:10:54 oh wait what is arm03 19:11:26 i pulled and used all the ssds in the arms in rack 146 19:11:34 is arm03 the box in the cloud? 19:11:39 yep. 19:11:47 it's the old armv7 calexida in cloud 19:12:01 if we can get that cloud emag up I can put armv7 instances on it and we can retire it. 19:12:07 so.. ok I was about to say 'I don't know if we have anything in that calxeda in the cloud' 19:12:21 there's 4 ssds at least. Possibly more. 19:12:36 nirik, I am not sure we can get a cloud emag up.. switch ports are needed for 10g 19:12:37 I don't know if they will fit/need caddys/etc 19:13:17 that was our 'its is always something' discussion a couple of days ago 19:13:27 well, arm03 is gonna go during the move at the latest. ;) 19:13:52 the one thing about the arm box in that rack is there is no way to tell which ones are active 19:14:11 indeed. 19:14:25 if I have them pull caddies to see if they have ssd's the drives don't map 1:1 with anything so I am probably going to kill those boxes 19:14:32 thats fine. 19:14:37 they are test machines. 19:14:48 if they go down too bad... 19:15:20 I am fine scavenging that box now. 19:15:23 ok I will put in some tickets for them to look at stuff 19:15:38 if we can bring up that emag somehow I can put them on it 19:15:59 ok, any other tickets or things to discuss? 19:16:21 not at the moment 19:16:27 #endmeeting