[NETVIRT-799] NeutronPortChangeListener: handleNeutronPortUpdated doesn't catch, that Subnet ID for neutron port was changed (port was updated) Created: 21/Jul/17 Updated: 30/Oct/17 Resolved: 24/Aug/17 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Carbon |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Valentina Krasnobaeva | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8875 |
| Priority: | Normal |
| Description |
|
Issue was introduced by this gerrit change: https://git.opendaylight.org/gerrit/#/c/45969 at NeutronPortChangeListener.java, handleNeutronPortUpdated method: 445 + final DataStoreJobCoordinator portDataStoreCoordinator = DataStoreJobCoordinator.getInstance(); catch (Exception e) { 477 + LOG.error("Port removed from subnet notification failed", e); 478 + }479 + } catch (Exception e) { 498 + LOG.error("Port added to subnet notification failed", e); 499 + }500 + } At lines 454, 455 we set values for subnetIdOr and subnetIdUp, but these variables will always have the same value, because we get SubnetId for both two variables from updated neutron port (portupdate) => comparation at line 457 will always give False => condition in line 459 will be never executed. So this makes handleNeutronPortUpdated unable to catch, that Subnet ID for neutron port was changed (port was updated), hence, to threat a case, when we add a second subnet to a neutron network. See appropriate log with added debug traces in attachement |
| Comments |
| Comment by Valentina Krasnobaeva [ 21/Jul/17 ] |
|
(In reply to Valentina Krasnobaeva from comment #0) catch (Exception e) { > 477 + LOG.error("Port removed from subnet > notification failed", e); > 478 + }> 479 + } catch (Exception e) { > 498 + LOG.error("Port added to subnet > notification failed", e); > 499 + }> 500 + } |
| Comment by Hari Prasidh [ 18/Aug/17 ] |
|
(In reply to Valentina Krasnobaeva from comment #0) catch (Exception e) { > 477 + LOG.error("Port removed from subnet > notification failed", e); > 478 + }> 479 + } catch (Exception e) { > 498 + LOG.error("Port added to subnet > notification failed", e); > 499 + }> 500 + } Hi Valentina, Can you please provide me the clear procedure in which scenario you have observed this issue and please update the logs. |
| Comment by Hari Prasidh [ 22/Aug/17 ] |
|
Am trying to see the issue for that I've tested below scenarios. Test1 : Test2 : Test3: Valentina, |
| Comment by Hari Prasidh [ 23/Aug/17 ] |
|
With latest git pull for networking-odl, below mentioned code got triggered. |
| Comment by Hari Prasidh [ 24/Aug/17 ] |
|
Bug has been fixed. Patch pushed to Carbon & Master. Please find below, Carbon : https://git.opendaylight.org/gerrit/#/c/60636/ |