Yes, this matches that bug. Zane's comment on 2014-04-03 in that description is exactly the issue you are hitting.
Here is his comment: "After discussion on IRC of another bug, it appears that depending on the Router (and by extension the gateway) is insufficient, and we need to depend instead on the RouterInterface that connects the Router to the internal Subnet. This suggests that it's probably a mistake to have the RouterInterfaces take a Router argument, rather than the other way around; if Router took a list of Ports instead then depending on the Router would be sufficient." On Wed, Aug 13, 2014 at 9:08 PM, McLellan, Steven <[email protected]> wrote: > Thanks Kevin. Steve Baker pointed me at > https://bugs.launchpad.net/heat/+bug/1299259 which looks related. > > > > The only related field I see around floating ips is ‘router_id’ on > FloatingIP, but it feels like that wouldn’t correct any dependencies on the > RouterInterface. I understand the error I’m getting, but I’m not sure if > I’m doing something wrong or if it’s a bug. > > > > *From:* Kevin Benton [mailto:[email protected]] > *Sent:* Wednesday, August 13, 2014 10:44 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Heat] Occasional stack-delete failure > with RouterInterface > > > > It looks like there may be a missing dependency. The floating IP > association needs to depend on the router interface that attaches the > router to the subnet where the floating IP maps to. You can't remove a > router interface to a subnet if there is a port on that subnet with a > floating IP associated to it because it would prevent the floating IP from > functioning. > > > > On Wed, Aug 13, 2014 at 8:30 PM, McLellan, Steven <[email protected]> > wrote: > > Hello, > > > > We’re occasionally (as in occasionally repeatable but not consistent) > seeing failures deleting stacks containing a neutron RouterInterface. I’m > not sure if it’s a bug or the template is to blame. The error we get is: > > > > Conflict: Router interface for subnet <id> on router <id> cannot be > deleted, as it is required by one or more floating IPs. > > > > The router id is provided to the heat template as an id; the subnet is a > resource within the template. An abridged example (minus server) is below > (router interface towards the end). The logs (at INFO) for a SUCCESSFUL > delete show the router interface being deleted first (straight after the > server resource). I don’t have a lot of neutron expertise, but it seems > like there’s an implicit dependency that’s not being expressed properly – > or perhaps the template is flawed? The failure doesn’t happen all the time, > which makes me wonder if there’s a race going on. > > > > Any ideas? > > > > Thanks, > > Steve > > > > 2014-08-14 02:55:50.374 INFO heat.engine.resource [-] deleting > RouterInterface "router-interface" > [685971ab-4c80-41a7-b64b-715a78b61267:subnet_id=4de89638-0e8b-4353-a847-0a3fceefe1f9] > Stack "t1" > [ba13d445-d43d-45c1-bc76-e2c5898ae5ad] > > > 2014-08-14 02:55:50.491 INFO heat.engine.resource [-] deleting > FloatingIPAssociation "floating-ip-assoc" > [92f10394-b524-4f8b-9383-e1f111d70d68:23540c60-9b05-47ad-b93b-b3b24f86ab37] > Stack "t1" [ba13d445-d43d-45c1-bc76-e2c5898ae5ad] > > 2014-08-14 02:55:51.124 INFO heat.engine.resource [-] deleting Port > "port-on-subnet" [23540c60-9b05-47ad-b93b-b3b24f86ab37] Stack "t1" > [ba13d445-d43d-45c1-bc76-e2c5898ae5ad] > > > 2014-08-14 02:55:51.163 INFO heat.engine.resource [-] deleting FloatingIP > "floating-ip" [92f10394-b524-4f8b-9383-e1f111d70d68] Stack "t1" > [ba13d445-d43d-45c1-bc76-e2c5898ae5ad] > > > 2014-08-14 02:55:52.278 INFO heat.engine.resource [-] deleting Subnet > "subnet" [4de89638-0e8b-4353-a847-0a3fceefe1f9] Stack "t1" > [ba13d445-d43d-45c1-bc76-e2c5898ae5ad] > > > 2014-08-14 02:55:52.428 INFO heat.engine.resource [-] deleting > SecurityGroup "secgroup" [e7ec7fbb-6134-41dc-a98e-c0d4104b270f] Stack "t1" > [ba13d445-d43d-45c1-bc76-e2c5898ae5ad] > > > > > > floating-ip: > > properties: {floating_network_id: a60900f8-bdc9-40ef-b0ab-a41d20e0c660} > > type: OS::Neutron::FloatingIP > > floating-ip-assoc: > > properties: > > floatingip_id: {get_resource: floating-ip} > > port_id: {get_resource: port-on-subnet} > > type: OS::Neutron::FloatingIPAssociation > > port-on-subnet: > > properties: > > fixed_ips: > > - subnet_id: {get_resource: subnet} > > network_id: {get_resource: net} > > security_groups: > > - default > > type: OS::Neutron::Port > > net: > > properties: {name: mynet} > > type: OS::Neutron::Net > > router-interface: > > properties: > > router_id: 108eea7b-b846-40df-9f0d-c53c926b7608 > > subnet_id: {get_resource: subnet} > > type: OS::Neutron::RouterInterface > > subnet: > > properties: > > cidr: 10.0.29.0/24 > > dns_nameservers: [8.8.8.8] > > ip_version: 4 > > network_id: {get_resource: net} > > type: OS::Neutron::Subnet > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > -- > > Kevin Benton > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
