| commit | eef6ef54490c2fe997b872d3324bfb03f23e178a | [log] [tgz] |
|---|---|---|
| author | aguilard <e.dah.tid@telefonica.com> | Thu Nov 02 16:52:56 2023 +0000 |
| committer | aguilard <e.dah.tid@telefonica.com> | Mon Nov 13 12:19:32 2023 +0200 |
| tree | 7dc13e7306b2aa67a9d763e0b51fc97f31a2609c | |
| parent | f6fbe42594c64f6cacfaf1798568e3ff40712240 [diff] |
Fix bug 2302: IP ranges management in Azure not working properly OSM uses a specific vnet to create NS or VNF subnets when instantiating on Azure. The vnets allow more than one address prefix, but RO only try to allocate new subnets in the range defined in first place, ignoring the rest. Change-Id: I9792caf2a468e60b6762567a9b4a90d0f1646b39 Signed-off-by: aguilard <e.dah.tid@telefonica.com> (cherry picked from commit 5d27a33f4c8f6a9bc5f6ca20f844a124a5d8b223)