From e9529f7dc5449714c76afd7fce62f228f8111177 Mon Sep 17 00:00:00 2001
From: "Dr. Jens Harbott" <harbott@osism.tech>
Date: Fri, 3 Mar 2023 14:33:16 +0100
Subject: [PATCH] Add a reno for the fixed address scope calculation

[0] Ic6d48a86043aaf4b458bb2230883a355fc841ee9

Change-Id: Ia3593a6d2183c7621a5a39bf1a3023fc28e0f5ed
---
 .../fix-address-scope-calculation-c8ac84662a6547bd.yaml   | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 releasenotes/notes/fix-address-scope-calculation-c8ac84662a6547bd.yaml

diff --git a/releasenotes/notes/fix-address-scope-calculation-c8ac84662a6547bd.yaml b/releasenotes/notes/fix-address-scope-calculation-c8ac84662a6547bd.yaml
new file mode 100644
index 00000000..560c8a3f
--- /dev/null
+++ b/releasenotes/notes/fix-address-scope-calculation-c8ac84662a6547bd.yaml
@@ -0,0 +1,8 @@
+---
+fixes:
+  - |
+    Fixes the iteration to obtain the address_scope linked to a subnet.
+    A network can be linked to more than one subnet (ipv4 and ipv6),
+    but if one of them does not have an address_scope, a null object
+    element access failure occured.
+    See bug `1998104 <https://bugs.launchpad.net/neutron/+bug/1998104>`_.