Services of type LoadBalancer: IP appears in the status before LB was completely provisioned in Openstack

[Yossi Boaron]

In OpenStack with LBaaSV2 and provider=Octavia, it could take ~200 seconds to provision a load balancer.

Kuryr should update the Floating IP under service/status field after the LB was totally provisioned.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/554070

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/554070
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=e0dfd36e36887b7d56ff762e86741f1a6cb5e161
Submitter: Zuul
Branch: master

commit e0dfd36e36887b7d56ff762e86741f1a6cb5e161
Author: Yossi Boaron <email address hidden>
Date: Sun Mar 18 22:47:29 2018 +0200

    Services: update service's status after LB completely provisioned.

    When creating a service of type 'LoadBalancer', you create
    a cloud network load balancer.
    This provides an externally-accessible IP address that sends
    traffic to the correct port on your cluster nodes.
    The external IP address is stored in k8s service's status
    information (under loadbalancer/ingress/ip).

    Kuryr implements this capability using OpenStack floating IP
    functionality.
    This patch updates Kuryr to store external IP information only after
    LB was entirely configured in OpenStack.

    Change-Id: I1d43f03d49d6e760c859f219aa9a4c209087c753
    Closes-Bug: 1756730

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559280

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/559280
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=c7528a132ddf601dc121dc4b092d2ea22f6134a1
Submitter: Zuul
Branch: stable/queens

commit c7528a132ddf601dc121dc4b092d2ea22f6134a1
Author: Yossi Boaron <email address hidden>
Date: Sun Mar 18 22:47:29 2018 +0200

    Services: update service's status after LB completely provisioned.

    When creating a service of type 'LoadBalancer', you create
    a cloud network load balancer.
    This provides an externally-accessible IP address that sends
    traffic to the correct port on your cluster nodes.
    The external IP address is stored in k8s service's status
    information (under loadbalancer/ingress/ip).

    Kuryr implements this capability using OpenStack floating IP
    functionality.
    This patch updates Kuryr to store external IP information only after
    LB was entirely configured in OpenStack.

    Change-Id: I1d43f03d49d6e760c859f219aa9a4c209087c753
    Closes-Bug: 1756730
    (cherry picked from commit e0dfd36e36887b7d56ff762e86741f1a6cb5e161)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-kubernetes 0.4.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-kubernetes 0.5.0 release.