"Error: source_type" when trying to create a loadbalancer

Bug #1629258 reported by Alfredo Moralejo
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Neutron LBaaS Dashboard
New
Undecided
Unassigned

Bug Description

Using newton rc2 versions of packages from RDO and current master HEAD of neutron-lbaas-dashboard https://github.com/openstack/neutron-lbaas-dashboard/commit/63d4427a3bad36a16c6d77e3b057db1a5a8f46a2

When i try to create a new load balancer from dashboard i get errors:

"Error: source_type"
"Error: Unable to launch loadbalancer named "test1"."

And following message appears in horizon log:

2016-09-30 10:03:20,771 22117 WARNING horizon.exceptions Recoverable error: 'source_type'

Revision history for this message
Donny Davis (automatikdonn) wrote :

This bug still around, but I think that things are moving to octavia anyways. It's unlikely it will be addressed

Revision history for this message
Saverio Proto (zioproto) wrote :

Is this related to bug #1621403 ?

Revision history for this message
Saverio Proto (zioproto) wrote :

On top of my horizon newton installation I am trying the following:

pip install --upgrade pip
pip install oslo_log
pip install neutron-lbaas-dashboard
cp /usr/local/lib/python2.7/dist-packages/neutron_lbaas_dashboard/enabled/* /usr/share/openstack-dashboard/openstack_dashboard/local/enabled/
/usr/share/openstack-dashboard/manage.py collectstatic --noinput
/usr/share/openstack-dashboard/manage.py compress --force
service apache2 restart

Looks like I have no problem importing the panel:

Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from neutron_lbaas_dashboard.dashboards.project.ngloadbalancersv2 import panel
>>>

I am getting this error when I try to create a new load balancer:

in /var/log/horizon/horizon.log

2017-03-13 12:38:18,591 29 WARNING horizon.exceptions Recoverable error: 'source_type'

The system has already some LBaaSv2 that I can list with the CLI doing
neutron lbaas-loadbalancer-list

(neutron) lbaas-loadbalancer-list
+--------------------------------------+-------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
+--------------------------------------+-------+-------------+---------------------+----------+
| 44c9b3a3-cfc3-4b31-92e0-4eef2fbd353e | vipV1 | 10.0.77.113 | ONLINE | haproxy |
+--------------------------------------+-------+-------------+---------------------+----------+
(neutron)

BUT the Horizon panel is always empty and does not show this load balancer.

Revision history for this message
Saverio Proto (zioproto) wrote :

My versions:

neutron-lbaas==8.3.0
neutron-lbaas-dashboard==2.0.1.dev4

Revision history for this message
György Szombathelyi (gyurco) wrote :

I don't think it's a duplicate. The panel is there, I can create the LB, but after clicking on the Launch button,
"Error: source_type"
"Error: Unable to launch loadbalancer named "lb1"."
appears in Horizon.

Btw, the version is current HEAD from stable/ocata (with Horizon from Ocata).

Revision history for this message
György Szombathelyi (gyurco) wrote :

Ok, seems only the "old" lbaasv2 dashboard is affected, so simply use the ngloadbalancersv2 panel.

Install just the
openstack_dashboard/enabled/_1481_project_ng_loadbalancersv2_panel.py
and not the
openstack_dashboard/enabled/_1480_project_loadbalancersv2_panel.py

Revision history for this message
Alfredo Moralejo (amoralej) wrote :

Thanks for the help.

It works fine when using ngloadbalancersv2 in ocata, i'll test it for newton also. If i understand correctly, old panel is not longer used, right?

Revision history for this message
György Szombathelyi (gyurco) wrote :

I guess it is more like no longer maintained. But you don't need two panels for the same job, right? Both are GUIs for the lbaasv2 API.

Revision history for this message
Alfredo Moralejo (amoralej) wrote :

Yes, that's my understanding also. I wonder why the old one is not just removed from the repo.

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.