Mention Octavia on logs when loadbalancer transtion to PENDING_UPDATE

[Maysa de Macedo Souza]

If LB is stuck in `PENDING_UPDATE` state we need to clearly log that it's Octavia misbehaving and not raise some ambiguous `ResourceNotReady` exception.

[Darshna Das (climoiselle)]

Hi, I am an outreachy applicant. I am done setting up the local machine, is it okay if I take up this issue to start with?

[Maysa de Macedo Souza (maysa)]

Yes, sure, that's okay. Please reach out if you have questions/concerns.

[Darshna Das (climoiselle)]

Hello, can anyone help me on how to get started with this issue?

[Michal Dulko (michal-dulko-f)]

Sure! Basically if at [1] status is PENDING_UPDATE we should log a clear information that there is an issue with Octavia because the LB <id> is stuck in PENDING_UPDATE and Kuryr is unable to clear this.

[1] https://github.com/openstack/kuryr-kubernetes/blob/e21d2f3d8bc12384fb2e352e024e2637c523b1e3/kuryr_kubernetes/controller/drivers/lbaasv2.py#L831

[Darshna Das (climoiselle)]

Ah! thank you :)

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Darshna Das <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/kuryr-kubernetes/+/789052
Reason: Did not mention the bug_id

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/kuryr-kubernetes/+/796881

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/kuryr-kubernetes/+/796881
Committed: https://opendev.org/openstack/kuryr-kubernetes/commit/a17e5502c2702632317b8f51fb404a3e7c8874ea
Submitter: "Zuul (22348)"
Branch: master

commit a17e5502c2702632317b8f51fb404a3e7c8874ea
Author: Michał Dulko <email address hidden>
Date: Thu Jun 17 17:30:17 2021 +0200

    Show error messages when resources are stuck

    If an Octavia loadbalancer is stuck in PENDING_UPDATE state or Neutron
    port is DOWN despite being plugged there's not much Kuryr can do. For
    such cases we need to clearly message the user that the error they're
    seeing is caused by OpenStack service misbehaving and not Kuryr.

    This commit does so by making sure in such cases we raise a distinct
    version of ResourceNotReady exception.

    Change-Id: I2dd1e8989caf004b3dee0cb51780a45ce8d9353c
    Closes-Bug: 1918711

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-kubernetes 5.0.0.0rc1 release candidate.