<dustymabe>
cverna: if you re-run the promotion for testing it will update the existing PR
<dustymabe>
and the same for `next` (will create a new PR for that one)
<walters>
OK I booted `36.20221106.3.0` to try to quickly investigate https://github.com/okd-project/okd/issues/1475 but...zincati is just saying everything is stable and not updating. I think this is the first time I've tried to debug this "in anger" and figure out what may be going wrong in all the layers here
<dustymabe>
cverna: i think if you just remove the label and re-add it to the streams issue it will do the right thing
<baude>
bgilbert, spresti[m] heya, dustymabe sent me your way with my question ... i am trying to find docs on booting fcos on hyperv specifically around the ignition injection ... do you have apointer by chance?
<bgilbert>
baude: HyperV outside of Azure Stack?
<baude>
yes
<bgilbert>
baude: Ignition doesn't support fetching userdata on HyperV. if HyperV provides a mechanism for that, we'd be interested in adding support, though.
<bgilbert>
your recourse is to treat it as a bare metal install
<baude>
so you cannot boot fcos on windows machines. is that correct?
<bgilbert>
...on HyperV. VMware and VirtualBox support exists
<bgilbert>
but you can boot the live ISO and pass an Ignition config as part of the install
<bgilbert>
which will cause coreos-installer to write the config to a known location in /boot. Ignition will pick it up from there
<baude>
why cant that work with an image file ?
jpn has quit [Ping timeout: 264 seconds]
<bgilbert>
how do you mean?
<baude>
oh, thjis is because it GETs the file and writes it based on a kernel command line ?
<bgilbert>
Ignition needs to know what platform it's running on, and how to get the config on that platform, yeah
<bgilbert>
(there's hacks like the ignition.config.url= kernel argument also. it can be made to work. but it's not the sort of UX we'd want to document)
<walters>
dustymabe: mmmm....maaaybe
jpn has joined #fedora-coreos
<dustymabe>
bgilbert: baude: basically it's a chicken and egg problem. The ignition config is what tells the machine what to do, but because we don't have a hyperv specific image there's no mechanism on that platform to automagically know where to find the Ignition config
<dustymabe>
so the bare metal install workflow handles that problem for us
<baude>
only if you setup an http server
<dustymabe>
even though it's a bit cumbersome to use that (when compared to the other hypervisors that do have support)
<baude>
how do we move this down the road
<baude>
we are getting heat to support hyperv for podman machine
<baude>
will ignition search devices like cdrom?
<walters>
the Live ISO doesn't require a separate http server, coreos-installer iso ignition can inject it
<baude>
coreos-installer run on windows?
jpn has quit [Ping timeout: 246 seconds]
<walters>
no, though in principle I think this bit of code could
<walters>
hmm, maybe it'd be possible to try to generalize the approach of "write data into a stamped location" to other images too
<baude>
you mean like a cdrom or device of some sort?
jpn has joined #fedora-coreos
<walters>
the way customizing the ISO works is it just writes the ignition config into a reserved space
<walters>
(this avoids needing to mount the thing, which generalizes quickly to "run a Linux kernel as a VM" like guestfs does)
<walters>
(which means you need to run a VM so you can run your VM)
fifofonix has quit [Ping timeout: 252 seconds]
<dustymabe>
baude: I think the real answer is to get proper support into Ignition for what you want probably