[tempest] setUpClass of tempest.api.network.test_allowed_address_pair due to Identity error with 500 code

Bug #1524847 reported by Victor Ryzhenkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
Max Yatsenko

Bug Description

fuel-8.0-277-2015-12-09_16-24-26

Traceback:

Traceback (most recent call last):
  File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 272, in setUpClass
    six.reraise(etype, value, trace)
  File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 260, in setUpClass
    cls.setup_credentials()
  File "/home/developer/mos-tempest-runner/tempest/tempest/api/network/base.py", line 70, in setup_credentials
    super(BaseNetworkTest, cls).setup_credentials()
  File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 351, in setup_credentials
    credential_type=credentials_type)
  File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 474, in get_client_manager
    cred_provider = cls._get_credentials_provider()
  File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 452, in _get_credentials_provider
    identity_version=identity_version)
  File "/home/developer/mos-tempest-runner/tempest/tempest/common/credentials.py", line 39, in get_isolated_credentials
    identity_version=identity_version)
  File "/home/developer/mos-tempest-runner/tempest/tempest/common/isolated_creds.py", line 164, in __init__
    identity_version=self.identity_version)
  File "/home/developer/mos-tempest-runner/tempest/tempest/common/cred_provider.py", line 67, in get_configured_credentials
    identity_version=identity_version, **params)
  File "/home/developer/mos-tempest-runner/tempest/tempest/common/cred_provider.py", line 96, in get_credentials
    **params)
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/auth.py", line 511, in get_credentials
    creds = auth_provider.fill_credentials()
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/auth.py", line 82, in fill_credentials
    auth_data = self.get_auth()
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/auth.py", line 102, in get_auth
    self.set_auth()
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/auth.py", line 111, in set_auth
    self.cache = self._get_auth()
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/auth.py", line 243, in _get_auth
    token, auth_data = auth_func(**auth_params)
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/services/identity/v2/token_client.py", line 101, in get_token
    body = self.auth(user, password, tenant)
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/services/identity/v2/token_client.py", line 51, in auth
    resp, body = self.post(self.auth_url, body=body)
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 259, in post
    return self.request('POST', url, extra_headers, headers, body)
  File "/home/developer/mos-tempest-runner/.venv/lib/python2.7/site-packages/tempest_lib/services/identity/v2/token_client.py", line 95, in request
    'Unexpected status code {0}'.format(resp.status))
tempest_lib.exceptions.IdentityError: Got identity error
Details: Unexpected status code 500

Build link: https://jenkins.mosi.mirantis.net/view/Periodic%20(deployment)/job/periodic-testing-deploy-openstack-8.0-ubuntu-vlan-ceph-swift/71/

Changed in mos:
assignee: nobody → MOS Keystone (mos-keystone)
Boris Bobrov (bbobrov)
Changed in mos:
assignee: MOS Keystone (mos-keystone) → Boris Bobrov (bbobrov)
Revision history for this message
Boris Bobrov (bbobrov) wrote :

I don't see this error in logs anywhere and cannot even guess where it could happen.

There is a suspicious thing I see: [cache]memcache_servers is not set, while it should be set to a list of memcache_servers. Max, could you please have a look at puppet logs and verify that setup finished normally? (If it's not you who will check it, please assign to the one who should)

Changed in mos:
assignee: Boris Bobrov (bbobrov) → Max Yatsenko (myatsenko)
Max Yatsenko (myatsenko)
Changed in mos:
status: Confirmed → In Progress
Revision history for this message
Max Yatsenko (myatsenko) wrote :

This issue was not reproduced on ISO #303 .

After run this command, tests were successfully passed:

$ run_tests tempest.api.network.test_allowed_address_pair
tempest.api.network.test_allowed_address_pair.AllowedAddressPairIpV6TestJSON
    test_create_list_port_with_address_pair[id-86c3529b-1231-40de-803c-00e40882f043]OK 11.15
tempest.api.network.test_allowed_address_pair.AllowedAddressPairTestJSON
    test_create_list_port_with_address_pair[id-86c3529b-1231-40de-803c-00e40882f043]OK 28.30
tempest.api.network.test_allowed_address_pair.AllowedAddressPairIpV6TestJSON
    test_update_port_with_address_pair[id-9599b337-272c-47fd-b3cf-509414414ac4]OK 39.10
tempest.api.network.test_allowed_address_pair.AllowedAddressPairTestJSON
    test_update_port_with_address_pair[id-9599b337-272c-47fd-b3cf-509414414ac4]OK 31.74
    test_update_port_with_cidr_address_pair[id-4d6d178f-34f6-4bff-a01c-0a2f8fe909e4]OK 18.65
tempest.api.network.test_allowed_address_pair.AllowedAddressPairIpV6TestJSON
    test_update_port_with_cidr_address_pair[id-4d6d178f-34f6-4bff-a01c-0a2f8fe909e4]OK 13.11
    test_update_port_with_multiple_ip_mac_address_pair[id-b3f20091-6cd5-472b-8487-3516137df933]OK 35.86
tempest.api.network.test_allowed_address_pair.AllowedAddressPairTestJSON
    test_update_port_with_multiple_ip_mac_address_pair[id-b3f20091-6cd5-472b-8487-3516137df933]OK 38.27

(Logs of 307 ISO : https://jenkins.mosi.mirantis.net/job/periodic-testing-deploy-openstack-8.0-ubuntu-vlan-ceph-swift/79/consoleFull)

According to it this bug can be set to invalid for ISO 303+ .

Changed in mos:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.