Description of problem: After executing lbaasv2 activation steps ( https://mojo.redhat.com/docs/DOC-1032130 - worked well for kilo) I tried to create LB. "neutron lbaas-loadbalancer-create 0414a04e-f7fe-42eb-8c2f-5abd8684b58c 404 Not Found The resource could not be found." Neutron agent-list command show lbaas agent as "xxx" and lbaasv2 agent is not shown ( was shown in Kilo) Version-Release number of selected component (if applicable): python-neutron-7.0.0-4.el7ost.noarch python-neutron-fwaas-7.0.0-1.el7ost.noarch python-neutron-lbaas-7.0.0-2.el7ost.noarch python-neutronclient-3.1.0-1.el7ost.noarch openstack-neutron-lbaas-7.0.0-2.el7ost.noarch openstack-neutron-7.0.0-4.el7ost.noarch openstack-neutron-openvswitch-7.0.0-4.el7ost.noarch openstack-neutron-common-7.0.0-4.el7ost.noarch openstack-neutron-fwaas-7.0.0-1.el7ost.noarch openstack-neutron-ml2-7.0.0-4.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Install openstack with packstack ( make sure CONFIG_LBAAS_INSTALL=y in answerfile) 2.Enable lbaasv2, create internal net and subnet. https://mojo.redhat.com/docs/DOC-1032130 3. run - neutron lbaas-loadbalancer-create VIPSUBNETID ( internal subnet) Actual results: "neutron lbaas-loadbalancer-create 0414a04e-f7fe-42eb-8c2f-5abd8684b58c 404 Not Found The resource could not be found." Expected results: Loadbalancer should be created. Additional info: Logs: http://pastebin.com/LLz3BKFy
Still relevant?
(In reply to Assaf Muller from comment #3) > Still relevant? Nope- Works on Liberty
will verify again anyway
Hi Alex, Please let me know if there is any action needed here. This seems like something you guys will catch on sanity tests.
Closing, please re-open if needed.