No, it wasn't know...

So, the rawhide script that syncs containers had a typo/syntax error in it. I have corrected this and also pushed todays rawhide. So, f37 should be up to date and stay up to date moving forward.

Stable releases are apparently only synced manually... but since there's not really an active container sig, I am not sure this is really a good idea anymore.
I'd like to propose we just sync them every day when we build new containers, but not sure if that breaks or causes problems for anyones workflow.
I guess I can ask on the devel list?

In the mean time, I pushed the latest f35 and f36 containers. f35 is updated as of today. f36 has been failing to build since july 19th due to armv7 container failing due to https://bugzilla.redhat.com/show_bug.cgi?id=2077680 but I pushed the july 19th one.

We're hitting some issues in FCOS CI. It seems as if any dnf operations in the f36 container just die with exit code 137.

[root@8bcd6fdd00e0 /]# dnf -y install systemd dnsmasq iproute iputils
Fedora 36 - x86_64                                                                                                                                                                                                                    21 MB/s |  81 MB     00:03    
Fedora 36 openh264 (From Cisco) - x86_64                                                                                                                                                                                             3.4 kB/s | 2.5 kB     00:00    
Fedora Modular 36 - x86_64                                                                                                                                                                                                           2.6 MB/s | 2.4 MB     00:00    
Fedora 36 - x86_64 - Updates                                                                                                                                                                                                         798 kB/s |  24 MB     00:31    
Killed
[root@8bcd6fdd00e0 /]# echo $?
137
[root@8bcd6fdd00e0 /]# 
[root@8bcd6fdd00e0 /]# dnf update -y 
Killed

Anybody else seeing this?

Anybody else seeing this?

I was able to run dnf update locally for new fedora:36 here.

I tried the update by myself and even installed some packages, don't see the issue happening to @dustymabe

I'm closing this ticket as Fixed. @dustymabe Feel free to reopen it, if the issue persist on your side.

I found a bug that seems to be related: https://bugzilla.redhat.com/show_bug.cgi?id=1907030#c9

A little more information in https://bugzilla.redhat.com/show_bug.cgi?id=1907030#c13

TL;DR - is it possible there is some new change in the yum repos that's now causing dnf to use extra memory that leads to an OOM?