Unit test can not make sense in tests for availability_zones.reset_cache

[Chen Xiao]

In test_availability_zones.py and and test_compute.py, There are two tests for availability_zones.reset_cache which can not make sense.

Follow code:
        az.reset_cache()
        self.assertIsNone(az._get_cache().get('cache'))

if we do not add cache for key 'cache', the result of az._get_cache().get('cache') before az.reset_cache() is same as after az.reset_cache(). So it can not make sense.
In test_compute.py, the wrong is in https://github.com/openstack/nova/blob/master/nova/tests/compute/test_compute.py#L8463

the change for test_compute.py is in my another review https://review.openstack.org/#/c/59922/,

[OpenStack Infra (hudson-openstack)]

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

[Guangya Liu (Jay Lau) (jay-lau-513)]

What is wrong with test_compute.py?

[Chen Xiao (chenxiao)]

the change for test_compute.py is in my another review https://review.openstack.org/#/c/59922/, I will change the bug context

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/60165
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0aff41a0214c8f751f01712a3423405b21bd7ce7
Submitter: Jenkins
Branch: master

commit 0aff41a0214c8f751f01712a3423405b21bd7ce7
Author: chenxiao <email address hidden>
Date: Thu Dec 5 15:31:40 2013 +0800

    Change unit test for availability_zones.reset_cache

    Test_rest_availability_zone_reset_cache can not make sense
    because the result of az._get_cache().get('cache') before
    executing az.reset_cache() and after az.reset_cache() are
    same.

    This Patch will provide a reasonable test for it.

    Change-Id: I7a27998bdf70f39077a5d79fc460974fc5806c3e
    Closes-bug: #1258041