16:02:41 #startmeeting Fedora ELN SIG (2022-04-22) 16:02:41 Meeting started Fri Apr 22 16:02:41 2022 UTC. 16:02:41 This meeting is logged and archived in a public location. 16:02:41 The chair is dcavalca. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:02:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:41 The meeting name has been set to 'fedora_eln_sig_(2022-04-22)' 16:02:53 #meetingname eln 16:02:53 The meeting name has been set to 'eln' 16:02:59 here 16:03:17 #chair sgallagh SSmoogen dcavalca 16:03:17 Current chairs: SSmoogen dcavalca sgallagh 16:03:23 #topic init process 16:03:38 sgallagh is out today fyi 16:03:47 .hi 16:03:49 dcavalca: Something blew up, please try again 16:03:52 dcavalca: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:03:55 lol thanks zodbot 16:04:07 t184256 is me 16:04:09 * t184256 is asosedkin 16:04:30 .hello2 16:04:31 dcavalca: Something blew up, please try again 16:04:34 dcavalca: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:04:50 ok nevermind 16:04:54 Hi everyone 16:05:20 Do we have an agenda? 16:05:31 #topic Old Business 16:05:44 jforbes: looking now 16:06:39 doesn't look like it, at least not on devel@ 16:06:56 checking logs for the last one 16:07:23 ok, so for old business, we had two actions from the last one 16:08:31 sgallagh and asosedkin to finalize the branch-vs-rawhide approach 16:08:31 clang Conditionalize openssl in ELN to behave as C9S 16:08:31 anybody has updates on these? 16:08:31 we've decided to go for a separate branch following c9s 16:09:13 .hello salimma 16:09:14 michel: salimma 'Michel Alexandre Salim' 16:09:15 it hasn't been landed yet, as we've started with a mass-rebuild first and half the stuff's broken there by itself 16:09:44 .hello jkonecny 16:09:45 jkonecny[m]: jkonecny 'Jiří Konečný' 16:09:49 if Fedora ELN war installable and rebuildable, that'd be just great =/ 16:10:03 iirc we did get a good compose earlier in the week 16:10:20 or at least, one that didn't make my builds explode :) 16:10:34 for clang, he's landed the OpenSSL change, I believe 16:10:52 Any issues with the installation or just packages? 16:10:52 .hello ngompa 16:10:53 can we also have one installable with anaconda? =) 16:10:53 Eighth_Doctor: ngompa 'Neal Gompa' 16:11:25 jkonecny[m]: https://github.com/fedora-eln/eln/issues/88 16:11:33 Do you have BZ or something about the installation issue? 16:11:49 yeah please file a ticket if you haven't already 16:11:49 Looking 16:12:05 ah thanks 16:12:06 there are many, masking each other. reproducer's attached 16:13:38 I wonder about this 16:13:41 https://github.com/fedora-eln/eln/issues/87 also qualifies, but is likely workaroundable 16:13:53 dumb question: do we have something to do this kind of testing already in fedora? 16:14:07 OpenQA 16:14:41 And Anaconda has kickstart tests but it's more a project upstream testing than Fedora 16:14:46 why isn't ELN running through OpenQA testing? 16:14:56 cool, yeah that looks worthwhile to do 16:16:10 Anaconda project had ELN included in our upstream tests bit we removed that because of stability issues... 16:16:39 But these were really just unit tests not integration tests 16:16:46 jkonecny[m]: can we add it back and get issues filed against ELN when it breaks? 16:17:01 but yeah, I think we need both actually 16:18:05 Eighth_Doctor: I suspect because nobody's hooked it up yet 16:18:20 We could probably even add the integration tests we have, issue is that these are not easy to maintain and team don't have a capacity for that really 16:19:06 jkonecny[m]: is the concerns that the tests break because of ELN specifically, or something else? 16:19:31 I can try to convince team to put the ELN tests back again, the issue is again time spend on that 16:20:21 I think it'd be worth a try, we can't really improve this if we don't have visibility on when things break 16:21:17 ok, I'm not precise here. We are still running the ELN unit tests daily: https://github.com/rhinstaller/anaconda/actions/runs/2205114928 16:21:32 we just disabled them on pull requests 16:21:38 that was painful 16:22:00 so yes, it's still running and it's even green for some time 16:22:04 oh good 16:22:09 yeah I don't think we need this on PRs 16:22:34 if you want, we might even add the kickstart tests part but not a simple thing to create that nor maintain 16:23:03 https://github.com/rhinstaller/kickstart-tests 16:23:45 oh yeah that does look useful 16:23:57 right now we are running that on Rawhide, RHEL8 and RHEL9 https://github.com/rhinstaller/kickstart-tests/actions/runs/2204792769 16:24:06 and would probably help us catch breakage like the one t184256 hit down the road 16:24:34 Eighth_Doctor, I expect 1) someone needs to help Adam make it work. 2) Someone needs to actually work on giving openqa more resources as it is usually overburdened doing the tests for things it has now 16:25:50 It should be "easy" to enable if we have a boot.iso which will be used for the testing 16:25:59 Something like release candidate 16:26:48 I mean the kickstart tests 16:26:51 looks like we do 16:26:53 e.g. https://odcs.fedoraproject.org/composes/production/Fedora-ELN-10-20220422.0/compose/BaseOS/x86_64/iso/Fedora-ELN-10-20220422.0-x86_64-boot.iso 16:27:11 Completely different issue is to solve failures and flakes 16:27:42 I think just getting signal to begin with would be great, we can make these non-blocking until they get stable enough 16:27:49 and in the meantime fix the outstanding issues 16:28:40 SSmoogen: for 2), would funding some cloud instances help with that? 16:31:01 no openqa runs on bare metal hardware 16:32:29 at least it did when I was part of CPE and was asked to move it to cloud. It is its own 'cloud' in some ways and needs to have bare metal to run all its vms and virtual devices that tests are captured on 16:32:52 that shouldn't be an obstacle, iirc, aws metal instances would be able to simulate that 16:33:12 I'm pretty sure between davdunc and Davide Cavalca, we could get some of those in place 16:33:30 dunno if there are ARM metal instances, but if there are, that'd also be useful 16:33:33 yea. 16:33:38 there are arm metal instances 16:34:04 there are Intel, AMD,and Graviton (neoverse) metal instances. 16:34:23 then those would be useful for OpenQA 16:34:47 sure.. you guys knock yourself out :) 16:35:13 this is a bit of a tangent, but yeah, my point was that if the blocker here is capacity, we can try to help with that 16:36:59 I think if it can be done, then that would be great. It would require some heavy lifting of people who know AWS networking, serial/etc. These boxes regularly get wedged and have to be dealt with by hand 16:37:49 I can help with periodic testing on x86 VMs and reporting failures, but somebody please make it go green at least once 16:38:09 SSMoogen happy to help with that. I can definitely provide guidance and tech contribution on the AWS side. 16:38:28 adamw, ^^ you have a victim who wants to help with openqa into the cloud 16:38:57 my work here is done 16:39:16 we should probably find some folks on IBM Cloud side to give us POWER and Z too 16:39:22 those are really big gaps 16:39:52 seriously though, davdunc[m and Eighth_Doctor please set up something with adamw and help him on it to see if it is possible after F36 goes out 16:40:03 sure 16:40:15 we already have plans to talk about Cloud Edition testing anyway 16:40:24 we can just add this on top 16:41:00 ack SSmoogen we'll work with him in the regular QA meetings too. 16:41:22 #action Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity 16:42:01 #action jkonecny[m] look into enabling kickstart tests for ELN 16:42:28 did I miss anything else from the previous discussion? 16:43:54 Yeah, do we have something like nightly boot.iso for ELN? 16:44:22 jkonecny[m]: yeah, it ends up here: https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/compose/BaseOS/x86_64/iso/ 16:44:35 but the name has the compose date in it 16:44:55 if you need a stable URL I suppose we could try and get it symlinked to boot.iso or something like that 16:45:17 That would be definitely helpful 16:46:02 #action dcavalca file an issue to get a stable boot.iso symlink for the latest compose 16:46:28 I say file an issue because I have no clue how to actually fix this, but hopefully someone else does :p 16:46:59 Thank you 16:47:21 alright, anything else on this before we move on? 16:49:32 alright, moving on 16:49:46 #topic New Business 16:50:05 I wanted to signal boost https://bugzilla.redhat.com/show_bug.cgi?id=2077299 16:50:23 I'm seeing reliable build failures on fedora-eln-ppc64le in copr 16:50:33 (and, interestingly, only in copr) 16:51:40 That's weird 16:51:59 It didn't even get started 16:51:59 hmmm I don't know if all copr ppc builds are done on power9 systems 16:52:16 it seems to be hitting a bunch of SIGILL in the postinst for ca-certificates 16:52:26 all builds prefer Power8 unless we talk about EL9 builds 16:52:33 which I assume is why it then dies in the transaction 16:52:58 ah, ELN .. not sure, does ELN ppc64le require Power9 builders? 16:53:04 yeah this is ELN 16:53:05 Is there any significant difference between the rawhide PPC and eln PPC builders? 16:53:55 michel, no difference in Copr 16:54:05 I am not sure if it does or not. I would expect that if it did hard require it, then all the eln builds would fail 16:54:17 s/it/power9/ 16:54:37 why? 16:55:20 I would figure that the instructions which are p9/p10 only would be in glibc 16:55:45 SSmoogen: davdunc hah, they say that *now* ;) 16:55:52 https://download.copr.fedorainfracloud.org/results/@meta/drgn/fedora-eln-ppc64le/04294758-python-drgn/builder-live.log.gz is one example fyi 16:55:59 and other items which would cause trying to run code on an 8 to go SIGILL 16:56:18 dcavalca, so those 3 were not the only builds which were failing? 16:56:32 yes, from "Permanently added '2620:52:3:1:dead:beef:cafe:c210'" that was the Power8 machine 16:56:40 SSmoogen: I had a few more but they were older so I didn't bother adding them to the BZ 16:56:47 the power9 machines have IPv4 addresses 16:57:11 praiskup: can we try pinning eln to the power9 builders to see if that fixes this? 16:57:47 SSmoogen: but yeah, it was reliably failing for me on every build 16:58:18 we're almost out of time, anything else folks wanted to discuss? 16:58:53 dcavalca, done 16:59:17 thanks praiskup, I'll try again and report back on the BZ 16:59:49 dcavalca, but ATM we small amount of Power9 builders .. it may take longer to get the builder 17:00:16 that's fine, at least for my usecase we're using these for CI with packit 17:00:26 thanks for the help 17:00:32 alright, we're out of time 17:00:40 thanks everyone, really good discussion today 17:00:45 #endmeeting