Red Hat Bugzilla – Bug 1465989
"Error: source_type" when trying to create a Loadbalancer
Last modified: 2017-07-21 06:14:31 EDT
Description of problem:
From customer problem description:
I have created three instances called brie, camembert and cheddar. (screenshot 1).
I try to create a Load balancer called "cheese", by using the "Réseau (Network) > Load Balancer v2" menu Please note that I am translating from french, I do not know if the wording is exactly the same in the english version of horizon. I choose "Launch Load Balancer".
I choose "cheese" as "Nom (Name)", "Round Robin" as "Méthode de répartition de charge (Load balancing policy)", TCP as "LB Protocol", 22 as Instance Port and 22 as LB Port (screenshot 2).
On the Moniteur (Monitor) tab, I choose "PING" as Moniteur, 5 as "Health Check Interval", 3 as "Retry Count before markdown", and "test" for both "Send String" and "Receive String". '(Screenshot 3)
On the Instances tab, I choose my three instances ("cheddar", "camembert" and "brie") (Screenshot 4), and I clicked on "Démarrer (Start)".
I then get the following error "Erreur source_type" "Erreur Impossible de démarrer loadbalancer instance(s) nommée(s) "cheese"", which translates as "Error : impossible to start instances loadbalancer named "cheese"").
The same error also apperas in the log of our first controller (ycrta00); in /var/log/horizon/horizon.log as :
"2017-06-28 13:33:18,700 491719 WARNING horizon.exceptions Recoverable error: 'source_type'".
This seems related to https://bugs.launchpad.net/neutron-lbaas-dashboard/+bug/1629258
This is related to a plugin that we don't support (Neutron LBaaS Dashboard).
(In reply to Beth Elwell from comment #1)
> This is related to a plugin that we don't support (Neutron LBaaS Dashboard).
How about we remove it from the Dashboard then? :)
Currently it's only confusing people.
Created attachment 1295359 [details]
Launch Load Balancer Button snapshot
Let's leave this one as closed. If you could open a new bz for that issue that would be great and then we can look into how we will address that.