Just for the record... A brand new instance, from the same Tenant, that ended up running within the very same "problematic" Compute Node, gets its IP normally, look:
--- cloud-init start-local running: Mon, 18 Nov 2013 18:15:59 +0000. up 3.50 seconds no instance data found in start-local ci-info: lo : 1 127.0.0.1 255.0.0.0 . ci-info: eth0 : 1 192.168.210.12 255.255.255.0 fa:16:3e:c8:fe:dd ci-info: route-0: 0.0.0.0 192.168.210.1 0.0.0.0 eth0 UG ci-info: route-1: 192.168.210.0 0.0.0.0 255.255.255.0 eth0 U cloud-init start running: Mon, 18 Nov 2013 18:16:00 +0000. up 4.88 seconds found data source: DataSourceEc2 --- I don't understand why the previous running Instances are offline just because of a Compute Node reboot... :-/ Tks! Thiago On 18 November 2013 16:10, Martinx - ジェームズ <thiagocmarti...@gmail.com>wrote: > Okay... I'm calm... :-P > > This is the second time I'm seeing this with Havana. > > Compute Node reboots, lots of Instances doesn't get its IP anymore, look: > > --- > cloud-init start-local running: Mon, 18 Nov 2013 16:34:06 +0000. up 18.19 > seconds > no instance data found in start-local > cloud-init-nonet waiting 120 seconds for a network device. > cloud-init-nonet gave up waiting for a network device. > ci-info: lo : 1 127.0.0.1 255.0.0.0 . > ci-info: eth0 : 1 . . fa:16:3e:a2:71:74 > route_info failed > Waiting for network configuration... > Waiting up to 60 more seconds for network configuration... > Booting system without full network configuration... > --- > > New Instances that I launch right now, get its IP normally. > > The only way to put the website online again now is: take a snapshot of a > Instance without IP, launch a new instance based on that image, voialá! > Instance gets its IP again... But this is non-viable. > > I appreciate any help! > > Tks! > Thiago > > > On 18 November 2013 15:35, Razique Mahroua <razique.mahr...@gmail.com>wrote: > >> Hey Martin :) >> On 18 Nov 2013, at 8:40, Martinx - ジェームズ wrote: >> >> > Guys, >> > >> > My Havana (Ubuntu based) Compute Node was restarted and lots of >> Instances >> > does not get an IP anymore. >> > >> > Tips?! >> Stay clam >> >> > >> > It is ramdom, I mean, some instances of this same compute node are >> normal, >> > while others have no IP. >> Are you reffering to the private IPs pool or the public. When you say >> "don't have", you mean they don't get allocated or the instances (DHCP? ) >> don't retrieve it? >> >> > >> > I really need help here because my client's web site is completely off >> line >> > now... >> > >> > I'm using Per-Tenant router with private networks + VXLAN. >> > >> > Tks! >> > Thiago >> > _______________________________________________ >> > Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> > Post to : openstack@lists.openstack.org >> > Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
