大家有遇到这样神奇的情况吗？

如下图，，我l3 agent用neutron agent-list查不到，可是查其状态，发现在运行，，我重启好几遍也是没用，用neutron agent-list总是查不到？这样影响吗？究竟此服务有没有启动成功？如何解决？



以下是启动l3 agent的日志，感觉也没报错哈？
[mw_shl_code=scala,true]Feb 13 18:31:07 controller systemd-logind: Removed session 4.
Feb 13 18:37:02 controller systemd: Stopping OpenStack Neutron Layer 3 Agent...
Feb 13 18:37:02 controller systemd: Started OpenStack Neutron Layer 3 Agent.
Feb 13 18:37:02 controller systemd: Starting OpenStack Neutron Layer 3 Agent...
Feb 13 18:37:02 controller neutron-l3-agent: Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
Feb 13 18:37:03 controller neutron-l3-agent: Option "verbose" from group "DEFAULT" is deprecated for removal.  Its value may be silently ignored in the future.
Feb 13 18:37:03 controller neutron-l3-agent: Option "notification_driver" from group "DEFAULT" is deprecated. Use option "driver" from group "oslo_messaging_notifications".
Feb 13 18:37:03 controller neutron-l3-agent: /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:187: RuntimeWarning: You have iterated over the result of pkg_resources.parse_version. This is a legacy behavior which is inconsistent with the new version class introduced in setuptools 8.0. In most cases, conversion to a tuple is unnecessary. For comparison of versions, sort the Version instances directly. If you have another use case requiring the tuple, please file a bug with the setuptools project describing that need.
Feb 13 18:37:03 controller neutron-l3-agent: stacklevel=1,[/mw_shl_code]