16:31:11 <jlebon> #startmeeting fedora_coreos_meeting
16:31:11 <zodbot> Meeting started Wed Apr 13 16:31:11 2022 UTC.
16:31:11 <zodbot> This meeting is logged and archived in a public location.
16:31:11 <zodbot> The chair is jlebon. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:31:11 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:31:11 <zodbot> The meeting name has been set to 'fedora_coreos_meeting'
16:31:17 <jlebon> #topic roll call
16:31:26 <bgilbert> .hi
16:31:29 <zodbot> bgilbert: bgilbert 'Benjamin Gilbert' <bgilbert@backtick.net>
16:31:47 <saqali> .hi
16:31:48 <zodbot> saqali: saqali 'Saqib Ali' <saqali@redhat.com>
16:32:45 <dustymabe> .hi
16:32:46 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dusty@dustymabe.com>
16:32:56 <travier> .hi siosm
16:32:56 <jlebon> #chair bgilbert saqali dustymabe
16:32:56 <zodbot> Current chairs: bgilbert dustymabe jlebon saqali
16:32:56 <zodbot> travier: Sorry, but user 'travier' does not exist
16:33:03 <travier> .hello siosm
16:33:04 <zodbot> travier: siosm 'Timothée Ravier' <travier@redhat.com>
16:33:05 <jlebon> #chair travier
16:33:05 <zodbot> Current chairs: bgilbert dustymabe jlebon saqali travier
16:33:38 <mnguyen_> hello .mnguyen
16:33:50 <mnguyen_> .hello mnguyen
16:33:51 <zodbot> mnguyen_: mnguyen 'Michael Nguyen' <mnguyen@redhat.com>
16:34:01 <jlebon> #chair mnguyen_
16:34:01 <zodbot> Current chairs: bgilbert dustymabe jlebon mnguyen_ saqali travier
16:34:47 <jlebon> looks like a thinner crowd today. will start in 30s
16:35:21 <jlebon> #topic Action items from last meeting
16:35:27 <jlebon> ENOENT
16:35:37 <jlebon> cool, moving on
16:35:41 <dustymabe> yay
16:35:57 <jlebon> #topic F36: Fedora CoreOS Test Week
16:35:59 <jlebon> #link https://github.com/coreos/fedora-coreos-tracker/issues/1123
16:36:05 <dustymabe> 👋
16:36:22 <dustymabe> just wanted to go over some findings from the test week
16:37:00 <dustymabe> we found some issues that were large and some that were small :) - here's a summary of some of the issues opened in the issue tracker around test day:
16:37:07 <dustymabe> #info F36: No network on rpi4
16:37:13 <dustymabe> #link https://github.com/coreos/fedora-coreos-tracker/issues/1145
16:37:19 <dustymabe> #info rebasing to another stream fails when deployment is staged
16:37:23 <dustymabe> #link https://github.com/coreos/fedora-coreos-tracker/issues/1150
16:37:29 <dustymabe> #info F36: 36.20220325.1.0 NetworkManager not allowed to access NM dispatcher scripts
16:37:34 <dustymabe> #link https://github.com/coreos/fedora-coreos-tracker/issues/1156
16:37:40 <dustymabe> #info F36 VM fails to display the network device information on console
16:37:44 <dustymabe> #link https://github.com/coreos/fedora-coreos-tracker/issues/1153
16:37:49 <dustymabe> #info exoscale: disk images fail to provision
16:37:55 <dustymabe> #link https://github.com/coreos/fedora-coreos-tracker/issues/1160
16:38:12 <dustymabe> #info Fedora36 Next Auto-Upgrade Fails & Yields Grub Prompt
16:38:17 <dustymabe> #link https://github.com/coreos/fedora-coreos-tracker/issues/1149
16:38:40 <jlebon> nice!
16:39:00 <dustymabe> most of those represent things that we either don't currently have automated tests for or are hard to test in an automated fashion
16:39:28 <dustymabe> I'd like to also point out quite a few conversations and propsed fixes to our documentation:
16:39:36 <davdunc> .hello2
16:39:37 <zodbot> davdunc: davdunc 'David Duncan' <davdunc@amazon.com>
16:39:49 <jlebon> i think we have tests that rebase, but kola disables zincati so doesn't hit this
16:39:57 <jlebon> #chair davdunc
16:39:57 <zodbot> Current chairs: bgilbert davdunc dustymabe jlebon mnguyen_ saqali travier
16:40:10 <dustymabe> https://github.com/coreos/fedora-coreos-docs/pulls?q=is%3Apr+
16:40:28 <dustymabe> lots of new stuff in there over the past few weeks, mostly generated by test day involvement
16:41:02 <dustymabe> Thanks everyone who participated!
16:41:17 <jlebon> indeed, thanks all!
16:42:18 <jlebon> dustymabe: is there a badge in the works?
16:42:27 <dustymabe> yeah, i need to request one
16:42:33 <dustymabe> and also push the one from the previous test day forward :)
16:42:42 <dustymabe> nb was helping me and then we got sidetracked
16:42:45 <jlebon> haha
16:42:58 <jlebon> k cool
16:43:04 <jlebon> anything else, or should we move on?
16:43:09 <aaradhak> .hi
16:43:10 <zodbot> aaradhak: aaradhak 'Aashish Radhakrishnan' <aaradhak@redhat.com>
16:43:25 <jlebon> #chair aaradhak
16:43:25 <zodbot> Current chairs: aaradhak bgilbert davdunc dustymabe jlebon mnguyen_ saqali travier
16:43:43 <travier> and a tshirt?
16:43:54 <travier> lots of great testing. Good job
16:45:05 <jlebon> k, going to move on
16:45:15 <jlebon> #topic rebasing to another stream fails when deployment is staged
16:45:21 <jlebon> #link https://github.com/coreos/fedora-coreos-tracker/issues/1150
16:45:38 <jlebon> dustymabe: you tagged this, want to introduce it?
16:45:59 <dustymabe> yep - basically would like to get some concensus on if we think this is a UX issue we want fixed
16:46:45 <dustymabe> more or less if you have a staged update it's pretty hard to do any sort of change
16:47:06 <dustymabe> see my workaround in https://github.com/coreos/fedora-coreos-tracker/issues/1150#issuecomment-1086260097
16:47:21 <jlebon> this should be fixed in git main ostree. let me check if it's in a release
16:48:17 <jlebon> next ships 2022.1. fix is in 2022.2
16:48:23 <dustymabe> jlebon: "this" being part `2.` of https://github.com/coreos/fedora-coreos-tracker/issues/1150#issuecomment-1086260097
16:48:37 <jlebon> https://bodhi.fedoraproject.org/updates/FEDORA-2022-9c21ee528d
16:49:05 <jlebon> dustymabe: yup
16:49:35 <dustymabe> ok - cool - Let's add that info to the ticket and we can close it out when that lands.
16:49:42 <jlebon> hmm, it might actually fix 1. too
16:50:10 <dustymabe> ehh. I think `1.` could really use https://github.com/coreos/zincati/issues/498
16:50:34 <jlebon> right yeah, there's two separate things here
16:51:09 <jlebon> basically with the ostree fix, creating a new deployment manually should drop the lock
16:51:33 <jlebon> but it doesn't remove the need for an update-graph-aware way to force an update
16:52:08 <dustymabe> cool - let's #info the ostree fix and we can move on
16:53:05 <jlebon> #info this UX issue should be fixed by ostree 2022.2 (https://github.com/ostreedev/ostree/pull/2524)
16:53:28 <jlebon> #topic Fedora CoreOS talks for devconf.us 2022
16:53:30 <jlebon> #link https://github.com/coreos/fedora-coreos-tracker/issues/1154
16:54:37 <dustymabe> I guess let's get together tomorrow and try to work out the details of who does what talk(s) etc..
16:55:01 <dustymabe> and then submit a proposal
16:55:06 <jlebon> ack SGTM
16:55:23 <jlebon> moving on
16:55:24 <dustymabe> I'll make a meeting invite - if you want to participate let me know
16:55:39 <jlebon> #topic tracker: Fedora 36 changes considerations
16:55:41 <mnguyen_> interested
16:55:45 <jlebon> #link https://github.com/coreos/fedora-coreos-tracker/issues/918
16:56:48 <jlebon> dustymabe: are there newly synced changes to look at?
16:56:56 <dustymabe> I'm thinking we can probably start to close out the podman 4.0 issue - at least will make a comment there about it seeming OK so far
16:57:34 <dustymabe> jlebon: :) - I need to fixup the script so I can resync things - bugzilla stopped allowing unauthenticated access and I never got a round to using the new API with a token
16:58:08 <jlebon> ahh fun
16:58:20 <dustymabe> it's crazy to me that the unauth thing stopped working - that's a huge feature of issue trackers and such, being able to see/interact without having an account
16:58:23 <jlebon> though at this point, I don't think there should be many changes
16:58:27 <dustymabe> jlebon: right
16:58:32 <bgilbert> dustymabe: getting a bot token is pretty trivial fwiw
16:58:53 <dustymabe> bgilbert: yeah, I'm going to :)
16:59:13 <dustymabe> I guess for the DNS over TLS change we haven't seen any fallout yet?
16:59:19 <dustymabe> https://github.com/coreos/fedora-coreos-tracker/issues/1098
17:00:13 <dustymabe> i'll add a few comments
17:00:16 <travier> dustymabe: might join for the devconf meeting too
17:00:23 <dustymabe> +1
17:00:41 <jlebon> none that I'm aware of
17:02:15 <jlebon> final freeze is coming up soon-ish. i think in two weeks now
17:02:23 <jlebon> after which we'll move to weekly next releases
17:02:26 <dustymabe> jlebon: i think final freeze is already here
17:02:53 <dustymabe> https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
17:03:02 <dustymabe> started on the 5th
17:03:16 <dustymabe> so - weekly releases it is \o/
17:03:52 <jlebon> ohh fun. i've been misreading that
17:04:23 <jlebon> #info we are now in final freeze. we will be doing next releases weekly.
17:04:40 <dustymabe> i'll open a ticket for next week's `next`
17:04:46 <jlebon> +1 thanks
17:04:57 <jlebon> ok cool, moving on to open floor
17:05:08 <jlebon> #topic Open Floor
17:05:51 <bgilbert> VirtualBox support landed in this week's releases, thanks to spresti!
17:05:56 <bgilbert> updated docs should be landing shortly
17:06:16 <dustymabe> would anyone like to volunteer to look into why CLHM stopped spitting out some information on the serial console? https://github.com/coreos/fedora-coreos-tracker/issues/1153
17:06:34 <dustymabe> that's one of the most "found" things on test day. People really like that IP address printed out :)
17:06:45 <dustymabe> spresti++
17:06:45 <zodbot> dustymabe: Karma for spresti changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:06:45 <jlebon> woohoo, nice work spresti and bgilbert!
17:06:53 <bgilbert> spresti++
17:06:53 <zodbot> bgilbert: Karma for spresti changed to 2 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:07:17 <dustymabe> bgilbert: at this point how hard would it be to create a vagrant box for FCOS that just pulled out vbox (or qemu) image?
17:07:26 <dustymabe> s/out/our
17:07:41 <jlebon> dustymabe: heh that was going to be my question too :)
17:07:52 <bgilbert> dustymabe: not sure; I don't know Vagrant that well
17:07:59 <bgilbert> there's some old code somewhere that _might_ be a good starting point
17:08:16 <bgilbert> https://github.com/coreos/vagrant-ignition/
17:08:39 <dustymabe> Vagrant is definitely a good onramp for people (i.e. coming from a world they know)
17:08:39 <bgilbert> at a minimum, it would need to be reworked for guest properties
17:08:59 <dustymabe> and I honestly think we could get by without even creating a new artifact for it
17:09:16 <bgilbert> yeah, agreed that we shouldn't need a new artifact
17:09:33 <dustymabe> could be a cool hackday project or something
17:09:50 <davdunc> is the cloud-init support not enough?
17:09:50 <bgilbert> +1
17:10:02 <bgilbert> davdunc: we don't support cloud-init
17:10:29 <davdunc> bgilbert: makes sense, but vagrant does and couldn't it be an ignition file that gets passed to the box?
17:10:30 <dustymabe> but even so.. vagrant boxes don't typically run cloud-init either
17:10:46 <dustymabe> they have an SSH key baked in from the image creation time
17:10:54 <bgilbert> davdunc: not sure how cloud-init does it, but we read the config from a custom guest property
17:10:57 <dustymabe> i'm thinking we could get around that by using Ignition
17:10:58 <davdunc> current vagrant supports cloud-init as a provisioner.
17:11:09 <dustymabe> davdunc: didn't know that.. interesting
17:11:32 <bgilbert> it's possible we could reuse some infrastructure, but we'll likely need some custom parts too
17:12:01 <dustymabe> =1
17:12:07 <dustymabe> sigh.. +1, rather
17:12:13 <davdunc> bgilbert: I am sure you're right.
17:13:00 <dustymabe> Vagrant also supports creating boxes for things like AWS and such. i.e. `vagrant up` would give me an FCOS instance in AWS and then I can `vagrant ssh`
17:13:13 <dustymabe> I always wanted to explore that more for Fedora Cloud working group, but never got around to it
17:13:20 <dustymabe> would be cool to have that for FCOS/Fedora Cloud
17:13:23 <bgilbert> #link https://github.com/coreos/fedora-coreos-tracker/issues/144
17:13:29 <bgilbert> is our tracking issue
17:13:53 <jlebon> davdunc: oh neat, I didn't know that (re. AWS)
17:13:56 <dustymabe> +1 - thanks for that link @bgilbert
17:15:10 <jlebon> anything else for open floor?
17:15:26 <jlebon> will close meeting in 52.5 seconds otherwise
17:16:18 <jlebon> #endmeeting