16:30:40 #startmeeting fedora_coreos_meeting 16:30:40 Meeting started Wed Jun 21 16:30:40 2023 UTC. 16:30:40 This meeting is logged and archived in a public location. 16:30:40 The chair is spresti. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:30:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:30:40 The meeting name has been set to 'fedora_coreos_meeting' 16:30:55 #topic roll call 16:31:02 .hi 16:31:03 dustymabe: dustymabe 'Dusty Mabe' 16:31:11 .hello jasonbrooks 16:31:12 JasonBrooks[m]: jasonbrooks 'Jason Brooks' 16:31:28 .hi 16:31:29 quentin9696[m]: Sorry, but user 'quentin9696 [m]' does not exist 16:31:30 #chair dustymabe 16:31:30 Current chairs: dustymabe spresti 16:31:45 #chair jasonbrooks 16:31:45 Current chairs: dustymabe jasonbrooks spresti 16:31:54 .hello marmijo 16:31:55 marmijo[m]: marmijo 'Michael Armijo' 16:32:07 #chair marmijo 16:32:07 Current chairs: dustymabe jasonbrooks marmijo spresti 16:32:09 .hello aaradhak 16:32:10 ash[m]: aaradhak 'Aashish Radhakrishnan' 16:32:28 #chair aaradhak 16:32:28 Current chairs: aaradhak dustymabe jasonbrooks marmijo spresti 16:32:46 Hey everyone! 16:32:58 We just have a few items on the list today 16:33:21 Lets wait another minute or two to let people trickle in. 16:34:14 #topic Action items from last meeting 16:34:52 travier write a ticket to submit a fedora change to enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions 16:35:06 Any updates on this ? 16:35:47 I have an update 16:36:23 #info travier opened https://github.com/coreos/fedora-coreos-tracker/issues/1512 to discuss enabling `fwupd-refresh.timer in Fedora server like variants 16:37:15 Thats great! 16:38:27 Ok, if there is nothing else to add, lets move our meeting topics for today. 16:39:13 #topic tracker: drop default fedora-repos-modular 16:39:40 #link https://github.com/coreos/fedora-coreos-tracker/issues/1513 16:40:07 lets discuss 16:40:14 spresti: want me to intro this one? 16:40:51 Sure if you don't mind 16:41:06 .hi 16:41:07 jdoss: jdoss 'Joe Doss' 16:41:28 .hi 16:41:29 ravanelli: ravanelli 'Renata Ravanelli' 16:41:30 We got a PR to remove the fedora-repos-modular RPM from our package lists: https://github.com/coreos/fedora-coreos-config/pull/2469 16:41:41 #chair jdoss 16:41:41 Current chairs: aaradhak dustymabe jasonbrooks jdoss marmijo spresti 16:41:48 #chair ravanelli 16:41:48 Current chairs: aaradhak dustymabe jasonbrooks jdoss marmijo ravanelli spresti 16:42:03 after looking at it a bit closer the Fedora change hasn't been approved yet 16:42:17 but assuming it is approved this will have implications for us 16:43:01 It definitely makes sense to align with Fedora and drop the package from our package lists, but since we have automatic updates enabled this makes things a little complicated 16:43:29 basically if we remove the package then I think peoples updates will stop working if they have a layered modular package 16:44:47 so we may have to figure out something more complicated, which sucks 16:44:53 alternatively we just send out warnings 16:45:07 any thoughts on this? 16:45:54 Oh? why would that happen? I thought in the proposal doc it addressed that concern under upgrades. 16:46:12 cri-o is probably the best example of a modular package that might be commonly layered in our user base 16:46:56 I guess I miss-understood but it sounded like its intent is to just be an opt in repo which would create variants of pre existing and upgraded vs new fresh install. 16:46:58 spresti: the "Upgrade/compatibility impact" doesn't really consider how things behave in OSTree 16:47:19 Ah ok. 16:47:28 if a package is part of the base OSTree in FCOS and we remove it in our package lists then it will get removed on the next update. 16:47:45 for that same reason this problem also applies to silverblue and IoT 16:48:52 I'll put this information in the ticket 16:49:05 Sorry I completely missed the context of OSTree and its impact. Thank you. 16:50:11 no worries 16:50:13 it's subtle 16:50:54 this problem affects other OSTree variants, but it's worse for FCOS because people don't manually update theese systems so they won't know their systems aren't auto-updating 16:51:41 I'll add this information to the ticket. I'm interested in thoughts from travier and maybe bgilbert so I can gather feedback their too 16:51:47 there* 16:52:16 Ok. That makes sense; I think we can circle back on this topic at the next meeting. 16:53:01 👍 16:53:02 Does anyone have any other meeting topics for today ? 16:54:13 Ok, I am going to take that as a no; 16:54:27 #slowsummer 16:54:46 Lets go ahead and change over to open discussion 16:54:53 Yeah lol 16:55:00 #topic Open Floor 16:56:07 There is one issue with kubevirt/LVM i'm chasing downstream and will probably open an upstream issue for soon. 16:56:33 Ok I will give 2 more mins and see if anyone has things to discuss. 16:56:40 Ah sorry dusty 16:56:56 no - i meant that for open floor 16:57:12 I am exploring iPXE booting FCOS RPi CM4s on a Turing Pi 2 board. It's been an adventure. 16:57:27 Whats going on with kubevirt/LVM? 16:58:15 spresti: TL;DR host (OpenShift) fighting with Kubevirt Guest (which could be any linux OS) about who controls block devices with LVM signatures. 16:58:39 jdoss: adventure... at least you're having fun? 16:58:53 That's my secret Dusty, I am always having fun. 16:58:59 that's my jdoss 16:59:03 .hire jdoss 16:59:03 adamw hires jdoss 16:59:25 I will point out this is a super cool project that was shared by a community member: https://github.com/M1cha/router/ 16:59:45 he goes through some hoops, but gets FCOS running on a tiny ARM board that acts as his router 17:00:02 I'm using FCOS on my router, but it's still a x86_64 board 17:00:27 That is pretty neat 17:00:44 Wow thats awesome… 17:01:48 All right; since its been a bit quiet today I am going to go ahead and end the meeting (unless there are any objections) 17:02:09 +1 17:02:16 #endmeeting