kuryr-kubernetes

  1. Bug #1918711
  2. Comment #8

Comment 8 for bug 1918711

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (master)

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