The test_server_metadata test does not consider out of band metadata

[Castulo J. Martinez]

The "test_server_metadata" test does not consider metadata that could be added by an out of band compute process some cloud implementations could have which can cause these tests to fail because there may be additional unexpected values.

So lets say you are in a cloud that runs an out of band process that adds the following metadata to every server that is created {'some_cluod_process': 'proc_status'} and since the test is only looking for {'key1': 'value1', 'key2': 'value2'} then the test is always going to fail because of the extra unexpected value, the metadata actions being validated worked fine, so the test should have passed.

The tests should only look for the metadata they know is present in the server, ignoring that metadata that could have been added by an external agent.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Castulo J. Martinez (<email address hidden>) on branch: master
Review: https://review.openstack.org/328484
Reason: Looks like this is something the community feels is not part of the API contract.