Re: [openstack-dev] [Fuel][Neutron ML2][VMWare]NetworkNotFoundForBridge: Network could not be found for bridge br-int

2015-01-27 Thread Foss Geek
Hi Xarses,

Actually it is multi-hypervisor environment. The error in the nova.log is:

 NetworkNotFoundForBridge: Network could not be found for bridge br-int

the above error disappears changing the mech driver order in
/etc/neutron/plugins/ml2/ml2_conf.ini  file from mechanism_drivers =
openvswitch,dvs  to mechanism_drivers =dvs, openvswitch



On Mon, Jan 19, 2015 at 12:31 PM, Foss Geek thefossg...@gmail.com wrote:

 Hi Xarses,

 Thanks for your time!

 I was not able to check my mail yesterday. Sorry for the delay.

 One of my colleague fixed this issue yesterday. I will understand the
 issue and update this thread.

 --
 Thanks  Regards
 E-Mail: thefossg...@gmail.com
 IRC: neophy
 Blog : http://lmohanphy.livejournal.com/



 On Sat, Jan 17, 2015 at 1:17 AM, Andrew Woodward xar...@gmail.com wrote:

 neophy,

 It seems like there are left overs that fuel was using in the config
 that would not be present when you installed neutron fresh. I'd
 compare the config files and start backing out bits you dont need. I'd
 start with the lines refrencing br-int, you dont need them on nodes
 that aren't using the ovs agent.

 Poke me on IRC if you need more help

 Xarses (GMT-8)

 On Fri, Jan 9, 2015 at 1:08 PM, Foss Geek thefossg...@gmail.com wrote:
  Dear All,
 
  I am trying to integrate Openstack + vCenter + Neutron + VMware
 dvSwitch ML2
  Mechanism driver.
 
  I deployed a two node openstack environment (controller + compute with
 KVM)
  with Neutron VLAN + KVM using fuel 5.1. Again I installed nova-compute
 using
  yum in controller node and configured nova-compute in controller to
 point
  vCenter. I am also using Neutron VLAN with VMware dvSwitch ML2 Mechanism
  driver. My vCenter is properly configured as suggested by the doc:
 
 https://www.mirantis.com/blog/managing-vmware-vcenter-resources-mirantis-openstack-5-0-part-1-create-vsphere-cluster/
 
  I am able to create network from Horizon and I can see the same network
  created in vCenter. When I try to create a VM I am getting the below
 error
  in Horizon.
 
  Error: Failed to launch instance test-01: Please try again later
 [Error:
  No valid host was found. ].
 
  Here is the error message from Instance Overview tab:
 
  Instance Overview
  Info
  Name
  test-01
  ID
  309a1f47-83b6-4ab4-9d71-642a2000c8a1
  Status
  Error
  Availability Zone
  nova
  Created
  Jan. 9, 2015, 8:16 p.m.
  Uptime
  0 minutes
  Fault
  Message
  No valid host was found.
  Code
  500
  Details
  File
 /usr/lib/python2.6/site-packages/nova/scheduler/filter_scheduler.py,
  line 108, in schedule_run_instance raise
 exception.NoValidHost(reason=)
  Created
  Jan. 9, 2015, 8:16 p.m
 
  Getting the below error in nova-all.log:
 
 
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.135 31870
 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Authenticating user token
  __call__
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:676
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.136 31870
 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Removing headers from
 request
  environment:
 
 X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
  _remove_auth_headers
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:733
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.137 31870
 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Returning cached token
  _cache_get
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:1545
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.138 31870
 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Storing token in cache store
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:1460
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.139 31870
 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Received request from user:
  4564fea80fa14e1daed160afa074d389 with project_id :
  dd32714d9009495bb51276e284380d6a and roles: admin,_member_
  _build_user_headers
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:996
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.141 31870
 DEBUG
  routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Matched
 GET
 
 /dd32714d9009495bb51276e284380d6a/servers/309a1f47-83b6-4ab4-9d71-642a2000c8a1
  __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.142 31870
 DEBUG
  routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Route
 path:
  '/{project_id}/servers/:(id)', defaults: 

Re: [openstack-dev] [Fuel][Neutron ML2][VMWare]NetworkNotFoundForBridge: Network could not be found for bridge br-int

