F5Networks / f5-openstack-lbaasv1

OpenStack Neutron LBaaSv1 plugin and agent to control F5 BIG-IP devices
http://f5-openstack-lbaasv1.readthedocs.io
6 stars 8 forks source link

Agent repeatedly changes autosync setting on BIG-IP #134

Closed mattgreene closed 8 years ago

mattgreene commented 8 years ago

@jlongstaf

Issues: Fixes #132

Problem: Agent stuck in loop connecting to BIG-IP, changing autosync settings, then failing to connect to another BIG-IP in the cluster and raising out. BIG-IP 11.6.1 changed the behavior of an API to fetch cluster devices. The old behavior returned the device name in the 'name' field. The new behavior returns '/Common/' + name in the name field. The agent code fails to resolve this new name to extract the mgmt address, hence cannot connect. In the customer environment, the first device in the cluster was 11.6.0 (connects and sets autosync) and the next device was 11.6.1 (fails to connect and cause agent to terminate).

Analysis: Without checking the device version, add a simple method to check and remove '/Common/' from the front of a string and use this new method to normalize the device name when building out an ha cluster.

Tests: Recreated the agent failure and confirmed via log messages that normalizing the device name enables the agent to locate all devices in the cluster and attempt to connect.