'Attribute project_id was not found in the schema definition' when executing test case UsersV3TestJSON.test_user_update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Invalid
|
Undecided
|
yuxingw |
Bug Description
it throw 'Attribute project_id was not found in the schema definition' when executing test case UsersV3TestJSON
Test
tests=tempest/
According to API spec of V3, project_id should be removed from post_body.
class IdentityV3Clien
api_version = "v3"
def create_user(self, user_name, password=None, project_id=None,
"""Creates a user."""
en = kwargs.
print en
description = kwargs.
print description
print default_project_id
post_body = {
'name': user_name,
}
API Spec:Add user: JSON request
{
"user":{
"default_
"description"
"domain_
"email":"...",
"enabled":"...",
"name":"...",
"password"
}
}
2015-04-29 06:02:07.705 30068 ERROR keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
2015-04-29 06:02:07.705 30068 TRACE keystone.
Changed in tempest: | |
assignee: | nobody → yuxingw (yuxingw) |
summary: |
- it throw 'Attribute project_id was not found in the schema definition' - when executing test case UsersV3TestJSON.test_user_update + 'Attribute project_id was not found in the schema definition' when + executing test case UsersV3TestJSON.test_user_update |
Changed in tempest: | |
status: | Confirmed → Incomplete |
This does seem to be the case and the current keystoneclient has a deprecation warning if you provide project_id. Since this test passes in the gate I presume the ldap backend is doing stricter checking.