On 5/22/2017 11:01 AM, Zane Bitter wrote:
If the user does a stack update that changes the network from 'auto' to 'none', or vice-versa.
OK I guess we should make this a side discussion at some point, or hit me up in IRC, but if you're requesting networks='none' with microversion >= 2.37 then nova should not allocate any networking, it should not event attempt to do so.
Maybe the issue is the server is created with networks='auto' and has a port, and then when you 'update the stack' it doesn't delete that server and create a new one, but it tries to do something with the same server, and in this case you'd have to detach the port(s) that were previously created?
I don't know how Heat works, but if that's the case, then yeah that doesn't sound fun, but I think Nova provides the APIs to be able to do this.
-- Thanks, Matt __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
