Add Member action in loadbalancers does not enforce protocol as required field
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Undecided
|
Tatiana Ovchinnikova |
Bug Description
In Project-
1. Click on Members tab
2. Click on 'Add Member' button
**Make sure there are no instances to be added as members.**
Protocol Port is not a required field but if you don't enter the port, it fails with message "Unable to add members" which does not indicate the actual error.
Horizon log shows this error:
2015-11-30 21:09:39,964 DEBUG 25947 [neutronclient.
2015-11-30 21:09:39,964 DEBUG 25947 [neutronclient.
Neutron Log shows the following error:
2015-11-30 21:09:39,961 DEBUG [neutron.
2015-11-30 21:09:39,962 INFO [neutron.
Looks like the underlying problem is that protocol_port is removed as a requirement when there are no instances available to be selected as members. However, user can still choose the other way of entering the member ip address and will run into this problem (protocol_
description: | updated |
affects: | django-openstack-auth → horizon |
Changed in horizon: | |
assignee: | nobody → Tatiana Ovchinnikova (tmazur) |
Fix proposed to branch: master /review. openstack. org/252409
Review: https:/