15:00:56 #startmeeting Infrastructure (2019-03-21) 15:00:56 Meeting started Thu Mar 21 15:00:56 2019 UTC. 15:00:56 This meeting is logged and archived in a public location. 15:00:56 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:56 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:56 The meeting name has been set to 'infrastructure_(2019-03-21)' 15:00:56 #meetingname infrastructure 15:00:56 #topic aloha 15:00:56 #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mizdebsk mkonecny 15:00:56 The meeting name has been set to 'infrastructure' 15:00:56 Current chairs: cverna mizdebsk mkonecny nirik pingou puiterwijk relrod smooge tflink threebean 15:01:05 .hello2 15:01:06 mizdebsk: mizdebsk 'Mikolaj Izdebski' 15:01:12 .hello2 15:01:13 abompard: abompard 'Aurelien Bompard' 15:01:13 hello 15:01:20 .hello2 15:01:21 frailtyy: frailtyy 'Garrett Jansen' 15:01:25 :O 15:01:43 .hello zlopez 15:01:45 mkonecny: zlopez 'Michal Konečný' 15:02:18 .hello2 15:02:19 tflink: tflink 'Tim Flink' 15:02:22 .hello2 15:02:23 bowlofeggs: bowlofeggs 'Randy Barlow' 15:02:34 look at me, almost on time for once 15:02:58 hello everyone 15:03:11 #topic New folks introductions 15:03:11 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 15:03:11 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 15:05:02 #topic announcements and information 15:05:02 #info Beta Freeze Is Currently Going On. Please get FBR for frozen systems. 15:05:49 morning 15:05:57 hi nirik 15:05:57 * nirik got distracted and lost time 15:05:59 #info bodhi 4.0.0 is on the horizon - we are wrapping up the last few tickets that we plan to include 15:06:35 #info pagure 5.3.92 was installed on stg.pagure.io and src.stg.fpo 15:06:54 #topic Oncall 15:06:55 #info bowlofeggs is on call from 2019-03-14 -> 2019-03-21 15:06:55 #info nirik is on call from 2019-03-21 -> 2019-03-28 15:06:55 #info relrod is on call from 2019-03-28 -> 2019-04-04 15:06:55 #info smooge is on call from 2019-04-04 -> 2019-04-11 15:06:56 #info ????? is on call from 2019-04-11 -> 2019-04-18 15:06:57 #info Summary of last week: (from bowlofeggs ) 15:07:06 bowlofeggs, how was oncall this week? 15:07:27 sorry for not summarizing my last call on the previous meeting, something come up and i was not able to join 15:07:36 my last oncall* 15:07:47 * bowlofeggs passes the ceremonial oncall coffee mug to nirik 15:08:13 smooge: oncall was fairly quiet this round - i mostly just triaged bugs and none of them were urgent 15:08:33 * nirik drinks deep. 15:09:06 i am probably the least useful oncall since i'm not a sysadmin though ☺ 15:09:18 i sometimes notice that people .oncall, see it's me, and then go "oh well" :) 15:09:21 well thank you for your time. getting tickets traiged 15:09:28 heh, yeah i think doing that is useful 15:09:33 it was 15:09:35 it does help... 15:09:38 i can usually tell if soemthing is worth interrupting others or not 15:09:46 which i think is the main goal 15:10:11 (the secret: it's almost always not worth interrupting others!) 15:10:22 #topic Monitoring discussion 15:10:22 #info https://nagios.fedoraproject.org/nagios 15:10:22 #info Go over existing out items and fix 15:11:26 * nirik looks 15:11:53 pinging the abrt people about retrace servers 15:12:18 yeah, send email... 15:12:40 some disks needing replacement still... 15:12:49 and our usual suspects 15:12:54 pkgs02 no swap (because I tried to unswap/swap) 15:13:11 I thought I rebooted that 15:13:14 pkgs02 needs more space (but that should wait until after freeze) 15:13:15 i think pkgs02 needs more memory and disk 15:13:27 yeah. 15:14:44 nirik, did you do the swap/noswap after the last reboot? 15:15:47 just checking in case there was a different problem with swap 15:16:07 yes, but it is unable to swapon due to memory fragmentation 15:16:48 ok thanks 15:16:51 swapon: /dev/vda2: swapon failed: Cannot allocate memory 15:17:04 #topic Tickets discussion 15:17:04 #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 15:17:38 I didn't mark anything. 15:17:43 https://pagure.io/fedora-infrastructure/issue/7646 15:17:43 #topic Priorities for next week? 15:17:43 #info please put tickets needing to be focused on here 15:17:46 if anyone has a pet ticket to discuss, feel free. 15:17:50 oops sorry 15:17:55 thats fine 15:18:06 I tried it today and the fork is working 15:18:23 But the forked repo is stuck as read-only 15:18:51 With this message: "The permissions on this repository are being updated. This may take a while. During this time, you or some of the project's contributors may not be able to push to this repository." 15:19:45 Sorry I forgot to mark the ticket before meeting 15:20:04 * nirik has no status there, smooge or puiterwijk might know. 15:20:40 the updated version which was supposed to help fix this was applied earlier today 15:20:44 The read-only bit is a red herring, and a consequence of the former. The Hook ID is wrong 15:21:11 I don't know why the hook-id is wrong because i thought I set it 'right' using the commands earlier 15:21:18 well not that fork 15:21:43 Here is the fork, if you want to look at it - https://src.stg.fedoraproject.org/fork/zlopez/rpms/0ad 15:21:47 NEw forks get the Hook ID from config 15:22:25 so after we updated the config to make sure it had the right hook-id in it, I ran that command which was to change all the forks to it 15:23:02 Right. Did you also restart all of the services that set this up? (one of the celery runners) 15:23:05 smooge: This fork was created after the update 15:24:08 Anyway, we can get that fixed out-of-meeting 15:24:28 puiterwijk, I did what you told me to do. Asking me if I didn't do something will just be 'did you tell me to do that?' 15:24:42 That is totalyl fair 15:25:02 Anyway, let's talk out-of-meeting. It should be simple to fix, just need to look what step I forgot 15:25:09 ok focus this week: 15:25:29 Ok, I just wanted to ask about it, it's blocking one of my work in progress issue 15:25:30 1. repospanner/pagure deployments for post freeze 15:25:47 2. rawhide gating items in staging 15:25:53 3. ??? 15:26:16 mkonecny, understood. we will fix it after this meeting 15:26:16 things in no order for me: f30 beta, power9 installs, community openshift 15:26:16 nothing in staging for rawhide gating yet 15:26:40 3. community openshift 15:26:42 mizdebsk: oh, is the stg koji sync all done? I thought so, but didn't look... 15:26:42 4. power9 15:26:47 bodhi 4.0.0 will have a few thigns for rawhide gating, but not enough to actually turn it on 15:27:04 nirik, it is done, but last time i checked there was a problem with nfs on s390x builder 15:27:25 it shouldn't need nfs? 15:27:50 not for rpm builds, it may need it for images and stuff 15:27:56 * mizdebsk is not sure 15:27:57 I guess it would if we wanted runroot/compose tasks... but we never have in the past. 15:28:04 1. repospanner/pagure deployment help and repospanner fixes 15:28:44 2. nothing until 1 is considered "done enough" 15:28:58 speaking of, where are we on the ansible repospanner? still need to upgrade pagure.io and repospanner on batcave01? 15:29:12 bowlofeggs: getting the new resultsdb and greenwave in staging would be good 15:29:17 and it relates to rawhide gating 15:29:18 nirik: I'd say yes 15:29:29 (the resultsdb PR that should improve things just got merged) 15:30:31 * pingou not sure if we can run our test scripts against greenwave in staging 15:30:44 the koji db has been synced recently but is it new enough? 15:30:47 I guess we'll see :) 15:31:11 note that (I think) greenwave in stg is using prod data/listening to prod bus? 15:31:31 resultsdb is for sure 15:31:35 I'm not sure for greenwave 15:31:46 i think it is also. 15:31:56 then, should work :) 15:31:59 cool 15:32:08 well, it's querying src.stg git for objects that only exist in prod... ;) 15:32:08 pingou: staging isn't very useful with greenwave, because there are no tests in staging 15:32:13 pingou, koji db in stg was synced on 2019-03-12 - it's pretty recent 15:32:17 (and thus causing repospanner messages) 15:32:24 i've long wanted tests in staging, but alas 15:33:24 ok anymore items needing more than one person to focus on? 15:33:27 bowlofeggs: resultsdb in staging is full of test results (from prod) 15:33:49 nirik: that's likely going to be the issue yeah :( 15:33:51 pingou: that's not what i need - i need to see tests on builds that i make in staging, so i can force failures, successes, etc. 15:34:08 and use staging gating.yamls 15:34:25 I agree this would be good to have 15:35:46 ok I am going to move onto the next topic 15:35:54 #topic Apprentice Open office minutes 15:35:54 #info A time where apprentices may ask for help or look at problems. 15:36:21 any items that new people are looking at wanting help on? 15:36:46 I want to thank the person who gave a fix for the http certgetter 15:38:50 they also sent another patch in ticket for another item. ;) 15:38:59 hopefully we can get that one applied soon too. 15:39:06 cool will go look 15:39:10 #topic Open Floor 15:39:35 Anything for the open floor htis week? 15:39:53 If not I will give you back the rest of your day and will go eat some dinner 15:40:19 breakfast, its whats for dinner! 15:40:35 well I have been up for a whee bit 15:40:49 you on the other hand are at 7:40? 15:40:58 i ate dinner at america's restaurant last night 15:41:00 8:40now... 15:41:08 dennys? 15:41:13 smooge: yep! 15:41:28 I am an internationalist myself 15:41:28 cinammon roll pancakes. devastatingly delicious 15:41:34 they have the silliest name for a dish I think anywhere... 15:41:43 the slam? 15:41:44 Moons over my hammy 15:41:48 oh yeah, haha 15:41:50 moons over my hammy is a good touch 15:41:59 ive always been a grand slammer 15:42:08 https://www.dennys.com/food/breakfast-faves/moons-over-my-hammy/ 15:42:25 thankfully they never went with my idea of Sam and Ella Eggs 15:42:25 it used to be called Danny's originally 15:42:31 smooge: lol 15:42:57 ok and with that.. good night folks. Please tip the wait staff on your way out.. they have to put up with me 15:43:03 #endmeeting