openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #14893
Re: VM can't ping self floating IP after a snapshot is taken
-
To:
Sam Su <susltd.su@xxxxxxxxx>
-
From:
Brian Haley <brian.haley@xxxxxx>
-
Date:
Thu, 19 Jul 2012 11:37:49 -0400
-
Cc:
openstack <openstack@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAHOnjE4y3=7jM1WGzs52X2bj6mUeFmOtkS1xWjRfOmXkCSVCfg@mail.gmail.com>
-
Organization:
HP Cloud Services
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
On 07/17/2012 05:56 PM, Sam Su wrote:
> Hi,
>
> Just This always happens in Essex release. After I take a snapshot of my VM ( I
> tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I
> take a snapshot though, VM can ping its self floating IP.
>
> This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but
> still a little different. In 933640, it sounds like VM can't ping its self
> floating IP regardless whether we take a snapshot or not.
>
> Any suggestion to make an easy fix? And what is the root cause of the problem?
It might be because there's a missing _enable_hairpin() call in the reboot()
function. Try something like this...
nova/virt/libvirt/connection.py, _hard_reboot():
self._create_new_domain(xml)
+ self._enable_hairpin(instance)
self.firewall_driver.apply_instance_filter(instance, network_info)
At least that's what I remember doing myself recently when testing after a
reboot, don't know about snapshot.
Folsom has changed enough that something different would need to be done there.
-Brian
Follow ups
References