RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If you invoke CreateMachine() and pass a MemoryAcct=yes scope property, or alternatively create a slice unit setting MemoryAcct=yes, then systemd will accidentally set the memory limit to zero, instead of leaving it unlimited.
In the case of CreateMachine() this causes the OOM killer to immediately reap the container init processes before CreateMachine() even returns.

Version-Release number of selected component (if applicable):
206

How reproducible:
Always 
Steps to Reproduce:
# cat /etc/systemd/system/machine-demo.slice
[Unit]
Description=Demo slice

[Slice]
CPUAccounting=yes
MemoryAccounting=yes


# systemctl start machine-demo.slice

# cat /sys/fs/cgroup/memory/machine.slice/machine-demo.slice/memory.limit_in_bytes
0


Actual results:
Hard & soft memorys are set to 0

Expected results:
Limits are left on default values (unlimited) unless explicitly set in the unit file.

Additional info:
See also

http://lists.freedesktop.org/archives/systemd-devel/2013-July/012270.html

As mentioned in the mailing list discussion this was fixed in systemd-206.