Bug 1276204

Summary:	OS::Neutron::Subnet should not be deleted/created when allocation_pools is updated
Product:	Red Hat OpenStack	Reporter:	Giulio Fidente <gfidente>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	kbasil, mburns, mcornea, rbiba, rhel-osp-director-maint, sbaker, shardy, yeylon, zbitter
Target Milestone:	z3	Keywords:	TestOnly, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-heat-2015.1.1-8.el7ost	Doc Type:	Bug Fix
Doc Text:	The allocation_pools property of the OS::Neutron::Subnet resource was marked as not allowing updates. Consequently, if the allocation_pools property changed, the Subnet resource was replaced, and this generally failed if there was any overlap. The property is now marked to allow in-place updates. As a result, if the allocation_pools property changes, the existing Subnet will be updated with the new value.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-21 17:01:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1269285, 1272357

Description Giulio Fidente 2015-10-29 05:15:15 UTC

Description of problem:
when trying to update a subnet resource with a new allocation pool, the subnet resource seems to get deleted and recreated with the new properties

this causes troubles when updating for example a tripleo overcloud with updated pools for the isolated networks

Comment 2 Zane Bitter 2015-11-05 19:12:59 UTC

Upstream backport proposed.

Comment 5 Amit Ugol 2015-11-23 16:03:09 UTC

update passed in CI

Comment 7 errata-xmlrpc 2015-12-21 17:01:57 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2015:2680