+++ This bug was initially created as a clone of Bug #1019818 +++ Description of problem: If external Neutron provider is selected during new host install, then When ovirt-host-deploy attempts to install the layer 2 agent it uses "quantum" instead of "neutron". Havana changed the path of configuration files and such to use neutron. Version-Release number of selected component (if applicable): oVirt 3.3 from master How reproducible: 100% Steps to Reproduce: 1. Add new host with external Neutron provider Actual results: New host install fails when trying to install layer 2 agent. Attached logs. Expected results: New host install should succeed. --- Additional comment from Alon Bar-Lev on 2013-10-16 09:04:03 EDT --- A patch will be welcomed. --- Additional comment from Assaf Muller on 2013-10-16 09:05:18 EDT --- Possible solutions / implications: Currently we "support" Neutron integration with Grizzly where the name was still quantum. Havana changed the name to neutron. Should we just move to support havana? Does this have release notes implications? Should we add a select box to the GUI when adding a host instead? --- Additional comment from Dan Kenigsberg on 2013-10-18 18:14:04 EDT --- We cannot just drop the support for Grizzly during the ovirt-3.3 lifetime. So we should support both Grizzly and Havana. I see no reason to add a UI checkbox: ovirt-host-deploy should handle whatever version is available at the host. If Engine must know the version installed on the host, Vdsm should report it. --- Additional comment from Alon Bar-Lev on 2013-10-19 02:42:31 EDT --- As far as I know, openstack is not 'supported' it is 'release preview', in other words it is 'experimental'. I see no problem to require newer openstack component at any stage. --- Additional comment from Dan Kenigsberg on 2013-10-19 09:03:47 EDT --- Ok, it makes sense to use the benefits of being a "tech preview".
rhevm-3.3.0-0.40.rc.el6ev.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. http://rhn.redhat.com/errata/RHBA-2014-0074.html