[Yahoo-eng-team] [Bug 1212778] Re: Authenticating v2 token against v3 api fails with error 500
** Changed in: keystone
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1212778
Title:
Authenticating v2 token against v3 api fails with error 500
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
I've been trying to consume a trust as documented in:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/v3/src/markdown/identity-api-v3-os-trust-ext.md
Using my patch to keystoneclient:
https://review.openstack.org/#/c/39899/
And I find that although the request to v3/auth/tokens fails with the
following error:
REQ: curl -i -X POST http://localhost:35357/v3/auth/tokens -H User-Agent:
python-keystoneclient -H Content-Type: application/json -H X-Auth-Token:
ADMIN TOKEN
REQ BODY: {auth: {identity: {methods: [token], token: {id: ADMIN
TOKEN}}, scope: {OS-TRUST:trust: {id:
7b6d5a4ee39645e3aba11c535e5069f3
RESP: [500] {'date': 'Thu, 15 Aug 2013 17:18:08 GMT', 'content-type':
'application/json', 'content-length': '151', 'vary': 'X-Auth-Token'}
RESP BODY: {error: {message: An unexpected error prevented the server
from fulfilling your request. 'token', code: 500, title: Internal Server
Error}}
Request returned failure status: 500
Traceback (most recent call last):
File trust_reproducer.py, line 61, in module
c_trust.authenticate()
File /opt/stack/python-keystoneclient/keystoneclient/httpclient.py, line
458, in authenticate
resp, body = self.get_raw_token_from_identity_service(**kwargs)
File /opt/stack/python-keystoneclient/keystoneclient/v3/client.py, line
165, in get_raw_token_from_identity_service
'%s' % e)
keystoneclient.exceptions.AuthorizationFailure: Authorization failed: An
unexpected error prevented the server from fulfilling your request. 'token'
(HTTP 500)
I've replaced the real token with ADMIN TOKEN above.
In the keystone log output I see this:
2013-08-15 18:36:57.129 4171 ERROR keystone.common.wsgi [-] 'token'
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi Traceback (most
recent call last):
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi File
/opt/stack/keystone/keystone/common/wsgi.py, line 240, in __call__
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi result =
method(context, **params)
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi File
/opt/stack/keystone/keystone/auth/controllers.py, line 287, in
authenticate_for_token
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi
self.authenticate(context, auth_info, auth_context)
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi File
/opt/stack/keystone/keystone/auth/controllers.py, line 343, in authenticate
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi auth_context)
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi File
/opt/stack/keystone/keystone/auth/plugins/token.py, line 42, in authenticate
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi 'user_id',
token_ref['token_data']['token']['user']['id'])
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi KeyError: 'token'
2013-08-15 18:36:57.129 4171 TRACE keystone.common.wsgi
I'm at keystone git rev 14e090154c10001550127628c2728013f15d4256
I've attached a reproducer I've been testing with (will require
installing the keystoneclient patch mentioned above)
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1212778/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1217447] Re: ldap _get_enabled is returning entire groupOfNames object for enabled_users and enabled_tenants
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1217447 Title: ldap _get_enabled is returning entire groupOfNames object for enabled_users and enabled_tenants Status in OpenStack Identity (Keystone): Fix Released Bug description: If you have 500 users in a tenant, the enabled_users check will return a groupOfNames object with 500 user CNs in it. example ldapsearch: ldapsearch -x -D cn=admin,dc=example,dc=com -wpassword -b cn=enabled_users,ou=Users,dc=example,dc=com member=cn=6ac4f3701ba144888669b7f9026eb456,ou=Users,dc=example,dc=com -s base * OUTPUT * # extended LDIF # # LDAPv3 # base cn=enabled_users,ou=Users,dc=rcb,dc=me with scope baseObject # filter: member=cn=6ac4f3701ba144888669b7f9026eb456,ou=Users,dc=rcb,dc=me # requesting: ALL # # enabled_users, Users, example.com dn: cn=enabled_users,ou=Users,dc=example,dc=com objectClass: groupOfNames member: cn=dumb,dc=nonexistent member: cn=2c0c7a0ad381465e87faea4209780b93,ou=Users,dc=example,dc=com member: cn=6ac4f3701ba144888669b7f9026eb456,ou=Users,dc=example,dc=com member: cn=297b9d63b5fa4dcea1f33a21d732d357,ou=Users,dc=example,dc=com member: cn=fbe7ecef7bf64631943aed243c8a8740,ou=Users,dc=example,dc=com member: cn=2fa87b703eba4d118e8cecd7a9398a59,ou=Users,dc=example,dc=com member: cn=079b66e2f49449279e62057f94d0f370,ou=Users,dc=example,dc=com member: cn=e0c53180c6c344bc806ba558009258cf,ou=Users,dc=example,dc=com member: cn=a7e152918f8c42d18023abb147b129a6,ou=Users,dc=example,dc=com member: cn=3278c2b961a547edb7496f023f73eee5,ou=Users,dc=example,dc=com member: cn=ea70ba972c334fe39210a35ede37a1ab,ou=Users,dc=example,dc=com member: cn=f18cb5cbb6204f44853348abeef8dd9d,ou=Users,dc=example,dc=com member: cn=229366aa6ba3444f9bd8392342be81ab,ou=Users,dc=example,dc=com member: cn=efe4b41cac284a99a0cf4e0164e29ded,ou=Users,dc=example,dc=com member: cn=1f023c493f1241bb9fe02181f134fe13,ou=Users,dc=example,dc=com member: cn=a51ce49edc124096ba6dcb88b8ae518d,ou=Users,dc=example,dc=com member: cn=07d324f7b86d4fc39572a574953bc4a3,ou=Users,dc=example,dc=com * SNIP * member: cn=07d6df2e33bf4dafa93ef30a3b77d97f,ou=Users,dc=example,dc=com member: cn=c238bf336bc6466db5e92bb9ae68dcde,ou=Users,dc=example,dc=com member: cn=12c01d4381e74721b1c46a84b3e56b5a,ou=Users,dc=example,dc=com cn: enabled_users # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 The return size increases with the number of users in the tenant (e.g. 1000 users will return 1000+ rows) The ldap query should supply an Attribute List of CN instead of returning the entire list. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1217447/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1200769] Re: assignment fails for ldap get_user
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1200769
Title:
assignment fails for ldap get_user
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Seems like a bug associated with a recent implementation of
assignment.
File /opt/stack/keystone/tests/_ldap_livetest.py, line 119, in
test_ldap_dereferencing
user_ref = self.identity_api.get_user('alt_fake1')
File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 85, in
get_user
return self.assignment._set_default_domain(ref)
AttributeError: 'Identity' object has no attribute 'assignment'
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1200769/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210675] Re: Role lookup fails for Active Directory
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1210675 Title: Role lookup fails for Active Directory Status in OpenStack Identity (Keystone): Fix Released Bug description: When using Keystone against an Active Directory server, assigned roles aren't found for users. To recreate, set up Keystone to go against Active Directory, create users and roles, then try to get a token scoped to a project as a user. It will fail with User admin is unauthorized for tenant 3c1299e1042a40009691dfb3ad474180 (HTTP 401) I looked into this a bit, and it looks like the problem is that DNs aren't being compared correctly. With Active Directory, when you add a roleOccupant, the DN gets normalized. For exmample, here I add a cn=... dn to an entry, but when I search to get it back, it's now CN=... (the attribute name has been capitalized). $ ldapmodify EOF dn: CN=8bd9f13ac6cf43f7ac85fd95c66d0a4b,CN=3c1299e1042a40009691dfb3ad474180,ou=groups add: roleOccupant roleOccupant: cn=8bd9f13ac6cf43f7ac85fd95c66d0a4b,CN=3c1299e1042a40009691dfb3ad474180,ou=groups EOF modifying entry CN=8bd9f13ac6cf43f7ac85fd95c66d0a4b,CN=3c1299e1042a40009691dfb3ad474180,ou=groups $ ldapsearch -LL -s base \ -b CN=8bd9f13ac6cf43f7ac85fd95c66d0a4b,CN=3c1299e1042a40009691dfb3ad474180,ou=groups \ (objectclass=organizationalRole) roleOccupant version: 1 dn: CN=8bd9f13ac6cf43f7ac85fd95c66d0a4b,CN=3c1299e1042a40009691dfb3ad474180,ou=groups roleOccupant: CN=8bd9f13ac6cf43f7ac85fd95c66d0a4b,CN=3c1299e1042a40009691dfb3a d474180,ou=groups There's suspect code in keystone/assignment/backends/ldap.py: return [self.role._dn_to_id(a.role_dn) for a in role_assignments if a.user_dn == user_dn] here, user_dn is like 'cn=xxx' and the result user_dn is like 'CN=xxx' so they don't match. Keystone needs to do DN comparisons properly, for example by normalizing. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1210675/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1204221] Re: Authorization Failed: Could not find user, None. (HTTP 404)
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1204221 Title: Authorization Failed: Could not find user, None. (HTTP 404) Status in OpenStack Identity (Keystone): Fix Released Bug description: assignment/core.py: def _get_group_project_roles(): ... metadata_ref = self._get_metadata( group_id=x['id'], domain_id=project_ref['domain_id']) self._get_metadata() gets called with user_id=None assignment/backends/ldap.py: def _get_metadata(): ... if (not self.get_project(tenant_id) or user_id and not self.identity_api.get_user(user_id)): self.identity_api.get_user(user_id) raises Could not find user since user_id = None To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1204221/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210175] Re: User operations with LDAP Identity and enabled_mask/user_enabled_default fail
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1210175 Title: User operations with LDAP Identity and enabled_mask/user_enabled_default fail Status in OpenStack Identity (Keystone): Fix Released Bug description: Start with devstack configured for LDAP. Change configuration so that user_enabled_mask=2 and user_enabled_default=512 and restart Keystone server Try to create a user. $ keystone user-create --name blktest2 --tenant demo --pass test2pwd -- fails First problem is, can't get a token. (keystone.common.wsgi): 2013-08-08 09:55:38,954 ERROR wsgi __call__ 'enabled' Traceback (most recent call last): File /opt/stack/keystone/keystone/common/wsgi.py, line 240, in __call__ result = method(context, **params) File /opt/stack/keystone/keystone/token/controllers.py, line 80, in authenticate context, auth) File /opt/stack/keystone/keystone/token/controllers.py, line 242, in _authenticate_local username, DEFAULT_DOMAIN_ID) File /opt/stack/keystone/keystone/common/manager.py, line 44, in _wrapper return f(*args, **kw) File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 87, in get_user_by_name ref = identity.filter_user(self.user.get_by_name(user_name)) File /opt/stack/keystone/keystone/common/ldap/core.py, line 360, in get_by_name res = self.get_all(query) File /opt/stack/keystone/keystone/common/ldap/core.py, line 698, in get_all return super(EnabledEmuMixIn, self).get_all(filter) File /opt/stack/keystone/keystone/common/ldap/core.py, line 368, in get_all for x in self._ldap_get_all(filter)] File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 240, in _ldap_res_to_model obj['enabled_nomask'] = obj['enabled'] KeyError: 'enabled' When work around can't get a token, can't create user. (keystone.common.wsgi): 2013-08-08 09:57:20,717 ERROR wsgi __call__ unsupported operand type(s) for : 'str' and 'int' Traceback (most recent call last): File /opt/stack/keystone/keystone/common/wsgi.py, line 240, in __call__ result = method(context, **params) File /opt/stack/keystone/keystone/identity/controllers.py, line 206, in create_user new_user_ref = self.identity_api.create_user(user_id, user_ref) File /opt/stack/keystone/keystone/identity/core.py, line 72, in create_user return self.driver.create_user(user_id, user) File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 93, in create_user user_ref = self.user.create(user) File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 260, in create self.mask_enabled_attribute(values) File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 250, in mask_enabled_attribute if value != ((values['enabled_nomask'] self.enabled_mask) != TypeError: unsupported operand type(s) for : 'str' and 'int' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1210175/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1204314] Re: token provider/format defaults and uuid unexpected behavior
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1204314 Title: token provider/format defaults and uuid unexpected behavior Status in OpenStack Identity (Keystone): Fix Released Bug description: A couple of configs where it doesn't look like the Keystone server is acting correctly. Config 1: Defaults for both token_format and provider. [signing] # Deprecated in favor of provider in the [token] section #token_format = PKI [token] driver = keystone.token.backends.sql.Token # Provides token persistence. # driver = keystone.token.backends.sql.Token - says keystone.conf [signing] token_format is deprecated in favor of keystone.conf [token] provider I don't have token_format set, so Keystone shouldn't be complaining. Config 2: don't set token_format because it deprecated, use uuid provider. [signing] # Deprecated in favor of provider in the [token] section #token_format = PKI [token] driver = keystone.token.backends.sql.Token # Provides token persistence. # driver = keystone.token.backends.sql.Token # Controls the token construction, validation, and revocation operations. provider = keystone.token.providers.uuid.Provider - server fails to start, saying keystone.conf [signing] token_format (deprecated) conflicts with keystone.conf [token] provider I'm not using token_format because it's deprecated, so the server shouldn't fail to start when I don't use it with uuid provider. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1204314/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1204605] Re: assignment and identity backends should use normal dependency injection
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1204605 Title: assignment and identity backends should use normal dependency injection Status in OpenStack Identity (Keystone): Fix Released Bug description: The assignment and identity backends don't use Keystone's normal dependency injection and the constructor code for these parts is unnecessarily complicated. The reason the backends don't use the assignment backend is because the assignment backend uses the identity backend and the identity backend uses the assignment backend; so there's a circular dependency. The dependency injection code doesn't handle circular dependencies. So the fix is to change the dependency injection code to support circular dependency and then the assignment and identity backends can use the normal dependency injection. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1204605/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1201374] Re: Assignment link in Get /role_assignments not correct for expanded group entries
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1201374 Title: Assignment link in Get /role_assignments not correct for expanded group entries Status in OpenStack Identity (Keystone): Fix Released Bug description: If you call 'GET /role_assignments?effective', then any group grants are expanded in the response to be user grants for each member of the group. Although these entries are correctly returned, the assignment link in such entities does not match the spec. It should return (something like): http://identity:35357/v3/projects/proj_id/groups/group_id/roles/role_id but instead in returns: http://identity:35357/v3/projects/proj_id/users/user_id/roles/role_id Calling GET /role_assignments without the 'effective' flag returns the correct link To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1201374/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1206254] Re: build_ssl_config_file sets permissions on wrong file
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1206254 Title: build_ssl_config_file sets permissions on wrong file Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Security Advisories: Invalid Bug description: BaseCertificateConfigure.build_ssl_config_file() calls Both the index and serial file have their permissions set like this: self._set_permissions(self.ssl_config_file_name, PRIV_PERMS) This looks like a cut-n-paste bug because instead of self.ssl_config_file_name it should have been index_file_name and serial_file_name respectively. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1206254/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1190383] Re: Credential table in the backed still has foreign key reference to id column in tenant table (which is dropped).
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1190383 Title: Credential table in the backed still has foreign key reference to id column in tenant table (which is dropped). Status in OpenStack Identity (Keystone): Fix Released Bug description: Credential table in the backed still has foreign key reference to id column in tenant table sqlite .schema credential CREATE TABLE credential ( id VARCHAR(64) NOT NULL, user_id VARCHAR(64) NOT NULL, project_id VARCHAR(64), blob TEXT NOT NULL, type VARCHAR(255) NOT NULL, extra TEXT, PRIMARY KEY (id), FOREIGN KEY(user_id) REFERENCES user (id), FOREIGN KEY(project_id) REFERENCES tenant (id) ); There is a bug in the sql migration code where we drop the foreign key constraint. https://github.com/openstack/keystone/blob/master/keystone/common/sql/migrate_repo/versions/023_drop_credential_constraints.py To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1190383/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1178738] Re: s3 middleware depends on swift
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1178738 Title: s3 middleware depends on swift Status in OpenStack Identity (Keystone): Fix Released Bug description: The s3 middleware imports: from swift.common import utils as swift_utils This is used to initiate the logging: https://github.com/openstack/keystone/blob/master/keystone/middleware/s3_token.py#L57 self.logger = swift_utils.get_logger(conf, log_route='s3token') howerver, python has a standard logging framework, and we should not be bypassing that. It is up to the project that imports the middleware to set up logging properly, not up to the middleware to conform to multiple projects. THis requires two things: 1, on the swift side, set up the custom logging using the standard python mechanism, and 2 getting this middleware to use the python logging framework. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1178738/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1178532] Re: Keystone Client tests find old contrib.ec2
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1178532 Title: Keystone Client tests find old contrib.ec2 Status in OpenStack Identity (Keystone): Fix Released Bug description: When running older keystone client tests one of the first things to happen is we remove the keystoneclient module from the loaded modules and replace it with the older module that we want to test. At some point (obviously post Essex) an ec2 utils file was moved into the keystone client: keystone/contrib/ec2/core.py:39 from keystoneclient.contrib.ec2 import utils as ec2_utils. From what i can make out our tests will only pass if the Essex and 0.1.1 client tests are run some time after that file has been loaded from a fresh version first. For example: ./run_tests.sh test_keystoneclient test_keystoneclient:KcEssex3TestCase will fail every test with from keystoneclient.contrib.ec2 import utils as ec2_utils ImportError: No module named contrib.ec2 because it successfully loaded the keystoneclient module that was checked out into vendor/python-keystoneclient-essex-3 which does not have the contrib/ec2/utils file. when we run ./run_tests.sh directly keystone/contrib/ec2/core is loaded at least once in the sequence of tests before the client tests reset it. This means that ec2_utils is imported from the keystoneclient in our library path and the tests succeed. As nose resolves tests alphabetically another way of seeing this is to rename test_keystoneclient.py - test_aaakeystoneclient.py and ./run_tests.sh so that these tests runs first. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1178532/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1188301] Re: keystone kvs driver causes process to grow indefinitely and spin on CPU with thousands of keys in a single python dict
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1188301 Title: keystone kvs driver causes process to grow indefinitely and spin on CPU with thousands of keys in a single python dict Status in OpenStack Identity (Keystone): Fix Released Status in tripleo - openstack on openstack: Fix Released Bug description: After about 10 days of being up, things got sluggish in our proof of concept rack. The kvs middleware for tokens is basically just for testing. It is in- process and there is no persistence, and no garbage collection or memory limit at all. We should use sql if we want to persist tokens, or memcache if we are fine with losing some. PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 6955 keystone 20 0 3255m 3.0g 5640 S92 3.2 6532:10 keystone-all To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1188301/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1190149] Re: Token auth fails when token is larger than 8k
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1190149
Title:
Token auth fails when token is larger than 8k
Status in OpenStack Identity (Keystone):
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
The following tests fail when there are 8 or more endpoints registered with
keystone
tempest.api.compute.test_auth_token.AuthTokenTestJSON.test_v3_token
tempest.api.compute.test_auth_token.AuthTokenTestXML.test_v3_token
Steps to reproduce:
- run devstack with the following services (the heat h-* apis push the
endpoint count over the threshold
ENABLED_SERVICES=g-api,g-reg,key,n-api,n-crt,n-obj,n-cpu,n-sch,horizon,mysql,rabbit,sysstat,tempest,s-proxy,s-account,s-container,s-object,cinder,c-api,c-vol,c-sch,n-cond,heat,h-api,h-api-cfn,h-api-cw,h-eng,n-net
- run the failing tempest tests, eg
testr run test_v3_token
- results in the following errors:
ERROR: tempest.api.compute.test_auth_token.AuthTokenTestJSON.test_v3_token
tags: worker-0
--
Traceback (most recent call last):
File tempest/api/compute/test_auth_token.py, line 48, in test_v3_token
self.servers_v3.list_servers()
File tempest/services/compute/json/servers_client.py, line 138, in
list_servers
resp, body = self.get(url)
File tempest/common/rest_client.py, line 269, in get
return self.request('GET', url, headers)
File tempest/common/rest_client.py, line 394, in request
resp, resp_body)
File tempest/common/rest_client.py, line 443, in _error_checker
resp_body = self._parse_resp(resp_body)
File tempest/common/rest_client.py, line 327, in _parse_resp
return json.loads(body)
File /usr/lib64/python2.7/json/__init__.py, line 326, in loads
return _default_decoder.decode(s)
File /usr/lib64/python2.7/json/decoder.py, line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib64/python2.7/json/decoder.py, line 384, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
==
ERROR: tempest.api.compute.test_auth_token.AuthTokenTestXML.test_v3_token
tags: worker-0
--
Traceback (most recent call last):
File tempest/api/compute/test_auth_token.py, line 48, in test_v3_token
self.servers_v3.list_servers()
File tempest/services/compute/xml/servers_client.py, line 181, in
list_servers
resp, body = self.get(url, self.headers)
File tempest/common/rest_client.py, line 269, in get
return self.request('GET', url, headers)
File tempest/common/rest_client.py, line 394, in request
resp, resp_body)
File tempest/common/rest_client.py, line 443, in _error_checker
resp_body = self._parse_resp(resp_body)
File tempest/common/rest_client.py, line 519, in _parse_resp
return xml_to_json(etree.fromstring(body))
File lxml.etree.pyx, line 2993, in lxml.etree.fromstring
(src/lxml/lxml.etree.c:63285)
File parser.pxi, line 1617, in lxml.etree._parseMemoryDocument
(src/lxml/lxml.etree.c:93571)
File parser.pxi, line 1495, in lxml.etree._parseDoc
(src/lxml/lxml.etree.c:92370)
File parser.pxi, line 1011, in lxml.etree._BaseParser._parseDoc
(src/lxml/lxml.etree.c:89010)
File parser.pxi, line 577, in
lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:84711)
File parser.pxi, line 676, in lxml.etree._handleParseResult
(src/lxml/lxml.etree.c:85816)
File parser.pxi, line 627, in lxml.etree._raiseParseError
(src/lxml/lxml.etree.c:85308)
XMLSyntaxError: None
Ran 2 tests in 2.497s (+0.278s)
FAILED (id=214, failures=2)
- run keystone endpoint-delete on endpoints until there is 7 endpoints
- failing tests should now pass
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1190149/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1179955] Re: Disabling a tenant would not disable a user token
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1179955
Title:
Disabling a tenant would not disable a user token
Status in OpenStack Identity (Keystone):
Fix Released
Status in OpenStack Security Notes:
Fix Released
Bug description:
Using keystone/python-keystoneclient master as of today when disabling
a tenant would not disable the users attached to the and would still
have access.
I would not mind to fix it but I want to make sure first if this is
something done by design or I am missing something.
Here is a transcript of my tests :
# Here is the list of my tenants all enabled and nice (devstack default)
chmouel@vm:~$ keystone tenant-list
+--++-+
|id|name| enabled |
+--++-+
| 1f1aeeace0db41e3966a4873877c4dde | admin| True |
| b39f8b007abe472b93ebb5c7fdd80c98 |demo| True |
| 64e78275f80d47f998c4cd1f06e79b1e | invisible_to_admin | True |
| 13fe49ee5e0144d0acd0c89fb901a248 | service | True |
+--++-+
# Let's store the DEMO_TENANT_ID for later
chmouel@vm:~$ DEMO_TENANT=b39f8b007abe472b93ebb5c7fdd80c98
# getting a token with this script available here http://p.chmouel.com/ks
which
chmouel@vm:~$ ks localhost demo:demo ADMIN
[...]
# Using the token I can access to my swift account properly all good here.
chmouel@vm:~$ curl -i -H 'X-Auth-Token: b4b6fb5426914e19bc45cc7780be9b59'
http://172.16.129.140:8080/v1/AUTH_b39f8b007abe472b93ebb5c7fdd80c98
HTTP/1.1 204 No Content
Content-Length: 0
Accept-Ranges: bytes
X-Timestamp: 1368532646.31643
X-Account-Bytes-Used: 0
X-Account-Container-Count: 0
Content-Type: text/html; charset=UTF-8
X-Account-Object-Count: 0
X-Trans-Id: tx390b2fb557fb4cb48a082-0051923f3b
Date: Tue, 14 May 2013 13:42:19 GMT
# Now let's try to disable that tenant
chmouel@vm:~$ keystone tenant-update --enabled false ${DEMO_TENANT}
# tenant is disabled all good
chmouel@vm:~$ keystone tenant-list
+--++-+
|id|name| enabled |
+--++-+
| 1f1aeeace0db41e3966a4873877c4dde | admin| True |
| b39f8b007abe472b93ebb5c7fdd80c98 |demo| False |
| 64e78275f80d47f998c4cd1f06e79b1e | invisible_to_admin | True |
| 13fe49ee5e0144d0acd0c89fb901a248 | service | True |
+--++-+
# we still have access with that same token since it's properly in memcache
chmouel@vm:~$ curl -i -H 'X-Auth-Token: b4b6fb5426914e19bc45cc7780be9b59'
http://172.16.129.140:8080/v1/AUTH_b39f8b007abe472b93ebb5c7fdd80c98
HTTP/1.1 204 No Content
Content-Length: 0
Accept-Ranges: bytes
X-Timestamp: 1368532646.31643
X-Account-Bytes-Used: 0
X-Account-Container-Count: 0
Content-Type: text/html; charset=UTF-8
X-Account-Object-Count: 0
X-Trans-Id: txf9d27a7a8a034304b13cb-0051923f6f
Date: Tue, 14 May 2013 13:43:11 GMT
# let's restart memcache to clear it
chmouel@vm:~$ sudo /etc/init.d/memcached restart
Restarting memcached: memcached.
# but we still have access.
chmouel@vm:~$ curl -i -H 'X-Auth-Token: b4b6fb5426914e19bc45cc7780be9b59'
http://172.16.129.140:8080/v1/AUTH_b39f8b007abe472b93ebb5c7fdd80c98
HTTP/1.1 204 No Content
Content-Length: 0
Accept-Ranges: bytes
X-Timestamp: 1368532646.31643
X-Account-Bytes-Used: 0
X-Account-Container-Count: 0
Content-Type: text/html; charset=UTF-8
X-Account-Object-Count: 0
X-Trans-Id: txbe0c0caf533a4f6e98345-0051923f97
Date: Tue, 14 May 2013 13:43:51 GMT
the json reply when validating token says that the tenant is still
enabled even if it's disabled :
u'tenant': {u'description': None, u'enabled': True, u'id':
u'b39f8b007abe472b93ebb5c7fdd80c98', u'name': u'demo'}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1179955/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1200214] Re: Relax OpenStack upper capping of client versions
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1200214 Title: Relax OpenStack upper capping of client versions Status in Ceilometer: Fix Committed Status in Cinder: Fix Released Status in Orchestration API (Heat): Fix Released Status in OpenStack Dashboard (Horizon): Fix Committed Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: Fix Committed Status in Python client library for heat: Fix Committed Status in Tempest: Fix Released Bug description: Because of the way the gate process pip requirements (one project at a time), on a current gate run we actually install and uninstall python-keystoneclient 4 times in a normal run, flipping back and forth from HEAD to 0.2.5. http://paste.openstack.org/show/39880/ - shows what's going on The net of this means that if any of the projects specify a capped client, it has the potential for preventing that client from being tested in the gate. As part of the discussion here: http://lists.openstack.org/pipermail/openstack- dev/2013-July/011660.html it was suggested to only cap client versions at the major version, since all minor version bumps must be strictly backward compatible by policy. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1200214/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1178032] Re: ldap driver returns hashed passwords
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1178032
Title:
ldap driver returns hashed passwords
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
If I'm using the LDAP identity backend, listing group users includes the
users' passwords (sha-encoded, but that probably depends on LDAP server
configuration).
Keystone shouldn't be handing out users' passwords.
The fix is probably to just remove the password attribute. If Keystone
is just returning all attributes, then it should be changed to only
return the attributes that are known to be safe.
Steps to recreate:
1) start with devstack configured to use LDAP
# set LDAP options in localrc
./stack.sh ...
2) add the default domain since it doesn't exist by default for some
reason.
$ ldapadd -x -D dc=Manager,dc=openstack,dc=org -w ldapadminpwd
dn: cn=default,ou=Domains,dc=openstack,dc=org
objectclass: groupOfNames
member: cn=dummy
3) Create a couple users
(set environment variables so you're admin)
$ keystone user-create --name user1 --pass user1pwd
(example id is 1db4a4d16ba1458aae139db0f43b0904)
$ keystone user-create --name user2 --pass user2pwd
(example id is 4091d11924f5498c8008b655bcf94b9d)
4) Create a group
$ ldapadd -x -D dc=Manager,dc=openstack,dc=org -w ldapadminpwd
dn: ou=UserGroups,dc=openstack,dc=org
objectclass: organizationalUnit
dn: cn=group1,ou=UserGroups,dc=openstack,dc=org
objectclass: groupOfNames
member: cn=1db4a4d16ba1458aae139db0f43b0904,ou=Users,dc=openstack,dc=org
member: cn=4091d11924f5498c8008b655bcf94b9d,ou=Users,dc=openstack,dc=org
5) List the group members:
$ curl -H X-Auth-Token: admintoken
http://localhost:35357/v3/groups/group1/users | python -m json.tool
{
links: {
next: null,
previous: null,
self: http://localhost:5000/v3/groups/group1/users;
},
users: [
{
domain_id: default,
id: 1db4a4d16ba1458aae139db0f43b0904,
links: {
self:
http://localhost:5000/v3/users/1db4a4d16ba1458aae139db0f43b0904;
},
name: user1,
password: {SSHA}eQnQSd6SS6tioL/uN4M7odr/cf2SsjbG
},
{
domain_id: default,
id: 4091d11924f5498c8008b655bcf94b9d,
links: {
self:
http://localhost:5000/v3/users/4091d11924f5498c8008b655bcf94b9d;
},
name: user2,
password: {SSHA}HDtgM7HcrlXnLM7N85htpz1kKYL2npMS
}
]
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1178032/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1177630] Re: LDAP group search doesn't use filter
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1177630 Title: LDAP group search doesn't use filter Status in OpenStack Identity (Keystone): Fix Released Bug description: It doesn't look like the LDAP search for the group list is using the filter specified in the config. If you have a large group OU, the performance hit is very noticeable. The actual method is list_user_groups in the GroupApi class. I've attached the patch we've been using in production in case that helps. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1177630/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1176270] Re: add_user_to_project fails if default role_id hasn't been previously created
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1176270 Title: add_user_to_project fails if default role_id hasn't been previously created Status in OpenStack Identity (Keystone): Fix Released Bug description: The function add_user_to_project (self, tenant_id, user_id) uses the default role_id (config.CONF.role_id) without ensuring it has been created beforehand. If the default role_id hasn't been created, this function throws an error: File /home/edu/OpenStack/keystone/keystone/identity/core.py, line 125, in add_user_to_project config.CONF.member_role_id) File /home/edu/OpenStack/keystone/keystone/identity/backends/kvs.py, line 153, in add_role_to_user_and_project self.get_role(role_id) File /home/edu/OpenStack/keystone/keystone/identity/backends/kvs.py, line 127, in get_role raise exception.RoleNotFound(role_id=role_id) RoleNotFound: Could not find role: 9fe2ff9ee4384b1894a90878d3e92bab To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1176270/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1170455] Re: doc for configuring keystone with apache is incorrect
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1170455 Title: doc for configuring keystone with apache is incorrect Status in OpenStack Identity (Keystone): Fix Released Bug description: doc for configuring keystone with apache is incorrect: On http://docs.openstack.org/developer/keystone/apache-httpd.html it says the following: Make sure you use the SQL driver for tokens, otherwise the tokens will not be shared between the processes of the Apache HTTPD server. To do that, in /etc/keystone/keystone.conf make sure you have set: [token] driver = keystone.token.backends.sql.Token This incorrect. It is no longer required to mandate using the keystone.token.backends.sql.Token I believe the memcache token driver will work just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1170455/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 967832] Re: Instances are still running when a tenant are deleted
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/967832 Title: Instances are still running when a tenant are deleted Status in OpenStack Dashboard (Horizon): Won't Fix Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): Confirmed Bug description: If you have running instances in a tenant, then remove all the users, and finally delete the tenant, the instances are still running. Causing serious trouble, since nobody has access to delete them. Also affects the instances page in horizon. It will break if this scenario occurs. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/967832/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1216447] Re: enable sql tests for oauth1 and delete kvs backend
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1216447 Title: enable sql tests for oauth1 and delete kvs backend Status in OpenStack Identity (Keystone): Fix Released Bug description: Remove the KVS backend of oauth1 extension now instead of later, it will be deprecated eventually, and we don't want folks using it. Also, we need to enable the SQL backend for oauth1 tests To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1216447/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1216408] Re: oauth1 - consumer specifies roles instead of delegator
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1216408 Title: oauth1 - consumer specifies roles instead of delegator Status in OpenStack Identity (Keystone): Fix Released Bug description: From the mailing list [1]: How does the delegate know which role to request? This is unintuitive. A delegator (rather than delegate) knows the role he wants to delegate. One would normally expect the delegator to request Keystone to delegate this role to the named delegate, rather than the delegate asking for a role to be delegated to it, since it requires an out of band communications between the delegator and delegate to take place before the delegation, in which the delegator tells the delegate its un/pw and the role it should ask for. This seems to be a rather contrived exchange of messages. This design fault is present in both the spec and the current implementation. [1]: http://lists.openstack.org/pipermail/openstack- dev/2013-June/010402.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1216408/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220601] Re: format string missing object type
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1220601
Title:
format string missing object type
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
There is a code error in keystone/common/ldap/core.py.
82 def parse_tls_cert(opt):
83 try:
84 return LDAP_TLS_CERTS[opt]
85 except KeyError:
86 raise ValueError(_(
87 'Invalid LDAP TLS certs option: %(option). '
88 'Choose one of: %(options)s') % {
89 'option': opt,
90 'options': ', '.join(LDAP_TLS_CERTS.keys())})
in line 87, %(option) should be changed to %(option)s to show the
corret error message when the exception happens.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1220601/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215493] Re: error when deleting a consumer token (sql)
** Changed in: keystone
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1215493
Title:
error when deleting a consumer token (sql)
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Saw this when creating client support:
$ openstack consumer delete 8b0899403f93496384cddc0755953ba8
ERROR: cliff.app An unexpected error prevented the server from fulfilling
your request. 'token' (HTTP 500)
Keystone error:
(keystone.common.wsgi): 2013-08-22 10:16:41,241 ERROR wsgi __call__ 'token'
Traceback (most recent call last):
File /opt/stack/keystone/keystone/common/wsgi.py, line 237, in __call__
result = method(context, **params)
File /opt/stack/keystone/keystone/contrib/oauth1/controllers.py, line 60,
in delete_consumer
self.token_api.delete_tokens(user_id, consumer_id=consumer_id)
File /opt/stack/keystone/keystone/common/manager.py, line 44, in _wrapper
return f(*args, **kw)
File /opt/stack/keystone/keystone/token/backends/sql.py, line 109, in
delete_tokens
if not self._consumer_matches(consumer_id, token_ref_dict):
File /opt/stack/keystone/keystone/token/backends/sql.py, line 125, in
_consumer_matches
oauth = token_ref_dict['token_data']['token'].get('OS-OAUTH1', {})
KeyError: 'token'
Suggested fix is to wrap the else block of _consumer_matches in a try,
and catch any KeyErrors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1215493/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1218722] Re: add configuration.rst file for oauth1
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1218722 Title: add configuration.rst file for oauth1 Status in OpenStack Identity (Keystone): Fix Released Bug description: I really like the way fabio added this file to the endpoint filtering extension, i'd like to add one for oauth1 as well. example in endpoint filtering: https://github.com/openstack/keystone/blob/9e8f89fa5342c3561979eecaad3e5a8dc63c4ee1/keystone/contrib/endpoint_filter/configuration.rst To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1218722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1218720] Re: add function to tests core that allows adding to paste file
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1218720 Title: add function to tests core that allows adding to paste file Status in OpenStack Identity (Keystone): Fix Released Bug description: Both endpoint filtering and oauth1 extensions have tests in keystone that dynamically create a paste file that adds that specific extension to the pipeline. It would be best to put this in a utils file or just core.py under tests, so other extensions can use it. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1218720/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214476] Re: Default language for API responses has changed
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1214476 Title: Default language for API responses has changed Status in Ceilometer: Fix Committed Status in Cinder: Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): In Progress Bug description: With the delayed message translation changes in oslo, if a language isn't specified in the Accept-Language header on API requests, the default language is now set to en_US. It used to default to the language of the server side if the Accept-Language header was not provided. This behavior should be changed in the delayed message translation support to use the language of the server. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1214476/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215482] Re: conusmer create in sql, description should be nullable
** Changed in: keystone
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1215482
Title:
conusmer create in sql, description should be nullable
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
when playing around with openstack client:
$ openstack consumer create
ERROR: cliff.app An unexpected error prevented the server from fulfilling
your request. (OperationalError) (1048, Column 'description' cannot be null)
'INSERT INTO consumer (id, description, secret, extra) VALUES (%s, %s, %s, %s)'
('0ab66a011274424e9cfd4564809e645c', None, '89382f383c864257ab6620d27f792696',
'{}') (HTTP 500)
In keystone/contrib/oauth/backends/sql, I noticed that:
description = sql.Column(sql.String(64), nullable=False)
This should be nullable=True, we would also need a new migration file
too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1215482/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1213842] Re: Domain extraction from REMOTE_USER name should allow for '@' in username
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1213842 Title: Domain extraction from REMOTE_USER name should allow for '@' in username Status in OpenStack Identity (Keystone): Fix Released Bug description: The ExternalDomain support in REMOTE_USER expects to find an '@' character in the username as the delineator between the name and domain. However, if the username were to contain an '@' itself, the current code breaks. A simple change would be to only extract the domain name to the right of the rightmost '@' character. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1213842/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1211270] Re: missing dependency - babel
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1211270 Title: missing dependency - babel Status in OpenStack Identity (Keystone): Fix Released Bug description: Commit 2c2ebe88a18f3096035812e96ffcf4b23a0395be adds dependency on babel. Babel should be listed in requirements.txt too. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1211270/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215483] Re: update consumer (sql) not actually updating
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1215483 Title: update consumer (sql) not actually updating Status in OpenStack Identity (Keystone): Fix Released Bug description: Noticed this wile developing command line support: $ openstack consumer list | ID | Description | 5387ef1e888e4c1bb903ec1c7cfd500c | con1 $ openstack consumer set 5387ef1e888e4c1bb903ec1c7cfd500c --description myCon $ openstack consumer list | ID | Description | 5387ef1e888e4c1bb903ec1c7cfd500c | con1 The description is never updated for the consumer. I dug around and noticed that within update_consumer(), a session was being started immediately; then another session would be started when calling _get_consumer(). This was causing issues when saving the values and closing the sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1215483/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1211388] Re: Assignment API confirms user in Identity API
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1211388 Title: Assignment API confirms user in Identity API Status in OpenStack Identity (Keystone): Fix Released Bug description: In get_roles_for_user_and_domain and get_roles_for_user_and_project, the assignment API calls into the Identity API to confirm that the user exists. This call is makes it impossible to implement external authentication where the user is queried solely based on their current credential. Also, this call is not required, as the user liveness will and should be checked earlier in the token creation process. If it is important for a certain API call to check if a user uis active, it should be part of the controler call and not part of the core function. These calls are expensive; the make an additional RPC to the Database or Directory store. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1211388/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210099] Re: adding unit test for non-string password
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1210099 Title: adding unit test for non-string password Status in OpenStack Identity (Keystone): Fix Released Bug description: Conversion of non-string passwords has been added but a unit test has not so adding one. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1210099/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215192] Re: Static messages are not localized when requested
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1215192
Title:
Static messages are not localized when requested
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Messages created at import-time are not being translated when
the request is made with Accept-Language.
Note that messages created a run-time are being translated.
Since not many messages are translated at this point, to recreate
can set a translated message yourself. For example, update
keystone/keystone/locale/it_IT/LC_MESSAGES/keystone.po:
#: keystone/exception.py:101
msgid The request you have made requires authentication.
msgstr Wonderful Italian rendition of this
before running `python setup.py compile_catalog`
Then run Keystone and request a resource that requires authentication.
curl -s -H Accept-Language: it http://localhost:5000/v3/auth/tokens
| python -mjson.tool
{
error: {
code: 401,
message: The request you have made requires authentication.,
title: Unauthorized
}
}
-- this should return
{
error: {
code: 401,
message: Wonderful Italian rendition of this,
title: Unauthorized
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1215192/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1209249] Re: pki_setup on OpenSSL 0.9.x aborts
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1209249 Title: pki_setup on OpenSSL 0.9.x aborts Status in OpenStack Identity (Keystone): Fix Released Bug description: when running keystone-manage pki_setup on an older openssl installation, it aborts with the error message: subprocess.CalledProcessError: Command '['openssl', 'ca', '-batch', '-out', '/etc/keystone/ssl/certs/signing_cert.pem', '-config', '/etc/keystone/ssl/certs/openssl.conf', '-days', '3650d', '-cert', '/etc/keystone/ssl/certs/ca.pem', '-keyfile', '/etc/keystone/ssl/certs/cakey.pem', '-infiles', '/etc/keystone/ssl/certs/req.pem']' returned non-zero exit status 1 default is an unsupported message digest type The reason is that support for a default message digest type was only added in recent openssl versions. it seems to be good enough to check for OpenSSL 1.0 to differentiate between old and new OpenSSL versions. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1209249/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214734] Re: file TODO is no longer needed
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1214734 Title: file TODO is no longer needed Status in OpenStack Identity (Keystone): Fix Released Bug description: $ cat TODO - test validate token - policy tests - ec2 support this file is created two years ago, the content is out of date, since we have bugs and blueprints managed on launchpad, i think this file can be deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1214734/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214159] Re: move flake8 option from run_tests.sh to tox.ini
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1214159 Title: move flake8 option from run_tests.sh to tox.ini Status in OpenStack Identity (Keystone): Fix Released Bug description: In run_tests.sh, the function run_flake8() still keep the flake8 option. They should be moved to the section [flake8] to tox.ini, and keep the function run_flake8() simple. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1214159/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214135] Re: add foreign keys to oauth tables
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1214135 Title: add foreign keys to oauth tables Status in OpenStack Identity (Keystone): Fix Released Bug description: As suggested by Adam, the consumer_id should be a foreign key in the RequestToken and AccessToken tables, since it exists in the ConsumerTable. https://review.openstack.org/#/c/29130/64/keystone/contrib/oauth1/migrate_repo/versions/001_add_oauth_tables.py If these changes were to be implemented, then 'delete_consumer' would also need a slight change too. https://review.openstack.org/#/c/29130/64/keystone/contrib/oauth1/backends/sql.py To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1214135/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1185582] Re: When a new v3 credential of ec2 type is created, we store it with a new credential id in the backend
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1185582 Title: When a new v3 credential of ec2 type is created, we store it with a new credential id in the backend Status in OpenStack Identity (Keystone): Fix Released Bug description: When a new v3 credential of ec2 type is created, we store it with a new credential id in the id column in backend. It would be preferred to store the access key id in the id column in backend when the credential of type ec2 is created. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1185582/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1204995] Re: Vestiges of Assignments in LDAP backend
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1204995 Title: Vestiges of Assignments in LDAP backend Status in OpenStack Identity (Keystone): Fix Released Bug description: The LDAP identity backend still has UserRoleAssignments, GroupRoleAssignments, Projects, and Roles. These have all been moved to Assignments, and can and should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1204995/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1208778] Re: set startup log level to info
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1208778 Title: set startup log level to info Status in OpenStack Identity (Keystone): Fix Released Bug description: Would be nice to have this log at INFO level so that it is visible when log level is raised. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1208778/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1172794] Re: Some nose.exc.SkipTest() rendered as ERROR's by run_tests.sh and tox
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1172794 Title: Some nose.exc.SkipTest() rendered as ERROR's by run_tests.sh and tox Status in OpenStack Identity (Keystone): Fix Released Bug description: See http://paste.openstack.org/show/36606/ The above is on a fresh checkout of trunk from today, no modifications. You can clearly see mutiple ERROR results in the test output, and yet at the bottom of the test run you see: Ran 1296 tests in 98.651s OK (SKIP=82) What's going on? This is quite worrying. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1172794/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1136342] Re: v3 controller does not check for required field
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1136342
Title:
v3 controller does not check for required field
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
when creating item, 500 Internal Server Error returned when no name
given. Should return 400 Bad Request code.
ie. curl -X 'POST' -H 'X-Auth-Token: openstack1' -H 'Content-Type:
application/json' -d '{project:{description:est}}'
http://localhost:35357/v3/projects
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1136342/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1202778] Re: assignment driver config option missing
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1202778 Title: assignment driver config option missing Status in OpenStack Identity (Keystone): Fix Released Bug description: Keystone's sample config file doesn't include the assignment.driver option. [assignment] # driver = It's referenced in assignment.Manager: assignment_driver = CONF.assignment.driver To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1202778/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1081932] Re: Length of user_name in database too short for X.509 DNs
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1081932 Title: Length of user_name in database too short for X.509 DNs Status in OpenStack Identity (Keystone): Fix Released Bug description: We are using the REMOTE_AUTH authentication with X.509 certificates, setting the username to the user certificate's DN. However, the name column in the SQL backend is limited to 64 characters, but the certificate DN can be longer than that so we are unable to add some of our users. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1081932/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1208675] Re: user_project role assignement are not cleaned out when deleting a project/tenant
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1208675 Title: user_project role assignement are not cleaned out when deleting a project/tenant Status in OpenStack Identity (Keystone): Fix Released Bug description: Following review https://review.openstack.org/#/c/39878/1/keystone/identity/controllers.py we should deleting roles assigned to user/projects when deleting a project To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1208675/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1179425] Re: Keystone Cannot Translate the REST API message returned from exception.py
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1179425
Title:
Keystone Cannot Translate the REST API message returned from
exception.py
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
The doc string in exception.py of Keystone will be returned with
__doc__ method, but cannot realize the internationalization.
/v2.0/tokens
{
error: {
message: Expecting to find username or userId in
passwordCredentials. The server could not comply with the request since it is
either malformed or otherwise incorrect. The client is assumed to be in error.,
code: 400,
title: Bad Request
}
}
{
error: {
message: The request you have made requires authentication.,
code: 401,
title: Not Authorized
}
}
{
error: {
message: Invalid user / password,
code: 401,
title: Not Authorized
}
}
The message in error which should be translated is returned from the doc
string in excetpion.py of Keystone.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1179425/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1179009] Re: Use testtools for base test class
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1179009 Title: Use testtools for base test class Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in Git Review: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Dashboard (Horizon): Triaged Status in OpenStack Identity (Keystone): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Committed Status in Python client library for Ceilometer: Fix Committed Status in Python client library for heat: Fix Committed Status in OpenStack Object Storage (Swift): New Status in Tempest: Fix Released Status in Trove - Database as a Service: New Status in Zuul: A project gating system: New Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The testtools library has been chosen as the project-wide testing base class. It works across 2.6 and 2.7 and is a library that aims to develop new testing features before inclusion in the standard library. It enforces a few elements of correctness, such as always upcalling standard methods, as well as providing hooks for features such as detail collection and fixtures with cleanup. affects ceilometer affects cinder affects git-review affects glance affects horizon affects keystone affects openstack-ci affects oslo affects python-ceilometerclient affects python-heatclient affects reddwarf affects swift affects tempest affects zuul -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGObtcACgkQ2Jv7/VK1RgH0AgCg8uEx2Za2rXscfse508hhog7p OrMAoK2LacTVUNhbe6R6AxO8XXXB1PWv =QEI2 -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1179009/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1206725] Re: Select N+1 issue in catalog's SQL backend
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1206725 Title: Select N+1 issue in catalog's SQL backend Status in OpenStack Identity (Keystone): Fix Released Bug description: DESCRIPTION SQL backend for keystone catalog has classic select n+1 issue in get_catalog() and get_v3_catalog() methods (for each endpoint get service). Even though the number of endpoints and services is usually not very high, given methods are executed on each authenticate request, which impacts performance of each openstack service regardless of keystone identity backend used. FILES keystone/catalog/backends/sql.py EXPECTED BEHAVIOR Single select ... join SQL statement generated ACTUAL BEHAVIOR N+1 select statements generated, where N is the number of endpoints. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1206725/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214476] Re: Default language for API responses has changed
** Changed in: ceilometer Status: Fix Committed = Fix Released ** Changed in: ceilometer Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1214476 Title: Default language for API responses has changed Status in Ceilometer: Fix Released Status in Cinder: Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): In Progress Bug description: With the delayed message translation changes in oslo, if a language isn't specified in the Accept-Language header on API requests, the default language is now set to en_US. It used to default to the language of the server side if the Accept-Language header was not provided. This behavior should be changed in the delayed message translation support to use the language of the server. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1214476/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1200214] Re: Relax OpenStack upper capping of client versions
** Changed in: ceilometer Status: Fix Committed = Fix Released ** Changed in: ceilometer Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1200214 Title: Relax OpenStack upper capping of client versions Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in Orchestration API (Heat): Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: Fix Committed Status in Python client library for heat: Fix Committed Status in Tempest: Fix Released Bug description: Because of the way the gate process pip requirements (one project at a time), on a current gate run we actually install and uninstall python-keystoneclient 4 times in a normal run, flipping back and forth from HEAD to 0.2.5. http://paste.openstack.org/show/39880/ - shows what's going on The net of this means that if any of the projects specify a capped client, it has the potential for preventing that client from being tested in the gate. As part of the discussion here: http://lists.openstack.org/pipermail/openstack- dev/2013-July/011660.html it was suggested to only cap client versions at the major version, since all minor version bumps must be strictly backward compatible by policy. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1200214/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1178375] Re: Orphan exchanges in Qpid and lack of option for making queues [un]durable
** Changed in: ceilometer Status: Fix Committed = Fix Released ** Changed in: ceilometer Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1178375 Title: Orphan exchanges in Qpid and lack of option for making queues [un]durable Status in Ceilometer: Fix Released Status in Cinder: Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): Fix Committed Status in OpenStack Compute (nova) grizzly series: In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Committed Bug description: Start qpid, nova-api, nova-scheduler, and nova-conductor, and nova- compute. There are orphan direct exchanges in qpid. Checked using qpid-config exchanges. The exchanges continue to grow, presumably, whenever nova- compute does a periodic update over AMQP. Moreover, the direct and topic exchanges are by default durable which is a problem. We want the ability to turn on/off the durable option just like Rabbit options. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1178375/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220317] Re: missing localization in System Info panel
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1220317 Title: missing localization in System Info panel Status in OpenStack Dashboard (Horizon): Fix Released Bug description: in openstack_dashboard/dashboards/admin/info/tables.py string returned by get_network_agent_status and get_network_agent_state need to be localized To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1220317/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220686] Re: Remove spaces from translatable strings
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1220686 Title: Remove spaces from translatable strings Status in OpenStack Dashboard (Horizon): Fix Released Bug description: There are some spaces in translatable strings in Load balancers details pages. It would be nice to remove them for consistensy with the others. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1220686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1217608] Re: Pagination support for Glance and Keystone ignores user-set params
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1217608 Title: Pagination support for Glance and Keystone ignores user-set params Status in OpenStack Dashboard (Horizon): Fix Released Bug description: I noticed that the Glance and Keystone APIs for openstack_dashboard added pagination support. This is good. But they only use the admin-provided value, and not the one in the user cookie. That's bad. The Nova API works as expected. Make the others do the same thing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1217608/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1218058] Re: Sorting columns doesn't preserve row striping
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1218058 Title: Sorting columns doesn't preserve row striping Status in OpenStack Dashboard (Horizon): Fix Released Bug description: tablesorter provides a widget to keep row stripes looking correct, but it is not enabled by default, and Horizon doesn't use it. Ironically, there is a table trigger for filtering search results that fires it, so Horizon uses it, but not for its ostensibly intended purpose. Steps to Reproduce: 1. Find any datatable with multiple rows on it 2. Click on a sortable column Expected results: The row striping should be re-painted so that odd/even semantics are preserved Actual results: The row colors are essentially random, based on the table data To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1218058/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1219676] Re: Small cleanup is still needed
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1219676 Title: Small cleanup is still needed Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Small final cleanup in a few modules is still needed. We could replace some method imports with module imports instead of #noqa comments from H302 check patch set. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1219676/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1216157] Re: Glance image types are configurable, we need to reflect that
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1216157 Title: Glance image types are configurable, we need to reflect that Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Apparently Glance quietly gained the ability for deployer to configure their own set of image types. Horizon has two options: consume the list from the Glance schema API, or use a setting. Given how late it is in the cycle, I'm thinking the latter may be preferrable, with a TODO to consume this from Glance in Icehouse. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1216157/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1216903] Re: logical_resource_id disappeared in favor of resource_name
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1216903 Title: logical_resource_id disappeared in favor of resource_name Status in OpenStack Dashboard (Horizon): Fix Released Status in Python client library for heat: Fix Committed Status in Tempest: Fix Committed Bug description: impact from Heat side : https://review.openstack.org/#/c/43391/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1216903/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215923] Re: Download openrc fail on Firefox if the project contains blanks
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215923 Title: Download openrc fail on Firefox if the project contains blanks Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When downloading the openrc file or the ec2 credentials file on horizon of a tenant that contains blanks, on firefox the filename gets truncated up to the first space. For example on a project called 'My Report' when downloading the openrc you are prompted to download a file called 'My' instead the expected behavior shown on IE or chrome 'My Report-openrc.sh' http://kb.mozillazine.org/Filenames_with_spaces_are_truncated_upon_download To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215923/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215683] Re: Subnet doesn't show on Network Topology
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215683 Title: Subnet doesn't show on Network Topology Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Subnet information of public network doesn't show on Network Topology. https://dl.dropboxusercontent.com/u/7098/openstack/bug_tpv1.png Previously it showed correctly like this. https://dl.dropboxusercontent.com/u/7098/openstack/bug_tpv2.png To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215683/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215996] Re: Cleanup in test_data
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215996 Title: Cleanup in test_data Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Small cleanup in test_data is needed. We could replace a few method imports with module imports instead of #noqa comments. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215996/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215697] Re: Projects on Create User is listing all projects across Domain
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215697 Title: Projects on Create User is listing all projects across Domain Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When there is no Domain Context set, the list of Project displayed on the Create User should be limited to the Domain when the user will be created. Currently projects across Domain are listed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215697/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215543] Re: Aggregates panel throws stack trace if any aggregates actually defined
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215543 Title: Aggregates panel throws stack trace if any aggregates actually defined Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Steps to reproduce: 1. Install the novaclient (should already be installed if you have Horizon installed) 2. Open a terminal window and load a valid openrc into the shell environment 3. Login to Horizon as an admin user Point and go to the Admin - Aggregates panel 4. In the terminal window, run the command: nova aggregate-create kaboom 5. Refresh the panel in Horizon Expected behavior: The page refreshes and shows the new aggregate Actual behavior: The following error: AttributeError at /admin/aggregates/ 'AggregateManager' object has no attribute 'get' ...followed by a stack trace. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215543/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215277] Re: Form tooltips stay on screen when form closed on Escape key press
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215277 Title: Form tooltips stay on screen when form closed on Escape key press Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Steps to reproduce: 1) Open any form with input field that has a tooltip (E.g. tooltip open Instances - Launch instance - Post-creation tab) 2) Focus on input field to see tooltip 3) Press escape key Expected result: Tooltips hidden when form is closed on escape key Actual result: Tooltips stay on screen util the page is refreshed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215277/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215196] Re: Project Users/Groups is showing all users/groups across domain
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1215196 Title: Project Users/Groups is showing all users/groups across domain Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When running in Keystone V3, multiple Domains can be setup. Each Domain can also have a set of User and Groups scoped to it. On the Project Users/Groups page (Project Role Assignment to User/Group), it display the list of Users/Groups that can be assigned to the Project. Currently, all Users/Groups from across Domain are getting displayed. The page should only show Users/Groups that belongs to the same Domain as the Project. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1215196/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1212978] Re: LBaaS Add Health Monitor and Delete Health Monitor links are not displayed as pop-ups
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1212978 Title: LBaaS Add Health Monitor and Delete Health Monitor links are not displayed as pop-ups Status in OpenStack Dashboard (Horizon): Fix Released Bug description: LBaaS Add Health Monitor and Delete Health Monitor links don't open pop-up windows now. That's why there are no Cancel buttons there. It would be nice to solve this problem by adding ajax-modal class to these links. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1212978/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1211780] Re: Remove 'Status' field from Loadbalancer Healthmonitors page
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1211780 Title: Remove 'Status' field from Loadbalancer Healthmonitors page Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Loadbalancer healthmonitor object doesn't have 'status' field anymore. We need to remove it from corresponding page. Instead, 'status' field was added to PoolMonitorAssociation object. That field indicates deployment status of the real healthmonitor. Also, it would be convenient to see a list of pools that are associated with particular HealthMonitor and to see the status of such association. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1211780/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1212405] Re: test_basic_scenario fails in the gate with a 500 error
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1212405 Title: test_basic_scenario fails in the gate with a 500 error Status in OpenStack Dashboard (Horizon): Fix Released Status in Tempest: Invalid Bug description: I've seen this fail a few times now and no one has reported a bug for it. http://paste.openstack.org/show/44154/ Here is one tempest review that hit it: http://logs.openstack.org/46/39346/12/gate/gate-tempest-devstack-vm- postgres-full/da6c383/console.html And a nova one: http://logs.openstack.org/24/41324/4/gate/gate-tempest-devstack-vm- postgres-full/3b72b25/console.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1212405/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210419] Re: Documentation on customizing tabs/tables/actions could be clearer
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1210419 Title: Documentation on customizing tabs/tables/actions could be clearer Status in OpenStack Dashboard (Horizon): Fix Released Bug description: As far as I can tell, disabling pieces of functionality in Horizon leaves users with a few options: They can use the customization_module functionality to smash dashboards and panels, but nothing more fine-grained than that (if I'm wrong, please disabuse me of this notion with an example of how to do it) They can set permissions on various and sundry properties, and let the keystone service catalog work it out, but these aren't evenly distributed throughout the code (yet?) so there's no way to revoke permissions for, say, the Access Security - Floating IPs tab only (again, if I'm wrong on this one, please set me straight) They can add allowed() methods to the classes that support them to deactivate pieces, but that is taking on technical debt if tracking upstream progress is a desired goal. Since all functionality but tabs seems to have a way to control their visibility without altering code, I propose that the default tab allowed() method be altered to allow for overrides via config file. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1210419/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210337] Re: some strings are not translated
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1210337 Title: some strings are not translated Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Specifically: 'Your image %s has been queued for creation.' 'Select a health monitor of %s' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1210337/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210123] Re: Custom css and js documentation
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1210123 Title: Custom css and js documentation Status in OpenStack Dashboard (Horizon): Fix Released Bug description: This patch https://review.openstack.org/#/c/34878/ added the possibility to add custom javascript files used by dashboard. The documentation describing how to add custom stylesheets and javascript to dashboard is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1210123/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1208807] Re: Translator cannot control the order of logged in as user at the upper-right corner
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1208807 Title: Translator cannot control the order of logged in as user at the upper-right corner Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Translator cannot control the word order in translations. The following needs to be improved: - Logged in as: demo at the upper-right. E.g., in Japanese it is better to a username is placed first. - From -mm-dd To -mm-dd in Overview panel. (e.g., -mm-dd kara -mm-dd made is preferred in Japanese) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1208807/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210692] Re: Resizing an instance always yields the message unknown instance
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1210692 Title: Resizing an instance always yields the message unknown instance Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When using the new resize instance functionality, on success, the message is always: Resized instance unknown instance. This is problematic for two reasons: 1. It should know the name of the instance 2. The error message is incorrect — all that has happened is that it has successfully started preparing the resize. A second confirm/revert step is required to complete the resize. To reproduce: 1. Make an instance 2. Hit the Resize Instance button, change its flavor 3. Hilarity ensues Expected behavior: A confirmation message like: Preparing resize on instance minecraft-server. Actual behavior: The message: Resized instance unknown instance. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1210692/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1208714] Re: Update openstack_dashboard/api/nova.py implementation
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1208714 Title: Update openstack_dashboard/api/nova.py implementation Status in OpenStack Dashboard (Horizon): Fix Released Bug description: There is a TODO item in openstack_dashboard/api/nova.py:516 which says, # TODO(gabriel): servers.update method doesn't return anything. :-( Actually this is now fixed in python-novaclient via in63073104665ee4597cf3b7aa8dc2295a8a7db794. Since the issue is fixed, we should just update the implementation to: return novaclient(request).servers.update(instance_id, name=name) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1208714/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1211657] Re: Enable H201: Do not write except:, use except Exception: at the very least
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1211657 Title: Enable H201: Do not write except:, use except Exception: at the very least Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We should gate on H201 as per HACKING.rst To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1211657/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1209177] Re: Quotas tests fail when run as a subset
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1209177 Title: Quotas tests fail when run as a subset Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Although the tests pass when run as part of the full openstack_dashboard test suite, the quota tests behave differently when run as a subset and fail. $ ./run_tests.sh openstack_dashboard.test.tests.quotas ... == ERROR: test_tenant_quota_usages_no_instances_running (openstack_dashboard.test.tests.quotas.QuotaTests) -- Traceback (most recent call last): File /home/jpichon/devel/horizon/openstack_dashboard/test/helpers.py, line 77, in instance_stub_out return fn(self) File /home/jpichon/devel/horizon/openstack_dashboard/test/tests/quotas.py, line 136, in test_tenant_quota_usages_no_instances_running quota_usages = quotas.tenant_quota_usages(self.request) File /home/jpichon/devel/horizon/horizon/utils/memoized.py, line 33, in __call__ value = self.func(*args) File /home/jpichon/devel/horizon/openstack_dashboard/usage/quotas.py, line 120, in tenant_quota_usages disabled_quotas=disabled_quotas): File /home/jpichon/devel/horizon/openstack_dashboard/usage/quotas.py, line 103, in get_tenant_quota_data tenant_id=tenant_id) File /home/jpichon/devel/horizon/openstack_dashboard/usage/quotas.py, line 79, in _get_quota_data tenant_id = request.user.tenant_id File /home/jpichon/devel/horizon/.venv/lib/python2.7/site-packages/django/utils/functional.py, line 203, in inner return func(self._wrapped, *args) AttributeError: 'AnonymousUser' object has no attribute 'tenant_id' ... To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1209177/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1207599] Re: Test failing due to latest version of openstack_auth
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1207599 Title: Test failing due to latest version of openstack_auth Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) folsom series: Fix Committed Status in OpenStack Dashboard (Horizon) grizzly series: Fix Released Bug description: Horizon jobs are failing due to incompatibility with openstack_auth 2013-08-02 00:37:02.136 | == 2013-08-02 00:37:02.136 | ERROR: test_update_project_member_update_error_domain (openstack_dashboard.dashboards.admin.projects.tests.UpdateProjectWorkflowTests) 2013-08-02 00:37:02.136 | -- 2013-08-02 00:37:02.136 | Traceback (most recent call last): 2013-08-02 00:37:02.136 | File /home/jenkins/workspace/gate-horizon-python26/openstack_dashboard/dashboards/admin/projects/tests.py, line 1242, in test_update_project_member_update_error_domain 2013-08-02 00:37:02.136 | self.test_update_project_member_update_error() 2013-08-02 00:37:02.136 | File /home/jenkins/workspace/gate-horizon-python26/openstack_dashboard/test/helpers.py, line 77, in instance_stub_out 2013-08-02 00:37:02.137 | return fn(self) 2013-08-02 00:37:02.137 | File /home/jenkins/workspace/gate-horizon-python26/openstack_dashboard/dashboards/admin/projects/tests.py, line 1232, in test_update_project_member_update_error 2013-08-02 00:37:02.137 | res = self.client.post(url, workflow_data) 2013-08-02 00:37:02.137 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/django/test/client.py, line 463, in post 2013-08-02 00:37:02.137 | response = super(Client, self).post(path, data=data, content_type=content_type, **extra) 2013-08-02 00:37:02.137 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/django/test/client.py, line 297, in post 2013-08-02 00:37:02.137 | return self.request(**r) 2013-08-02 00:37:02.137 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/django/test/client.py, line 424, in request 2013-08-02 00:37:02.137 | six.reraise(*exc_info) 2013-08-02 00:37:02.138 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/django/core/handlers/base.py, line 115, in get_response 2013-08-02 00:37:02.138 | response = callback(request, *callback_args, **callback_kwargs) 2013-08-02 00:37:02.138 | File /home/jenkins/workspace/gate-horizon-python26/horizon/decorators.py, line 38, in dec 2013-08-02 00:37:02.138 | return view_func(request, *args, **kwargs) 2013-08-02 00:37:02.138 | File /home/jenkins/workspace/gate-horizon-python26/horizon/decorators.py, line 84, in dec 2013-08-02 00:37:02.138 | if request.user.is_authenticated(): 2013-08-02 00:37:02.138 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/openstack_auth/user.py, line 189, in is_authenticated 2013-08-02 00:37:02.138 | return self.token is not None and check_token_expiration(self.token) 2013-08-02 00:37:02.138 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/openstack_auth/utils.py, line 55, in check_token_expiration 2013-08-02 00:37:02.138 | if settings.USE_TZ and timezone.is_naive(expiration): 2013-08-02 00:37:02.139 | File /home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/django/utils/timezone.py, line 272, in is_naive 2013-08-02 00:37:02.139 | return value.tzinfo is None or value.tzinfo.utcoffset(value) is None 2013-08-02 00:37:02.139 | AttributeError: 'str' object has no attribute 'tzinfo' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1207599/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1211667] Re: NoReverseMatch: u'domains' is not a registered namespace inside 'horizon:admin'
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1211667 Title: NoReverseMatch: u'domains' is not a registered namespace inside 'horizon:admin' Status in OpenStack Dashboard (Horizon): Fix Released Bug description: when building horizon docs: reading sources... [ 27%] sourcecode/openstack_dashboard/openstack_dashboard.dashboards.admin.domains.tests Traceback (most recent call last): File /usr/lib/python2.7/site-packages/sphinx/ext/autodoc.py, line 321, in import_object __import__(self.modname) File /home/mrunge/fedora/python-django-horizon/horizon-2013.2.b2/openstack_dashboard/dashboards/admin/domains/tests.py, line 41, in module DOMAINS_INDEX_URL = reverse(index_url) File /usr/lib/python2.7/site-packages/django/core/urlresolvers.py, line 489, in reverse (key, ':'.join(resolved_path))) NoReverseMatch: u'domains' is not a registered namespace inside 'horizon:admin' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1211667/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1208558] Re: Refactor project user assignment workflow step
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1208558 Title: Refactor project user assignment workflow step Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Additionally, cleanup unused files related to Project User assignment. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1208558/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1207624] Re: heat panel doesn't parse errors of heat correctly
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = havana-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1207624 Title: heat panel doesn't parse errors of heat correctly Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Heat starts support JSONfied error message since havana-2. Heat panel of horizon should parse the jsonfied error and show only necessary message to end-user. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1207624/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1212748] Re: log in for user with first project disabled fails
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1212748 Title: log in for user with first project disabled fails Status in Django OpenStack Auth: Fix Committed Status in OpenStack Dashboard (Horizon): Fix Released Bug description: A user with roles on multiple projects may not be able to log in. If the first project in the list of projects returned by keystone is disabled, the user will not be able to login and scope the token to a project that is enabled. In openstack_auth/backend.py line 129 should be indented one less. To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1212748/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1202385] Re: Keystone V3 authentication throwing an error for user with no default project
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1202385 Title: Keystone V3 authentication throwing an error for user with no default project Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Unscoped token does not have roles in the response, the code needs to handle non-existent of roles in the auth token. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1202385/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1204375] Re: missing details for network agents in panel /admin/info/ (System Info)
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1204375 Title: missing details for network agents in panel /admin/info/ (System Info) Status in OpenStack Dashboard (Horizon): Fix Released Bug description: At the moment only services defined in Keystone are listed. I also want to have a table showing the available agents of Neutron and there state. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1204375/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1202784] Re: Instances index crashes when instance without an image is present in list
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1202784 Title: Instances index crashes when instance without an image is present in list Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When viewing the instance list, if any instance on the current page does not have an image (because it's attached to a volume), the page crashes with a 'Server' object has no attribute 'attrs' error. Steps to Reproduce: 1.) Log into Horizon 2.) Create a new instance attached to a volume 3.) Visit the instance index view. If necessary, change pages until your volume-based instance is present. Note that this bug is only occurring on master right now. It is not present in the release version. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1202784/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1207214] Re: Status bar of the stack status is running endlessly after updating the stack.
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1207214 Title: Status bar of the stack status is running endlessly after updating the stack. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: ProblemType: Bug DistroRelease: Ubuntu 12.04 LTS Installation type: DevStack with enable Heat Package: master Status bar of the stack continue running after completing the update of a template in heat. Gif with this problem is attached. Scenario: create a stack change something in template update the template To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1207214/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1203394] Re: Floating IPs tab shouldn't use all_tenants
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1203394 Title: Floating IPs tab shouldn't use all_tenants Status in OpenStack Dashboard (Horizon): Fix Released Bug description: openstack_dashboard/dashboards/project/access_and_security/tabs.py fetches the server list with all_tenants=True. But this is not an admin page, so I think it should call without specifying all_tenants. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1203394/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1207506] Re: Untranslated help text in Image Create Form
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1207506 Title: Untranslated help text in Image Create Form Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Help text is not translated for a field in the Create Image Form To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1207506/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1205322] Re: deleting last instance does not show No items to display.
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1205322 Title: deleting last instance does not show No items to display. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When deleting the last instance from the instances section of horizon, an empty table is displayed, when an empty table should actually contain the text No items to display.. Steps: 1) Create a single instance such that a project has only 1 instance. 2) Delete that instance. 3) Empty table is now shown without No items to display.. 4) Additionally, reloading the page presents the text No items to display. in the table. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1205322/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1202415] Re: __repr__ added to ApiResourceWrapper breaks e.g. Server list
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1202415 Title: __repr__ added to ApiResourceWrapper breaks e.g. Server list Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The recent patch Neutron Security Group native support added a __repr__ function to APIResourceWrapper. But this now throws an error if any attributes in _attrs are not defined, which happens for me when I browse to the server list screen in horizon (note that I'm using a special version of nova which doesn't necessarily have the exact same JSON data). In particular, for servers, __repr__ now requires attrs and private_ip, both of which I think are not in the OpenStack API spec (that I could find). +def __repr__(self): +return %s: %s % (self.__class__.__name__, + dict((attr, + getattr(self, attr)) +for attr in self._attrs)) + I'm not entirely sure why __repr__ was included in this patch, so I'm not comfortable just proposing a patch to rip it out. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1202415/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1207070] Re: 'tenant' used in load balancer help text
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1207070 Title: 'tenant' used in load balancer help text Status in OpenStack Dashboard (Horizon): Fix Released Bug description: LBaaS workflow help uses the term 'tenant' rather than 'project'. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1207070/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1197775] Re: adding aggregates panel to admin dashboard
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1197775 Title: adding aggregates panel to admin dashboard Status in OpenStack Dashboard (Horizon): Fix Released Bug description: At the moment I'm missing a view of all defined aggregates in the dashboard. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1197775/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1202079] Re: home/ url pattern is too eager
** Changed in: horizon
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1202079
Title:
home/ url pattern is too eager
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
One of our users reported an excellent bug...
If a bucket/container name , or any section of the key for any object end
with the letter sequence 'home', then attempting to browse to it using the
'Object Store containers' page at
https://dashboard.somecloud/project/containers/ dumps you back at the project
home page at https://dashboard.somecloud/project/ .
For example: a container name of 'home-test' is OK, but 'home' or
'testhome' or 'test-home' are all broken.
Key names like 'test-home' or 'dummypath/test-home' or
'dummypath/test-home/morekey' are also all broken.
In horizon/site_urls.py:
28 urlpatterns = patterns('horizon.views',
29 url(r'home/$', 'user_home', name='user_home')
30 )
home/ is matching anywhere in the URL.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1202079/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1196690] Re: Launch Instance dialog displays flavors in wonky sort order
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1196690 Title: Launch Instance dialog displays flavors in wonky sort order Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When launching an instance, the list of flavors comes back in what appears to be a pseudo-random order. Looking at the code for populate_flavor_choices, it is sorting its inputs, but it's doing a default comparison against the string values of the flavor IDs, which means you get odd artifacts like ['1', '10', '2', '21', '3', '4', '5', ...] in the resulting set. This should probably be sorted by the display name, amount of RAM/VCPU/etc., or likewise. Even better, it should be tunable through local_settings.py to return whatever the admins like. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1196690/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1195712] Re: Adding custom javascript
** Changed in: horizon
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1195712
Title:
Adding custom javascript
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Currently Horizon does not provide the way to add custom javascript
for the application that is built on top of it. All the javascript
files have to be included in horizon/templates/horizon/_scripts.html.
The solution: add the {% block custom_js %}{% endblock %} before the
end of list of scripts in horizon/templates/horizon/_scripts.html.
Dashboard's base.html then overrides block js with inclusion of its
own _scripts.html which extends horizon/_scripts.html and overrides
block custom_js including all js files needed by given dashboard.
Result is single compressed js file consisting both Horizon and
Dashboard's custom scripts.
I belive implementing this is also one of the steps in making Horizon
standalone (http://lists.openstack.org/pipermail/openstack-
dev/2013-June/010808.html)
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1195712/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1190548] Re: Load balancers pool menu is hidden for the lower pool
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1190548 Title: Load balancers pool menu is hidden for the lower pool Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In load balancers pools tab the bottom of pool menu is hidden for the lower pool. It would be nice to make it visible (e.g. like in the instance menu). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1190548/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1189877] Re: flavorid of flavor.create should have auto as its default value
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1189877 Title: flavorid of flavor.create should have auto as its default value Status in OpenStack Dashboard (Horizon): Fix Released Status in Python client library for Nova: Fix Released Bug description: If None is default value, calling flavor.create without flavorid specified will raise an exception. This causes horizon to delete an existing flavour when modify its value. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1189877/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1188622] Re: Docs: Automated class definition pages broken
** Changed in: horizon Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1188622 Title: Docs: Automated class definition pages broken Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The Workflows page looks more bare than it used to be, with only the section titles showing: http://docs.openstack.org/developer/horizon/ref/workflows.html An issue with the automation? https://raw.github.com/openstack/horizon/master/doc/source/ref/workflows.rst It looks like the autoclass ::members:: syntax is not working anymore at the moment, see for instance this is also happening http://docs.openstack.org/developer/horizon/ref/tables.html which is half-empty. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1188622/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
