Temporarily disable this check until we figure out why
operational_status sometimes does not become 'ONLINE'
while the member does indeed work and the subsequent
retrieval of payload through loadbalancer is successful
ref LP: #1896729.
Creating a load balancer consist of many independent API calls.
If any one of them fail today the whole job will be killed.
On failure to create a lb resoruce, clean up and retry.
When running in a deployment that is focused on bundles rather
than a specific charm, the Octavia setup can fail because there
is no configured charm_name in the tests.yaml. This change
ensures that the Octavia setup can continue.
The current test code for octavia requires DVR extensions to be
present on the Neutron API server.
We need to conditionally enable this based on enabled extensions to
allow the test to operate on multiple deployment configurations.
The existing code lead to intermittent failures as there are a few
Neutron ports tagged with ``device:owner`` ``compute:nova`` that
has nothing to do with our payload instances.
Get IP information by asking Nova to list instances instead.
Setup can be used standalone by other charms consuming the
``octavia-diskimage-retrofit`` charm for their testing purposes.
Tests the charms actions.
Full end to end test will be done by consuming this charm in the
``octavia`` charm tests.