Open Stack

Thanks Shake,
but I'm afraid unfortunately the problem is at a lower level. The VM doesn't receive the network; its NIC doesn't even seem to be connected to the network.

thanks,

	A.

On Jan 9, 2014, at 3:32 AM, Shake Chen wrote:

> https://bugzilla.redhat.com/show_bug.cgi?id=983611
> 
> 
> Hope the link can help you. 
> 
> 
> On Thu, Jan 9, 2014 at 1:41 AM, Alvise Dorigo <alvise.dorigo at pd.infn.it> wrote:
> Hi,
> I installed (with Packstack) the Havana release on 3 (virtual) machines each of them having 2 NIC configured with static IPs:
> 
> controller: 	keystone, glance, nova-api, nova-cert, 
> 		nova-vncproxy, nova-conductor, nova-scheduler
> 		neutron-server
> 
> 
> compute:	nova-compute
> 
> network:	L3-agent, dhcp-agent,
> 		lbaas
> 		metadata
> 
> When I try to instantiate a VM, eventually it cannot reach the network:
> 
> $ nova list
> +--------------------------------------+--------+---------+------------+-------------+-------------------------+
> | ID                                   | Name   | Status  | Task State | Power State | Networks                |
> +--------------------------------------+--------+---------+------------+-------------+-------------------------+
> | ee771359-497f-4996-aa2d-c0d5305ab3e4 | prova2 | ACTIVE  | None       | Running     | ext-net=192.168.120.101 |
> +--------------------------------------+--------+---------+------------+-------------+————————————+
> 
> $ nova console-log prova2
> […]
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
> cloud-setup: failed 30/30: up 43.47. request failed
> cloud-setup: after 30 fails, debugging
> cloud-setup: running debug (30 tries reached)
> ############ debug start ##############
> ### /etc/rc.d/init.d/sshd start
> /etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found
> route: fscanf
> ### ifconfig -a
> eth0      Link encap:Ethernet  HWaddr FA:16:3E:22:1F:55  
>           inet6 addr: fe80::f816:3eff:fe22:1f55/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:748 (748.0 B)  TX bytes:1364 (1.3 KiB)
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> […]
> ############ debug end   ##############
> cloud-setup: failed to read iid from metadata. tried 30
> WARN: /etc/rc3.d/S45-cloud-setup failed
> Starting dropbear sshd: generating rsa key... generating dsa key... OK
> ===== cloud-final: system completely up in 45.94 seconds ====
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
>   instance-id: 
>   public-ipv4: 
>   local-ipv4 : 
> wget: can't connect to remote host (169.254.169.254): Network is unreachable
> cloud-userdata: failed to read instance id
> WARN: /etc/rc3.d/S99-cloud-userdata failed
>   ____               ____  ____
>  / __/ __ ____ ____ / __ \/ __/
> / /__ / // __// __// /_/ /\ \ 
> \___//_//_/  /_/   \____/___/ 
>  http://launchpad.net/cirros
> 
> 
> login as 'cirros' user. default password: 'cubswin:)'. use 'sudo' for root.
> cirros login: 
> 
> 
> 
> $ neutron net-list
> +--------------------------------------+----------+-------------------------------------------------------+
> | id                                   | name     | subnets                                               |
> +--------------------------------------+----------+-------------------------------------------------------+
> | 9436c5d0-b556-4653-962c-9dc90e9efc50 | demo-net | 6b632a13-6f94-4fbc-aa57-8fbc67f8aab9 10.5.5.0/24      |
> | defd117f-101b-4644-b3de-53745158d93b | ext-net  | 677a1fb6-948d-4795-b20e-978b72987cc5 192.168.120.0/24 |
> +--------------------------------------+----------+-------------------------------------------------------+
> 
>  neutron net-show ext-net
> +---------------------------+--------------------------------------+
> | Field                     | Value                                |
> +---------------------------+--------------------------------------+
> | admin_state_up            | True                                 |
> | id                        | defd117f-101b-4644-b3de-53745158d93b |
> | name                      | ext-net                              |
> | provider:network_type     | vlan                                 |
> | provider:physical_network | physnet1                             |
> | provider:segmentation_id  | 2                                    |
> | router:external           | True                                 |
> | shared                    | True                                 |
> | status                    | ACTIVE                               |
> | subnets                   | 677a1fb6-948d-4795-b20e-978b72987cc5 |
> | tenant_id                 | 5a3847093ac24db4958eac2f3c39a604     |
> +---------------------------+--------------------------------------+
> 
> 
> The only log file where I see a strange (?) message is the server.log (of neutron-server) in the controller node; it says:
> 
> 2014-01-05 22:16:12.005 1565 WARNING neutron.db.agentschedulers_db [-] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'677a1fb6-948d-4795-b20e-978b72987cc5'], 'name': u'ext-net', 'provider:physical_network': u'physnet1', 'admin_state_up': True, 'tenant_id': u'5a3847093ac24db4958eac2f3c39a604', 'provider:network_type': u'vlan', 'router:external': True, 'shared': True, 'id': u'defd117f-101b-4644-b3de-53745158d93b', 'provider:segmentation_id': 2L}
> 
> Here http://pastebin.com/kFpEs0D7, the Packstack’s answer file I used.
> 
> Could you please advice me where what I can investigate in order to understand why my VMs do not get the network after instantiated ?
> 
> many thanks,
> 
> 	Alvise
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> 
> 
> 
> 
> -- 
> Shake Chen
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140109/9b85f0b3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1756 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140109/9b85f0b3/attachment.bin>