15:00:19 #startmeeting Fedora ARM and AArch64 Status Meeting 15:00:19 Meeting started Tue Aug 28 15:00:19 2018 UTC. 15:00:19 This meeting is logged and archived in a public location. 15:00:19 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:19 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:00:19 #chair pwhalen pbrobinson 15:00:19 #topic roll call 15:00:19 Current chairs: pbrobinson pwhalen 15:00:29 morning folks, who's here today? 15:00:43 * pbrobinson o/ 15:01:09 is here in case there are deployment items 15:03:16 smooge, what sort of deployment issues? 15:03:21 or items 15:03:22 * jlinton waves 15:03:27 howdy jlinton 15:03:59 hardware being sent to locations. hardware needing to be brought online for testing 15:06:16 ok, lets get started 15:06:18 #topic 1) ==== Userspace Status ==== 15:06:42 any new issues with user space? 15:07:08 nothing here that I'm aware of 15:07:34 smooge: we can discuss that towards the end 15:08:19 #info No new issues. 15:08:25 #topic 2) ==== Kernel Status ==== 15:08:45 #info F29: kernel-4.18.5-300.fc29 15:08:45 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1139115 15:08:51 #info F30: kernel-4.19.0-0.rc1.git0.1.fc30 15:08:51 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1139720 15:09:06 there looks to be a bunch of random problems with 4.19rc1 15:09:24 pine64 is broken 15:09:45 and Jetson TX2 has regressed to the bad state it was in before 15:09:56 at the first tests I've done 15:10:35 * pwhalen needs to test 15:10:48 how does 4.18 look? 15:11:00 I needed to for a couple of reasons and it was all fire 15:11:00 is anyone seeing any issues there? 15:11:24 4.18 looks fine AFAICT, jlinton have you had a chance to test any bits? 15:11:38 No, I'm busy trying to automate the whole thing.. 15:12:03 I expect in the next few days to be able to deploy fedora into our (maas) infrastructure here. 15:12:25 which should give us better coverage than the adhoc testing i've been doing. 15:12:26 nice 15:13:00 jlinton: that's awesome, will tests etc be public? 15:13:16 No, but I will be opening defects/working issues as they appear 15:13:24 good news 15:14:02 #info Please test and report any issues to the list or #fedora-arm. 15:14:18 anything else for kernel news? 15:15:03 #topic 3) ==== Bootloader Status ==== 15:15:21 we still have an issue with grub2 on aarch64 15:16:48 #info Bug 1615969 - AArch64 - Error when booting "error: out of memory." 15:17:20 anything else? 15:17:43 new u-boot rc3 should be out today I think 15:17:49 nice 15:18:10 will let you know if that fixes the arndale 15:19:39 #topic 4) == F29 == 15:20:02 so beta freeze is today 15:20:55 we havent had a new nominated compose in a while due to an issue with the bot, but one is expected shortly 15:21:17 #info F29 Beta freeze is today (Aug 28th). 15:23:31 #info New nominated compose expected this week. 15:23:40 #topic 5) == Fedora Infra == 15:24:16 smooge: so infra size we had some cavium boxes for cloud/copr, what's the latest status of those? 15:24:55 you were going to get and update the firmware 15:25:40 or walk one of us in doing it at FLOCK (or that is my recollection on it) 15:25:48 smooge: I don't remember that, someone had already updated it 15:26:47 mgalgoci did an update when the box was installed. last we checked you had some other updates you thought were needed but had not shown up. 15:26:51 they're basically the same as most x86 boxes, I think Zi said he would create you a login for the support site in the last couple of days to that thread for the gen 2 devices 15:27:41 my understanding is the latest version of el7 needs a new firmware but I've not been involved in anything aorund el7 so it's just rumours I heard, I can try and find out 15:28:53 ok sorry.. we don't know anyone except you on this so when you said it was needed, I figured it was a hard requirement 15:29:07 if you can get us some connections also that would be useful. 15:29:42 and I meant connectiosn internal. The email to Zi will be very helpful for the cavium hardware 15:29:43 smooge: there's been enough problems with the Cavium that my understanding is that there's basically a new firmware with each el7 release 15:30:29 once that box is up.. we can start interfacing it with the new cloud that is being worked on 15:31:00 that will get it on the copr and other cloud items 15:31:04 smooge: YAY! I would try with the current firmware it has, let me know if I need to poke people 15:31:05 boxes 15:32:05 ok next up.. the HP moonshot goes out of warranty soonish... and has some serious hardware issues which would require a complete chassis replacement from the tech last sent 15:32:30 URGH 15:32:31 :( 15:32:35 we need to look at getting a replacement and lining up funding for it for next fiscal year (which starts in March) 15:32:57 we don't yet have a replacement that will run armv7 accelerated 15:33:31 I will likely know more in Sept though, I can sync when I know more 15:33:43 Right all the "serious" servers are 64-bit only. 15:33:59 But there are some xgene'ish class machines using ARM cores that have 32-bit 15:34:10 this is more of a 'we need to think of a a plan C for arm' 15:35:11 smooge: well it's around timing 15:35:24 we can move the arm64 workload over to other boxes 15:35:46 at the moment 1 of the 3 power supply sockets do not work and require a new chassis... and 1 of the sockets in the chassis makes whatever is plugged into afterwords unbootable but they don't know why 15:36:21 smooge: can the chassis not be swapped under warrantee before it expires? 15:39:51 hopefully. the tech was of the opinion that was what was needed. the people in HP stopped responding on the ticket once it came up. What it looks like it will be is: Put in tickets, get a tech out to make the same report after replacing the parts which still don't work. Get them to send out a new chassis. Take out the old hardware and reset up the 'new' chassis (we are the only moonshot outside of silicon valley in the techs area), 15:39:51 reset every cartridge as they are locked ot the old one 15:40:19 we are looking at a couple days downtime and probably needing someone out there to be focused on it. 15:40:48 oh joy 15:41:22 I don't know if that downtime would affect all of Fedora because of how koji does jobs 15:41:59 smooge: we could bring the mustangs online in the interim, I'm pretty sure we have a bunch that are unused 15:42:18 I believe they are all in use as hardware aarch64 builders 15:42:35 buildhw-aarch64 vs buildvm-aarch64 15:43:06 well that should give us interim capacity then depending on when it's done 15:43:18 I was wondering about the arm side of things 15:43:48 smooge: we can put ARMv7 virt on some of those 15:44:01 they're the same CPU as in the moonshot 15:44:20 oh ok. phew 15:44:51 I was worried they were like the other hardware you had mentioned 15:45:03 smooge: they should be provision able in exactly the same ansible manner 15:45:49 in that case I will put together a workplan on this, get your ok on it and see how hard HP is going to be this time 15:46:39 smooge++ thanks! 15:46:41 pbrobinson: Karma for smooge changed to 17 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:47:16 no problem. I will also be back next week with update on cavium in cloud 15:47:38 thanks smooge 15:47:43 #topic 6) == Open Floor == 15:47:50 anything else for today? 15:48:12 nothing from me 15:48:18 we could also plug in and turn on the old old arm32 hardware. it was still int he racks 15:48:46 I will put that in as plan Z 15:49:37 #endmeeting