yahoo-eng-team team mailing list archive

[Radomir Dopieralski <1920010@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If there are more than Nova's pagination limit instances, and one tries
to associate a floating IP with a new instance, the form's validation
will fail.

This is because that form populates the drop-down field for association
target differently on initial display of the form (where it takes the
instance_id from the URL) than on submitting of that form (when the
information from the URL is lost). The latter attempts to get all
eligible ports, but is limited by Nova's pagination.

You can also observe weird behavior when that form has any error (for
instance, because the floating IP wasn't selected) — after submitting,
it will re-display the form with the error, but now the target drop-down
will be populated with all possible ports, instead of only ones on the
instance, like on the initial display.

** 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/1920010

Title:
  Validation on fails on the Associate Floating IP when too many
  instances exist

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  If there are more than Nova's pagination limit instances, and one
  tries to associate a floating IP with a new instance, the form's
  validation will fail.

  This is because that form populates the drop-down field for
  association target differently on initial display of the form (where
  it takes the instance_id from the URL) than on submitting of that form
  (when the information from the URL is lost). The latter attempts to
  get all eligible ports, but is limited by Nova's pagination.

  You can also observe weird behavior when that form has any error (for
  instance, because the floating IP wasn't selected) — after submitting,
  it will re-display the form with the error, but now the target drop-
  down will be populated with all possible ports, instead of only ones
  on the instance, like on the initial display.

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