[2.1. Yakkety] "Map subnet" action doesn't work

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.)

I see the issue now. When you click "Go", the drop-down dialog doesn't dismiss. Strange issue; it doesn't happen in my local test bed. I'll try with Yakkety to see if anything is different there.

I confirm that this doesn't happen when MAAS is running Xenial, but it is happening when running Yakkety.

I reproduced it in a local Yakkety test bed. This seems to have something to do with the newer version of Angular in Yakkety. Looking at the JS console, I see this:

angular.js?v=2.1.0(beta3+bzr5477):6
TypeError: Converting circular structure to JSON
    at Object.toJson (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):2:11966)
    at RegionConnection.callMethod (http://localhost:10001/MAAS/combo/maas-angular.js?v=2.1.0(beta3+bzr5477):783:41)
    at Manager.SubnetsManager.scanSubnet (http://localhost:10001/MAAS/combo/maas-angular.js?v=2.1.0(beta3+bzr5477):2368:37)
    at Scope.$scope.actionGo (http://localhost:10001/MAAS/combo/maas-angular.js?v=2.1.0(beta3+bzr5477):16109:32)
    at fn (eval at compile (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):7:5437), <anonymous>:4:215)
    at expensiveCheckFn (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):7:29272)
    at callback (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):10:3936)
    at Scope.$eval (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):8:15047)
    at Scope.$apply (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):8:15395)
    at HTMLButtonElement.<anonymous> (http://localhost:10001/MAAS/combo/angular.js?v=2.1.0(beta3+bzr5477):10:4052)(anonymous function) @ angular.js?v=2.1.0(beta3+bzr5477):6

So we need to find out why we're passing the region a circular structure in Yakkety but not in Xenial.

Hello Andres, or anyone else affected,

Accepted maas into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/2.1.0+bzr5480-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I've tested this and can confirm it has been fixed. Marking verification-done

The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.