Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 911149

Summary: First VM on each compute node will set to ERROR state since bridge is no there yet
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: openstack-novaAssignee: Gary Kotton <gkotton>
Status: CLOSED WORKSFORME QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0 (Folsom)CC: ndipanov
Target Milestone: snapshot4Keywords: Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-26 11:43:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Instance create after nova-manage network create none

Description Ofer Blaut 2013-02-14 13:43:53 UTC
Created attachment 697221 [details]
Instance create after nova-manage network create

Description of problem:


After creating new network using nova-manage , the first Instance on each compute node will set into Error state

See reproduction and logs attached 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install clean RHOS setup
2. create new network  
3. luanch VM
  
Actual results:

first VM per compute node fails 

Expected results:


Additional info:

Comment 2 Ofer Blaut 2013-02-14 14:30:07 UTC
Added external bug :
https://bugs.launchpad.net/nova/+bug/1036672

i also 
1. deleted the VMs
2 removed the network from DB
3. rebooted the hosts
4. tried again

Comment 3 Ofer Blaut 2013-02-19 18:48:15 UTC
it also reproduce when using installation with packstack on clean bare metal.

then 
1. removing the default nova-manage network created by packstack ( NO VM is launched )
2. switch to vlan.manager
3. restart all nova service 
4. creating launch new VM

Comment 4 Ofer Blaut 2013-02-21 08:42:34 UTC
I have recchecked again

This it was very very slow (~10 minutes) but VM successed to move to active 

grep 8260321a-851d-41ad-a991-8f22cdcf3d32 /var/log/nova/*
/var/log/nova/api.log:2013-02-21 09:54:53 INFO nova.api.openstack.wsgi [req-51d5ce49-d3ab-4af0-a5a0-c79cfdd98e46 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] GET http://10.35.160.17:8774/v2/e280b033595145ceadb9a4ec47096949/servers/8260321a-851d-41ad-a991-8f22cdcf3d32
/var/log/nova/api.log:2013-02-21 09:54:53 INFO nova.api.openstack.wsgi [req-51d5ce49-d3ab-4af0-a5a0-c79cfdd98e46 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] http://10.35.160.17:8774/v2/e280b033595145ceadb9a4ec47096949/servers/8260321a-851d-41ad-a991-8f22cdcf3d32 returned with HTTP 200
/var/log/nova/api.log:2013-02-21 09:54:53 INFO nova.osapi_compute.wsgi.server [req-51d5ce49-d3ab-4af0-a5a0-c79cfdd98e46 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] 10.35.160.17 - - [21/Feb/2013 09:54:53] "GET /v2/e280b033595145ceadb9a4ec47096949/servers/8260321a-851d-41ad-a991-8f22cdcf3d32 HTTP/1.1" 200 1489 0.115630
/var/log/nova/compute.log:2013-02-21 09:54:53 AUDIT nova.compute.manager [req-6ed29ac3-6e63-4385-8bb0-57adce2e6d89 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] [instance: 8260321a-851d-41ad-a991-8f22cdcf3d32] Starting instance...
/var/log/nova/compute.log:2013-02-21 09:54:58 INFO nova.virt.libvirt.driver [req-6ed29ac3-6e63-4385-8bb0-57adce2e6d89 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] [instance: 8260321a-851d-41ad-a991-8f22cdcf3d32] Creating image
/var/log/nova/compute.log:2013-02-21 10:05:17 2629 INFO nova.compute.manager [-] [instance: 8260321a-851d-41ad-a991-8f22cdcf3d32] During sync_power_state the instance has a pending task. Skip.
/var/log/nova/compute.log:2013-02-21 10:05:17 2629 AUDIT nova.compute.resource_tracker [-] Expiring resource claim 8260321a-851d-41ad-a991-8f22cdcf3d32
/var/log/nova/compute.log:2013-02-21 10:06:20 INFO nova.virt.libvirt.firewall [req-6ed29ac3-6e63-4385-8bb0-57adce2e6d89 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] [instance: 8260321a-851d-41ad-a991-8f22cdcf3d32] Called setup_basic_filtering in nwfilter
/var/log/nova/compute.log:2013-02-21 10:06:20 INFO nova.virt.libvirt.firewall [req-6ed29ac3-6e63-4385-8bb0-57adce2e6d89 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] [instance: 8260321a-851d-41ad-a991-8f22cdcf3d32] Ensuring static filters
/var/log/nova/compute.log:2013-02-21 10:06:26 2629 INFO nova.virt.libvirt.driver [-] [instance: 8260321a-851d-41ad-a991-8f22cdcf3d32] Instance spawned successfully.
/var/log/nova/compute.log:2013-02-21 10:06:26 INFO nova.compute.resource_tracker [req-6ed29ac3-6e63-4385-8bb0-57adce2e6d89 68310db924a14506b629a81ed2311d27 e280b033595145ceadb9a4ec47096949] Can't find claim 8260321a-851d-41ad-a991-8f22cdcf3d32.  It may have been 'finished' twice, or it has already timed out.

Comment 7 Ofer Blaut 2013-02-26 11:43:32 UTC
I have checked on 2013-02-22.1 puddle , The error issue is not seen any more 
it take 8-9 minutes to first VMs to launch