[Build-14]:UI:"Internal Server Error" while associating an instance to a floating IP"

Bug #1323984 reported by Ruchi Priya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Fix Released
High
Ruchi Priya

Bug Description

An association of instance with a Floating IP is giving error saying to add valid instance.
The instance has been selected from the drop down available.
The above operation is a success through open-stack

The network was created successfully .

The snapshot is attached.
setup info
:
host1 = 'root@10.204.216.63'
host2 = 'root@10.204.216.64'
host3 = 'root@10.204.216.65'
host4 = 'root@10.204.216.66'
host5 = 'root@10.204.216.67'
env.roledefs = {
    'all': [host1, host2, host3, host4, host5],
    'cfgm': [host1, host2, host3],
    'openstack': [host2],
    'control': [host2, host3],
    'compute': [host4, host5],
    'collector': [host1],
    'webui': [host1],
    'database': [host1, host2],
    'build': [host_build],
}

env.hostnames = {
    'all': ['nodec6', 'nodec7', 'nodec8', 'nodec9', 'nodec10']
}

Tags: ui
Revision history for this message
Ruchi Priya (ruchip) wrote :
Revision history for this message
Vedamurthy Joshi (vedujoshi) wrote :

This is seen when the fip pool is created from Contrail UI

If its created using router:external option, it works fine.

Changed in juniperopenstack:
assignee: nobody → Hampapur Ajay (hajay)
Revision history for this message
Rahul (rahuls) wrote :

Not sure of router:external, but as such UI has not been updated to handle VM/VMI related schema changes.

Changed in juniperopenstack:
assignee: Hampapur Ajay (hajay) → Balamurugan Gopal (gbala)
asbalaji (asbalaji)
Changed in juniperopenstack:
status: New → Fix Committed
assignee: Balamurugan Gopal (gbala) → Ruchi Priya (ruchip)
milestone: none → r1.06-fcs
Rahul (rahuls)
Changed in juniperopenstack:
status: Fix Committed → Fix Released
information type: Proprietary → Public
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.