Validation on fails on the Associate Floating IP when too many instances exist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Undecided
|
Unassigned |
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.
It is fixed by https:/ /review. opendev. org/c/openstack /horizon/ +/780925.