[2.1. Yakkety] "Map subnet" action doesn't work
Bug #1632862 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Unassigned |
Bug Description
When you try to map a subnet, nothing happens
1. Go to subnet details page
2. Take action
3. Map Subnet
4. Go
5. Nothing.
Related branches
lp:~mpontillo/maas/map-subnet-broken-on-yakkety--bug-1632862
- Gavin Panella (community): Approve
-
Diff: 56 lines (+10/-6)2 files modifiedsrc/maasserver/static/js/angular/factories/subnets.js (+6/-2)
src/maasserver/static/js/angular/factories/tests/test_subnets.js (+4/-4)
Changed in maas: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → 2.1.0 |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
A couple thoughts on this:
- We don't currently have an RPC call to get scan status from the rack, so we don't have a way to know a scan is in progress. So we haven't implemented the "Scanning" spinner that was in the design yet.
- The scan may appear not to do anything, if the subnet is large and only 'ping' is installed. (Perhaps we should require nmap to be installed if you want to scan a subnet over a certain size; I'm scanning a /16 right now and it's taking a very long time.)