## Description of problem: - Error being thrown in logging while booting - "libteamdctl: cli_dbus_check_error_msg: dbus: Error message content: "The name org.libteam.teamd.nm-team was not provided by any .service files" - dbus, team, interface, all working without issue once booted. ## Version-Release number of selected component (if applicable): - RHEL 8.7 ## How reproducible: - Every time. ## Steps to Reproduce: 1. Add team device to vanilla install; 2. Reboot; 3. Check logs. ## Actual results: ~~~ Mar 27 10:46:37 rhel8-7.home NetworkManager[950]: libteamdctl: cli_dbus_check_error_msg: dbus: Error message received: "org.freedesktop.DBus.Error.ServiceUnknown" Mar 27 10:46:37 rhel8-7.home NetworkManager[950]: libteamdctl: cli_dbus_check_error_msg: dbus: Error message content: "The name org.libteam.teamd.nm-team was not provided by any .service files" Mar 27 10:46:37 rhel8-7.home NetworkManager[950]: libteamdctl: teamdctl_connect: Failed to connect using CLI "dbus". Mar 27 10:46:37 rhel8-7.home NetworkManager[950]: libteamdctl: teamdctl_connect: Failed to connect using all CLIs. ~~~ ## Expected results: - No Errors being thrown. ## Additional info: - Looks very similar to https://access.redhat.com/solutions/107183 | Login to the server gives error "org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.oddjob was not provided by any .service files" - **New behaviour** - this was not occurring in RHEL 8.6.
> Hi, Beniamino, can you please take a look at this in NM? Hi, the problem seems to be that NM tries to create a generated connection reading the teamd configuration even if teamd is not running. It is a bug that an error message gets logged when the interface is brought up successfully; can you please reassign this bz to NetworkManager (unless you think something should be done it libteam)? Thanks. Since the issue is easily reproducible, I don't think we need more information at this moment.