provider/openstack: Fix create/delete statuses in load balancing resources for openstack provider.

[pfrybar]

When trying to create a complete load balancer in Openstack, I would often run into the following error:

* openstack_lb_member_v1.lb_member.1: unexpected state 'PENDING_CREATE', wanted target '[ACTIVE]'

After digging around in the code, I saw that the Pending status was different for the various LB resources (member, monitor, pool, and vip). Based on the source code for neutron lbaas, I found that the statuses should be as follows:

Create resource - 'PENDING_CREATE' - https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_db.py - lines 379, 593, 659, and 728.

Delete resource - 'PENDING_DELETE' - https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/services/loadbalancer/plugin.py - lines 167, 250, 277, and 341.

After making this change, and re-compiling the openstack provider, I have not seen the error after multiple deployments.

Note: the create resource for vip (resource_openstack_lb_vip_v1.go) already has the Pending status set to 'PENDING_CREATE'.

[jtopjian]

Thanks so much for this!

I'll run it through the acceptance test suite as soon as I have a chance and then merge this in.

[pfrybar]

Sounds good!

[jtopjian]

All looks good to me! Thanks again for fixing this.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.