summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Williams <dcbw@redhat.com>2013-11-07 11:33:16 -0600
committerDan Williams <dcbw@redhat.com>2013-11-07 11:33:16 -0600
commit60cf32f271b801a9f6276339da64b2c625836358 (patch)
treef582b0ebe4f54fad9c435977e1db3186d4b0f168
parent47a0cf2a6cf03d072e038bc5b00178c065c11aab (diff)
downloadNetworkManager-60cf32f271b801a9f6276339da64b2c625836358.tar.gz
trivial: quiet log message about failing to determine virtual interface name
In the case of autoconnect VLANs or IB partitions, if the parent interface hasn't been detected yet at startup, then the get_virtual_interface_name() won't be able to find the parent yet. That's normal, and when the parent is found, system_create_virtual_device() will be run again and the parent will be found, and the autoconnect VLAN/IB partition will be created. But we shouldn't warn that the parent can't be found when that might be a normal occurance.
-rw-r--r--src/nm-manager.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/nm-manager.c b/src/nm-manager.c
index 3e5f86c8e0..9177f3a30a 100644
--- a/src/nm-manager.c
+++ b/src/nm-manager.c
@@ -1200,8 +1200,8 @@ system_create_virtual_device (NMManager *self, NMConnection *connection)
iface = get_virtual_iface_name (self, connection, &parent);
if (!iface) {
- nm_log_warn (LOGD_DEVICE, "(%s) failed to determine virtual interface name",
- nm_connection_get_id (connection));
+ nm_log_dbg (LOGD_DEVICE, "(%s) failed to determine virtual interface name",
+ nm_connection_get_id (connection));
return NULL;
}