Non-existent assertion methods being called on mocks

[Kevin Benton]

There are various places in the unit tests where non-existent "assert" methods are called on mock objects.

e.g. assert_called_once(), assert_called_twice(), assert_called_one_with(), assert_called_twice()

To reproduce, put the mock.py file in the base neutron directory and edit the __getattr__ methods to check if the name begins with 'assert' and raise an exception if true.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/94141

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/94141
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0ff8536c0d9b95172c42b1a01d292df58ed2e573
Submitter: Jenkins
Branch: master

commit 0ff8536c0d9b95172c42b1a01d292df58ed2e573
Author: Kevin Benton <email address hidden>
Date: Mon May 19 06:58:58 2014 +0000

    Fix non-existent 'assert' calls to mocks

    Fixes calls to non-existent 'assert' methods
    called on mock objects.

    Closes-Bug: #1320774
    Change-Id: I7eab28fc9b23cbb39d5507ff3e8004a493c90bed