The lbaasv2 agent is not registering with neutron in the neutron agent-list upon installation and start of the process. The service status looks as though it is active:
[root@host-145 testlab(keystone_admin)]# systemctl status f5-openstack-agent
● f5-openstack-agent.service - F5 LBaaSv2 BIG-IP Agent
Loaded: loaded (/usr/lib/systemd/system/f5-openstack-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2017-08-29 15:39:28 MDT; 1s ago
Main PID: 24924 (coverage)
CGroup: /system.slice/f5-openstack-agent.service
└─24924 /usr/bin/python2 /usr/bin/coverage run --rcfile=/home/testlab/coverage/.coveragerc /usr/bin/f5-oslbaasv2-agent --log-file /var/log/neutron/f5-openstack-agent.log --con...
Aug 29 15:39:28 host-145.int.lineratesystems.com systemd[1]: Started F5 LBaaSv2 BIG-IP Agent.
Aug 29 15:39:28 host-145.int.lineratesystems.com systemd[1]: Starting F5 LBaaSv2 BIG-IP Agent...
Aug 29 15:39:29 host-145.int.lineratesystems.com coverage[24924]: Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future.
[root@host-145 testlab(keystone_admin)]#
But there is no entry for agent in the neutron agent-list:
In the agent log, I see repeated critical and error messages indicating no lbdriver attribute on the LbaasAgentManager object. These error messages repeat for a time, then disappear.
After the errors disappear, the agent log looks like such. Note that the /usr/bin/f5-oslbaasv2-agent version is 8.3.0. This seems to be a reference to the neutron-lbaas version, which is 8.3.0, not of our own agent version, which differs from OpenStack by one.
Agent version and neutron-lbaas version. As far as I know, this problem has always existed though.
f5-icontrol-rest (1.3.0)
f5-openstack-agent (9.3.3b2)
f5-openstack-lbaasv2-driver (9.3.3b2)
f5-sdk (2.3.3)
[root@host-145 testlab(keystone_admin)]# pip list | grep neutorn
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
[root@host-145 testlab(keystone_admin)]# pip list | grep neutron
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
neutron (8.3.0)
neutron-lbaas (8.3.0)
neutron-lib (0.0.3)
python-neutronclient (4.1.2)
[root@host-145 testlab(keystone_admin)]#
I do see the driver initialization in the neutron server.log, but of course there's no RPC communication with the agent.
OpenStack Release
mitaka
Description
The lbaasv2 agent is not registering with neutron in the neutron agent-list upon installation and start of the process. The service status looks as though it is active:
But there is no entry for agent in the neutron agent-list:
In the agent log, I see repeated critical and error messages indicating no lbdriver attribute on the LbaasAgentManager object. These error messages repeat for a time, then disappear.
After the errors disappear, the agent log looks like such. Note that the /usr/bin/f5-oslbaasv2-agent version is 8.3.0. This seems to be a reference to the neutron-lbaas version, which is 8.3.0, not of our own agent version, which differs from OpenStack by one.
Agent version and neutron-lbaas version. As far as I know, this problem has always existed though.
I do see the driver initialization in the neutron server.log, but of course there's no RPC communication with the agent.
Agent Version
mitaka
Operating System
CentOS 7
OpenStack Release
mitaka