2015-01-18 Thread Foss Geek
Hi Xarses,

Thanks for your time!

I was not able to check my mail yesterday. Sorry for the delay.

One of my colleague fixed this issue yesterday. I will understand the issue
and update this thread.

-- 
Thanks  Regards
E-Mail: thefossg...@gmail.com
IRC: neophy
Blog : http://lmohanphy.livejournal.com/



On Sat, Jan 17, 2015 at 1:17 AM, Andrew Woodward xar...@gmail.com wrote:

 neophy,

 It seems like there are left overs that fuel was using in the config
 that would not be present when you installed neutron fresh. I'd
 compare the config files and start backing out bits you dont need. I'd
 start with the lines refrencing br-int, you dont need them on nodes
 that aren't using the ovs agent.

 Poke me on IRC if you need more help

 Xarses (GMT-8)

 On Fri, Jan 9, 2015 at 1:08 PM, Foss Geek thefossg...@gmail.com wrote:
  Dear All,
 
  I am trying to integrate Openstack + vCenter + Neutron + VMware dvSwitch
 ML2
  Mechanism driver.
 
  I deployed a two node openstack environment (controller + compute with
 KVM)
  with Neutron VLAN + KVM using fuel 5.1. Again I installed nova-compute
 using
  yum in controller node and configured nova-compute in controller to point
  vCenter. I am also using Neutron VLAN with VMware dvSwitch ML2 Mechanism
  driver. My vCenter is properly configured as suggested by the doc:
 
 https://www.mirantis.com/blog/managing-vmware-vcenter-resources-mirantis-openstack-5-0-part-1-create-vsphere-cluster/
 
  I am able to create network from Horizon and I can see the same network
  created in vCenter. When I try to create a VM I am getting the below
 error
  in Horizon.
 
  Error: Failed to launch instance test-01: Please try again later
 [Error:
  No valid host was found. ].
 
  Here is the error message from Instance Overview tab:
 
  Instance Overview
  Info
  Name
  test-01
  ID
  309a1f47-83b6-4ab4-9d71-642a2000c8a1
  Status
  Error
  Availability Zone
  nova
  Created
  Jan. 9, 2015, 8:16 p.m.
  Uptime
  0 minutes
  Fault
  Message
  No valid host was found.
  Code
  500
  Details
  File
 /usr/lib/python2.6/site-packages/nova/scheduler/filter_scheduler.py,
  line 108, in schedule_run_instance raise exception.NoValidHost(reason=)
  Created
  Jan. 9, 2015, 8:16 p.m
 
  Getting the below error in nova-all.log:
 
 
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.135 31870 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Authenticating user token
  __call__
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:676
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.136 31870 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Removing headers from request
  environment:
 
 X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
  _remove_auth_headers
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:733
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.137 31870 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Returning cached token
  _cache_get
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:1545
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.138 31870 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Storing token in cache store
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:1460
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.139 31870 DEBUG
  keystoneclient.middleware.auth_token
  [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Received request from user:
  4564fea80fa14e1daed160afa074d389 with project_id :
  dd32714d9009495bb51276e284380d6a and roles: admin,_member_
  _build_user_headers
 
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:996
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.141 31870 DEBUG
  routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Matched GET
 
 /dd32714d9009495bb51276e284380d6a/servers/309a1f47-83b6-4ab4-9d71-642a2000c8a1
  __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.142 31870 DEBUG
  routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Route path:
  '/{project_id}/servers/:(id)', defaults: {'action': u'show',
 'controller':
  nova.api.openstack.wsgi.Resource object at 0x43e2550} __call__
  /usr/lib/python2.6/site-packages/routes/middleware.py:102
  183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.142 31870 DEBUG
  routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Match dict:
  {'action': u'show', 'controller': nova.api.openstack.wsgi.Resource
 object
  at 0x43e2550, 'project_id': 

Re: [openstack-dev] [Fuel][Neutron ML2][VMWare]NetworkNotFoundForBridge: Network could not be found for bridge br-int

2015-01-16 Thread Andrew Woodward
neophy,

It seems like there are left overs that fuel was using in the config
that would not be present when you installed neutron fresh. I'd
compare the config files and start backing out bits you dont need. I'd
start with the lines refrencing br-int, you dont need them on nodes
that aren't using the ovs agent.

Poke me on IRC if you need more help

Xarses (GMT-8)

On Fri, Jan 9, 2015 at 1:08 PM, Foss Geek thefossg...@gmail.com wrote:
 Dear All,

 I am trying to integrate Openstack + vCenter + Neutron + VMware dvSwitch ML2
 Mechanism driver.

 I deployed a two node openstack environment (controller + compute with KVM)
 with Neutron VLAN + KVM using fuel 5.1. Again I installed nova-compute using
 yum in controller node and configured nova-compute in controller to point
 vCenter. I am also using Neutron VLAN with VMware dvSwitch ML2 Mechanism
 driver. My vCenter is properly configured as suggested by the doc:
 https://www.mirantis.com/blog/managing-vmware-vcenter-resources-mirantis-openstack-5-0-part-1-create-vsphere-cluster/

 I am able to create network from Horizon and I can see the same network
 created in vCenter. When I try to create a VM I am getting the below error
 in Horizon.

 Error: Failed to launch instance test-01: Please try again later [Error:
 No valid host was found. ].

 Here is the error message from Instance Overview tab:

 Instance Overview
 Info
 Name
 test-01
 ID
 309a1f47-83b6-4ab4-9d71-642a2000c8a1
 Status
 Error
 Availability Zone
 nova
 Created
 Jan. 9, 2015, 8:16 p.m.
 Uptime
 0 minutes
 Fault
 Message
 No valid host was found.
 Code
 500
 Details
 File /usr/lib/python2.6/site-packages/nova/scheduler/filter_scheduler.py,
 line 108, in schedule_run_instance raise exception.NoValidHost(reason=)
 Created
 Jan. 9, 2015, 8:16 p.m

 Getting the below error in nova-all.log:


 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.135 31870 DEBUG
 keystoneclient.middleware.auth_token
 [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Authenticating user token
 __call__
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:676
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.136 31870 DEBUG
 keystoneclient.middleware.auth_token
 [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Removing headers from request
 environment:
 X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
 _remove_auth_headers
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:733
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.137 31870 DEBUG
 keystoneclient.middleware.auth_token
 [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Returning cached token
 _cache_get
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:1545
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.138 31870 DEBUG
 keystoneclient.middleware.auth_token
 [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Storing token in cache store
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:1460
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.139 31870 DEBUG
 keystoneclient.middleware.auth_token
 [req-c9ec0973-ff63-4ac3-a0f7-1d2d7b7aa470 ] Received request from user:
 4564fea80fa14e1daed160afa074d389 with project_id :
 dd32714d9009495bb51276e284380d6a and roles: admin,_member_
 _build_user_headers
 /usr/lib/python2.6/site-packages/keystoneclient/middleware/auth_token.py:996
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.141 31870 DEBUG
 routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Matched GET
 /dd32714d9009495bb51276e284380d6a/servers/309a1f47-83b6-4ab4-9d71-642a2000c8a1
 __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.142 31870 DEBUG
 routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Route path:
 '/{project_id}/servers/:(id)', defaults: {'action': u'show', 'controller':
 nova.api.openstack.wsgi.Resource object at 0x43e2550} __call__
 /usr/lib/python2.6/site-packages/routes/middleware.py:102
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.142 31870 DEBUG
 routes.middleware [req-05089e83-e4c1-4d90-b7c5-065226e55d91 ] Match dict:
 {'action': u'show', 'controller': nova.api.openstack.wsgi.Resource object
 at 0x43e2550, 'project_id': u'dd32714d9009495bb51276e284380d6a', 'id':
 u'309a1f47-83b6-4ab4-9d71-642a2000c8a1'} __call__
 /usr/lib/python2.6/site-packages/routes/middleware.py:103
 183Jan  9 20:16:23 node-18 nova-api 2015-01-09 20:16:23.143 31870 DEBUG
 nova.api.openstack.wsgi [req-05089e83-e4c1-4d90-b7c5-065226e55d91 None]
 Calling method 'bound method Controller.show of
 nova.api.openstack.compute.servers.Controller object at 0x4204290'
 (Content-type='None', Accept='application/json') _process_stack