Changing service network mask breakes new service subnet creation

Bug #1713060 reported by Jan Vondra on 2017-08-25
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Manila
Low
Unassigned

Bug Description

Steps to reproduce:
1. Create share using service network and generic driver
2. Change service_network_division_mask
3. Create share on new subnet and share network

Result:
2017-08-16 15:00:38.856 5742 ERROR oslo_messaging.rpc.server NetworkException: Invalid input for operation: Requested subnet with cidr: 10.254.0.0/26 for network: b78c29b6-a89e-49b8-8eb1-f5335029869a overlaps with another subnet.

Cause:
Change of mask tricks the _get_cidr_for_subnet mechanism in service instance and it tries to create the subnet from the beginnig of the pool.

Ben Swartzlander (bswartz) wrote :

Modifying network-related configuration options after manila has already created some shares using those options is not supported. Manila treats some configuration options are immutable (which is probably a bad design) and the simplest way to fix the problem is to better document which options can't be changed without causing breakage. This looks like one of those cases.

Longer term, we should find a way to not treat information in the config file as immutable and for stuff that truly must be immutable to go into the database, not the config file.

Changed in manila:
status: New → Triaged
importance: Undecided → Low
tags: added: docs
Tom Barron (tpb) on 2018-06-19
tags: added: doc
removed: docs
Jason Grosso (jgrosso) wrote :

Has anyone taken a look at updating the docs, or looked into making the code changes to make these kinds of changed immutable and not in a config file but the DB.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers