Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_coreos_meeting.2022-03-09-16.30.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_coreos_meeting.2022-03-09-16.30.txt Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_coreos_meeting.2022-03-09-16.30.log.html ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:30:16 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_coreos_meeting.2022-03-09-16.30.log.html . Meeting summary --------------- * roll call (dustymabe, 16:30:22) * Action items from last meeting (dustymabe, 16:35:07) * the msi-x commit was reverted temporarily (again) in the Fedora kernel while AWS works to upgrade instances so they will no longer be affected https://github.com/coreos/fedora-coreos-tracker/issues/1066#issuecomment-1061789661 (dustymabe, 16:39:51) * ACTION: ravanelli to look into the F36 changes 127 to see if this change affects us on ppc64le (dustymabe, 16:41:33) * CVE-2022-0847 (The Dirty Pipe Vulnerability) (dustymabe, 16:42:27) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1118 (dustymabe, 16:42:32) * there is a `testing` and `next` stream release going out today with the 5.16.13 kernel that should address the CVE (dustymabe, 16:43:12) * Update the VMware metadata to new, modern defaults (dustymabe, 16:45:05) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1119 (dustymabe, 16:45:10) * AGREED: We aren't opposed to updating the OVA to contain more modern defaults, but would like to know how users can revert the behavior if they need to since the platforms aren't EOL yet. We'd either need some documentation to let the users know how or to know that the users can ignore warnings and still proceed. (dustymabe, 17:03:43) * open floor (dustymabe, 17:04:36) * Here is the action update #127. The gcc ppc64le team was able build fcos using F36 as host in a P9, P8 failed completely in the boot part for F36, they are looking at it, looks the issue is related to the bits change. I will keep an eye on how it is going (dustymabe, 17:04:58) * Your time may shift in your locale in the coming weeks, but FCOS community meetings will stay at 16:30 UTC. (dustymabe, 17:12:48) Meeting ended at 17:15:44 UTC. Action Items ------------ * ravanelli to look into the F36 changes 127 to see if this change affects us on ppc64le Action Items, by person ----------------------- * ravanelli * ravanelli to look into the F36 changes 127 to see if this change affects us on ppc64le * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (71) * miabbott (28) * zodbot (26) * jlebon (10) * fifofonix (8) * davdunc (6) * travier (5) * ravanelli (4) * davdunc[m (3) * jforbes (2) * aaradhak (1) * skunkerk (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
