yahoo-eng-team team mailing list archive

[Tara-K <2004243@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In Horizon under Network > Floating IPs, we are seeing errors when
trying to click on the "Mapped Fixed IP Address" info if the FIP in
question is  associated with an Octavia Loadbalancer rather than an
Instance.

We see the following error:
Error: Unable to retrieve details for instance "lb-<octavia-lb-id>". Details
Instance lb-<octavia-lb-id> could not be found. (HTTP 404)

It attempts to locate an instance ID instead of a Loadbalancer. The
issue only occurs when the port contains an "lb-" prefix.

Are there plans to implement a fix for this, or has it already been
addressed from the Xena upgrade onwards?

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/2004243

Title:
  Mapped Fixed IP Address error for Octavia LB IPs

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In Horizon under Network > Floating IPs, we are seeing errors when
  trying to click on the "Mapped Fixed IP Address" info if the FIP in
  question is  associated with an Octavia Loadbalancer rather than an
  Instance.

  We see the following error:
  Error: Unable to retrieve details for instance "lb-<octavia-lb-id>". Details
  Instance lb-<octavia-lb-id> could not be found. (HTTP 404)

  It attempts to locate an instance ID instead of a Loadbalancer. The
  issue only occurs when the port contains an "lb-" prefix.

  Are there plans to implement a fix for this, or has it already been
  addressed from the Xena upgrade onwards?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/2004243/+subscriptions