Agenda for the Flatcar Release Team Call on Tuesday, 27th of July 9pm IST / 5:30pm CEST / 3:30pm GMT / 11:30am EDT / 8:30am PST

[sayanchowdhury]

Agenda for the Flatcar Release Team Call on Tuesday, 27th of Jul 9pm IST / 5:30pm CEST / 3:30pm GMT / 11:30am EDT / 8:30am PST

• Zoom link: https://us06web.zoom.us/j/82054240491
  • Meeting ID: 820 5424 0491
  • Passcode: 444888

• Youtube live stream / recording: https://www.youtube.com/watch?v=P8IjaNuKnxQ
• Community Calls calendar (all future calls): link
  • iCal version: link

Welcome

• Brief intro/check-in of the new participants in the Zoom call. Please introduce yourself and share what brings you here today.

News

• Talk about the current release and problems faced
• Status of the current set of issues in the Stable and the plan for the fix

Release planning

• Ongoing and upcoming releases (https://github.com/orgs/flatcar-linux/projects/7/views/8)

Q&A

• Questions from community participants, answered by the Flatcar maintainers

[jepio]

Status of the current set of issues in the Stable and the plan for the fix

Systemd v250 landed in stable, and several issues have surfaced:

• accidentally enabled systemd stub-resolver.conf, report came in via slack (thanks @whites11). Patch merged to all branches sys-apps/systemd: fix tmpfile entry for resolv.conf link flatcar-archive/coreos-overlay#2057
• behavior of systemd-networkd changed wrt. keeping IP addresses configured on wireguard interfaces Wireguard does not work after upgrade to 3227.2.0 #808
• gcc libs (libgcc/libstdc++) were accidentally placed in the wrong library directory (/usr/lib instead of /usr/lib64), may show up on upgrade to stale dynamic linker cache (/etc/ld.so.cache) multipathd fails to start after 3139.2.3 upgrade to 3227.2.0 #809. PR open: prod_image_util: extract gcc libs to /usr/lib64 scripts#391
• systemd-networkd failure during boot on certain bare metal platforms and linode. https://groups.google.com/g/flatcar-linux-user/c/44jLwvlogqQ / Flatcar instance at Linode loses network connectivity after 3227.2.0 upgrade #807. Insufficient logs to root cause at this time, if you're affected reach out so that we can get to a resolution faster.

[t-lo]

@sayanchowdhury There's an umbrella tracking issue for the 3227.2.0 networkd issues: #810 . @miao0miao is tracking the overall status.