Found the problem...there is a periodic task that disassociates fixed IPs from instances when the network is no longer valid for the host:
https://github.com/openstack/nova/blob/2014.1.rc2/nova/network/manager.py#L357 The timeout_fixed_ips config option defaults to True. By default, 10 minutes after a fixed IP is deallocated it will be disassociated from the instance via the periodic task: cfg.IntOpt('fixed_ip_disassociate_timeout', default=600, help='Seconds after which a deallocated IP is disassociated'), ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1306870 Title: grenade job fails with "NoMoreFixedIps_Remote: Zero fixed ips available" Status in OpenStack Compute (Nova): Invalid Bug description: Lots of failures here: http://logs.openstack.org/47/69047/17/check/check-grenade- dsvm/f153c4a/console.html message:"NoMoreFixedIps_Remote: Zero fixed ips available." AND tags:screen-n-net.txt http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiTm9Nb3JlRml4ZWRJcHNfUmVtb3RlOiBaZXJvIGZpeGVkIGlwcyBhdmFpbGFibGUuXCIgQU5EIHRhZ3M6c2NyZWVuLW4tbmV0LnR4dCIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5NzI3Mzc0Mzc3NH0= This is a 100% failure and only showing up on one patch: https://review.openstack.org/#/c/69047/ But I don't think that has anything to do with the patch to add DB2 support. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1306870/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
