Websocket API: vlan.update not triggered on subnet_ids change

Bug #2037614 reported by Peter Makowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned
3.3
Won't Fix
Medium
Unassigned
3.4
Won't Fix
Medium
Unassigned
3.5
Won't Fix
Medium
Unassigned

Bug Description

## Description
WebSocket doesn't send an update notification (vlan.update) when a new subnet is added and subsequently vlan.subnet_ids is updated.

## Steps to reproduce:
1. Go to a Subnets page
2. Open developer tools and inspect websocket connection (you may need to now refresh the page)
2. Add a new subnet

## Result:

### Actual:
no vlan.update message is sent from the server

### Expected:
vlan.update with and updated vlan.subnet_ids is sent from the server

Bill Wear (billwear)
Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 3.5.0
Changed in maas:
importance: High → Medium
milestone: 3.5.0 → 3.5.x
milestone: 3.5.x → 3.6.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.