Created attachment 1070749 [details] horizon log Description of problem: ======================= Error: "Unable to connect to Neutron" displays when instance table displays on project tab. This error display after creating instance. Version-Release number of selected component: ============================================= python-django-horizon-2014.1.5-1.el7ost.noarch openstack-dashboard-2014.1.5-1.el7ost.noarchpython-neutron-2014.1.5-2.el7ost.noarch openstack-neutron-openvswitch-2014.1.5-2.el7ost.noarch openstack-neutron-2014.1.5-2.el7ost.noarch python-neutronclient-2.3.4-3.el7ost.noarch openstack-neutron-ml2-2014.1.5-2.el7ost.noarch How reproducible: ================= 100% Steps to Reproduce: =================== 1. Create a network 2. Launch an instance with that network Actual results: ================= Instances created successfully, but Error: "Unable to connect to Neutron" displays on Project --> Instances Expected results: ================= Instances created successfully, no errors Additional info:
Created attachment 1070750 [details] neutron metadata agent.log
Created attachment 1070751 [details] neutron server log
Created attachment 1070752 [details] l3-aget.log
Created attachment 1070753 [details] openvswich-agent.log
This works with nova network, but not with neutron enabled.
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Patch referenced in comment #8 https://review.openstack.org/#/c/189459/ - icehouse patch was abandoned https://review.openstack.org/#/c/114088/ - master patch was merged
*** Bug 1274252 has been marked as a duplicate of this bug. ***
Hi, Customer is requesting for the hotfix. I am not aware of the procedure for requesting the hotfix, do I need to follow a procedure / form to do that? Cheers Faiaz
cloned and split bug for OSP 5 - rhel 6
Verified ======== python-django-horizon-2014.1.5-2.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0508.html