Description of problem: Hello all, I'm trying to add a new host selecting an external neutron network provider. The host ( RHEL 7.3 standard ) has those repositories enabled: jb-eap-7-for-rhel-7-server-rpms rhel-7-server-extras-rpms rhel-7-server-openstack-10-devtools-rpms rhel-7-server-openstack-10-rpms rhel-7-server-rhv-4-mgmt-agent-rpms rhel-7-server-rhv-4.0-rpms rhel-7-server-rpms rhel-7-server-supplementary-rpms The deploy will fail with the error "Invalid response from OVS" Looking the host-deploy log I found the error: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) I think this could be caused because the openvswitch service is started and in the same moment the command ovs-vsctl is used. Activating first the service and after using the command will work succesfully. I also replicated the error running the ovs-vsctl command when openvswitch service is still disabled. Version-Release number of selected component (if applicable): RHEV 4.0.7 RHOSP 10 How reproducible: 100% Steps to Reproduce: 1. Install RHEV 4.0.7 2. Configure RHOSP10 repositories on the hypervisor will be added 3. Add a new hypervisor with the external network provider Actual results: The deploy will fail with the "Invalid response from OVS" error Expected results: The deploy must finish succesfully Additional info: A short extract from the log: 2017-04-04 14:49:35 DEBUG otopi.plugins.ovirt_host_deploy.openstack.neutron plugin.execute:926 execute-output: ('/bin/openstack-config', '--set', '/etc/neutron/neutron.conf', 'DEFAULT', 'rabbit_host', '172.16.16.108') stderr: 2017-04-04 14:49:35 DEBUG otopi.context context._executeMethod:128 Stage misc METHOD otopi.plugins.ovirt_host_deploy.openstack.neutron_linuxbridge.Plugin._misc 2017-04-04 14:49:35 DEBUG otopi.context context._executeMethod:134 condition False 2017-04-04 14:49:35 DEBUG otopi.context context._executeMethod:128 Stage misc METHOD otopi.plugins.ovirt_host_deploy.openstack.neutron_openvswitch.Plugin._bridge 2017-04-04 14:49:35 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting service openvswitch 2017-04-04 14:49:35 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute: ('/bin/systemctl', 'start', 'openvswitch.service'), executable='None', cwd='None', env=None 2017-04-04 14:49:35 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863 execute-result: ('/bin/systemctl', 'start', 'openvswitch.service'), rc=0 2017-04-04 14:49:35 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921 execute-output: ('/bin/systemctl', 'start', 'openvswitch.service') stdout: 2017-04-04 14:49:35 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/bin/systemctl', 'start', 'openvswitch.service') stderr: 2017-04-04 14:49:35 DEBUG otopi.plugins.ovirt_host_deploy.openstack.neutron_openvswitch plugin.executeRaw:813 execute: ('/bin/ovs-vsctl', 'br-exists', 'br-int'), executable='None', cwd='None', env=None 2017-04-04 14:49:35 DEBUG otopi.plugins.ovirt_host_deploy.openstack.neutron_openvswitch plugin.executeRaw:863 execute-result: ('/bin/ovs-vsctl', 'br-exists', 'br-int'), rc=1 2017-04-04 14:49:35 DEBUG otopi.plugins.ovirt_host_deploy.openstack.neutron_openvswitch plugin.execute:921 execute-output: ('/bin/ovs-vsctl', 'br-exists', 'br-int') stdout: 2017-04-04 14:49:35 DEBUG otopi.plugins.ovirt_host_deploy.openstack.neutron_openvswitch plugin.execute:926 execute-output: ('/bin/ovs-vsctl', 'br-exists', 'br-int') stderr: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) 2017-04-04 14:49:35 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/tmp/ovirt-ewDqHd306d/pythonlib/otopi/context.py", line 132, in _executeMethod method['method']() File "/tmp/ovirt-ewDqHd306d/otopi-plugins/ovirt-host-deploy/openstack/neutron_openvswitch.py", line 186, in _bridge odeploycons.OpenStackEnv. File "/tmp/ovirt-ewDqHd306d/otopi-plugins/ovirt-host-deploy/openstack/neutron_openvswitch.py", line 79, in _createBridge raise RuntimeError(_('Invalid response from OVS')) RuntimeError: Invalid response from OVS 2017-04-04 14:49:35 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Misc configuration': Invalid response from OVS 2017-04-04 14:49:35 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' 2017-04-04 14:49:35 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Performing yum transaction rollback
It doesn't seem related to rhev-h, moving to ovirt-host-deploy component.
Moving to network for further investigation since they own the ovs support feature. Looks like a regression due to changes in RHOSP10 but I let network team investigate.
We do not support the deployment of Neutron services on the hosts. In any case, you can try to install the needed OSP packages and try again. We only support manual configuration in 4.0 and in RHV 4.1 we added support of using director provisioned networker nodes.
Hello, we were trying to integrate RHEV with an external network provider, in this case RHOSP 10. Our neutron services are OVS and neutron agent. Are you saying what is described here is not supported? http://rhelblog.redhat.com/2016/09/19/integrating-red-hat-virtualization-and-red-hat-openstack-platform-with-neutron-networking/ " The actual steps to take advantage of the integration between RHV 4 and RHOSP 8 are straightforward. The steps are as follows: Install the OpenStack Neutron packages on the RHV hypervisor hosts Configure hosts (hypervisor nodes) – a very quick text edit Define OpenStack Neutron as an “External Network Provider” in RHV Manager Create one or more hosts in RHV that utilize the Neutron integration Import one or more networks from RHOSP into RHV Create one or more virtual machines that use the Neutron network(s) " Regards Alessio Dini
(In reply to Alessio from comment #4) > Hello, > we were trying to integrate RHEV with an external network provider, in this > case RHOSP 10. Our neutron services are OVS and neutron agent. > Are you saying what is described here is not supported? > It is support, as this says: > Install the OpenStack Neutron packages on the RHV hypervisor hosts Right now you have missing packages. > Configure hosts (hypervisor nodes) – a very quick text edit This means doing manual configuration of the Neutron agent.
Ok, so adding hosts with external providers via administration portal is not supported. Can I suggest to add a message or some warning in the network provider tab? Something like "WARNING: Adding hosts with network provider is not supported!". I'm asking because this limitation it's missing, also on the official Redhat documentation. Regards Alessio Dini
Created attachment 1279968 [details] Neutron providing add host warning We already provide a warning about deployment of Neutron provider.
(In reply to Leon Goldberg from comment #8) > Created attachment 1279968 [details] > Neutron providing add host warning > > We already provide a warning about deployment of Neutron provider. Hello, in the comment #3 Yaniv Dary said is not supported to add hosts with external provider via rhevm dashboard. I actually checked again the warning you are talking about. From the dashboard,adding a new hosts selecting the external provider section it will display: "Automatic deployment of the Neutron provider on host may not work. It is highly recommended to manually deploy the OVS agent on the host." This is different from a not supported operation. This detail is missing from any documentation, as well as the supported operation: 1) Install packages and manually configure neutron agents on the host u want to add to a cluster 2) Add the host via rhevm dashboard without selecting the network provider section ( in 4.1 we can't add additional hosts via hosted-engine command ) Best Regards Alessio Dini
Leon, could you suggest a clearer text (and where it should be placed) for our documentation?
*** Bug 1446264 has been marked as a duplicate of this bug. ***
Moving to 'NEW' to be reassigned as resources allow. Dan, did you mean to set a needinfo here?
Let add a note the docs we created for director integration that it is the only support path in RHV.
Assigning to Emma for review. Emma, we need to add a note to the following section in 4.1: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-Adding_External_Providers#Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning The note should state that using the Red Hat OpenStack Platform director to deploy the Networker role on a network node before adding it to the Red Hat Virtualization Manager as a host is the only supported method for integrating OpenStack Networking with RHV.
Hi Leon In addition to adding the note that Lucy suggested, I think the documentation needs a couple more clarifications. 1. In the following sentence, shouldn't we say that it is a Manual configuration? "To use neutron networks, hosts must have the neutron agents configured." Is this configuration done via the Director? 2. Shouldn't we also change the text in the following section from "you CAN use the director" to you Must use the director... 7.5.4. Adding a Red Hat OpenStack Platform Network Node as a Host https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-host_tasks#Adding_a_RHOSP_Network_Node_as_a_Host
Hi Marcin. Leon suggested I consult with you about the questions in comment 15. Thanks!
Since the original bug could be important, could you please provider the version info for the env: yum info openvswitch
Text approved by Yaniv.
Now published at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-adding_external_providers#Adding_an_OpenStack_Network_Service_Neutron_for_Network_Provisioning and https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-Host_Tasks#Adding_a_RHOSP_Network_Node_as_a_Host