Description of problem: Version-Release number of selected component (if applicable): How reproducible: Build the following Go program: ``` package main import ( "context" "fmt" "os" "strconv" systemdDbus "github.com/coreos/go-systemd/v22/dbus" "github.com/godbus/dbus/v5" ) // GetUserConnection returns an user connection to D-BUS func GetUserConnection(uid int) (*systemdDbus.Conn, error) { return systemdDbus.NewConnection(func() (*dbus.Conn, error) { return dbusAuthConnection(uid, dbus.SessionBusPrivate) }) } func dbusAuthConnection(uid int, createBus func(opts ...dbus.ConnOption) (*dbus.Conn, error)) (*dbus.Conn, error) { conn, err := createBus() if err != nil { return nil, err } methods := []dbus.Auth{dbus.AuthExternal(strconv.Itoa(uid))} err = conn.Auth(methods) if err != nil { conn.Close() return nil, err } if err := conn.Hello(); err != nil { return nil, err } return conn, nil } func main() { conn, err := GetUserConnection(os.Geteuid()) if err != nil { panic(err) } name := "user-libpod_pod_642a6b41ae846eedd6587e86d653e43fae07431e9c8ee235dfff9652274aca2f.slice" properties := []systemdDbus.Property{ systemdDbus.PropDescription(fmt.Sprintf("cgroup %s", name)), systemdDbus.PropWants("user.slice"), } pMap := map[string]bool{ "DefaultDependencies": false, "MemoryAccounting": true, "CPUAccounting": true, "BlockIOAccounting": true, } for k, v := range pMap { p := systemdDbus.Property{ Name: k, Value: dbus.MakeVariant(v), } properties = append(properties, p) } ch := make(chan string) _, err = conn.StartTransientUnitContext(context.TODO(), "user-libpod_pod_047d1efebfc678193ffe5a251334be92e62a1aee7ecab2c8c6fc80973e9e51d5.slice", "replace", properties, ch) fmt.Println(err) } ``` Steps to Reproduce: 1. go mod init example.com/m 2. go mod tidy 3. go build 4 ./m Actual results: Unit user-libpod_pod_047d1efebfc678193ffe5a251334be92e62a1aee7ecab2c8c6fc80973e9e51d5.slice already exists. Expected results: <nil> Additional info: It works fine on F36 and Rawhide
Podman upstream issue: https://github.com/containers/podman/issues/16107
This is an urgent issue for us. If we downgrade to systemd-251.4-53.fc37 the problem goes away. This will block the next release of Podman.
I briefly checked the last point release, but nothing suspicious found. Could you see https://github.com/containers/podman/issues/16107#issuecomment-1278581594 and open an systemd upstream issue?
a simpler reproducer that uses only busctl: NAME=test-$RANDOM.slice echo Running $NAME busctl --user call org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager StartTransientUnit 'ssa(sv)a(sa(sv))' "$NAME" "replace" 6 "Description" "s" "slice" "Wants" as 1 "user.slice" "DefaultDependencies" b false MemoryAccounting b true CPUAccounting b true BlockIOAccounting b true 0 On F36 I get: Running test-20500.slice o "/org/freedesktop/systemd1/job/44528" On F37: Running test-31900.slice Call failed: Unit test-31900.slice already exists.
https://github.com/systemd/systemd/pull/25004
The pull request is still being discussed upstream. For now, you can uninstall systemd-oomd-defaults as a work-around.
FEDORA-2022-c72fd8b071 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c72fd8b071
FEDORA-2022-c72fd8b071 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c72fd8b071` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c72fd8b071 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-c72fd8b071 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-ef4f57b072 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ef4f57b072
FEDORA-2022-ef4f57b072 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ef4f57b072` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ef4f57b072 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ef4f57b072 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.