jdoss and dustymabe were able to pin podman to
1.9.3 in testing-devel stream. the next stream will contain podman
2.x and we can gather feedback on the update from users
there.(dustymabe,
16:33:42)
Discussion: OKD release schedule and blocking FCOS releases on OKD e2e tests(dustymabe, 16:37:14)
OKD will release roughly bi-weekly, alternating
with the FCOS releases(lorbus,
16:38:45)
AGREED: The group
agrees it would be a good idea to trigger OKD tests on new builds of
FCOS so we can get feedback about breakage sooner than later. It's
possible the breakage is a regression in the base OS OR a desired
change that OKD needs to adapt for. Either way running tests will
help both FCOS and OKD.(dustymabe,
16:56:06)
Change deadline for FCOS releases(dustymabe, 16:59:54)
AGREED: In order to
get a little more clarity and reliability for our releases we'd like
to implement a guideline that if changes don't land by the previous
Friday of a scheduled release then we won't hold the release for
that change. This gives the release wrangler some clear guidelines
about when it's safe to proceed with running the release.(dustymabe,
17:09:38)
ACTION: bgilbert to
update the ticket(bgilbert,
17:10:18)
forwarding NIC renaming udev rules from the initramfs(dustymabe, 17:12:20)
AGREED: We haven't
seen a lot of users needing this functionality just yet so we'd
prefer to wait to add that functionality. What we have for
propagating networking karg information a bit hacky, but is required
for now in order to not require every user who needs static
networking to specify networking information twice. We'd prefer to
not further the behavior for now.(dustymabe,
17:25:22)
if you want to see OKD running on FCOS (and a
general overview of FCOS) check out the presentation we did
yesterday: https://www.youtube.com/watch?v=ErF_0xQmxrU(dustymabe,
17:28:13)