Fix grenade resource waiters

The grenade job resource.sh script is waiting for the created object
status but not the overall load balancer status to go ACTIVE.
This can lead to the script failing with a 409 error.

This patch adds a check for the load balancer to be unlocked before
advancing to the next create call.

Change-Id: I6505243ddbf1eab7d110e9bfa03bffda840f07ae
This commit is contained in:
Michael Johnson 2021-03-05 01:37:52 +00:00
parent 79268cc9e3
commit d17b23282c
1 changed files with 5 additions and 0 deletions

View File

@ -49,18 +49,23 @@ function create {
openstack loadbalancer listener create --name listener1 --protocol HTTP --protocol-port 80 lb1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer listener show listener1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer show lb1
openstack loadbalancer pool create --name pool1 --lb-algorithm ROUND_ROBIN --listener listener1 --protocol HTTP
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer pool show pool1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer show lb1
openstack loadbalancer healthmonitor create --delay 5 --max-retries 4 --timeout 10 --type HTTP --url-path / --name hm1 pool1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer healthmonitor show hm1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer show lb1
openstack loadbalancer member create --subnet-id $PRIVATE_SUBNET_NAME --address $vm1_ipv4 --protocol-port 80 pool1 --name member1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer member show pool1 member1
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer show lb1
openstack loadbalancer member create --subnet-id $PRIVATE_SUBNET_NAME --address $vm2_ipv4 --protocol-port 80 pool1 --name member2
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer member show pool1 member2
_wait_for_status "ACTIVE" "ONLINE" openstack loadbalancer show lb1
lb_vip_ip=$(openstack loadbalancer show -f value -c vip_address lb1)
resource_save octavia lb_vip_ip $lb_vip_ip