[Yahoo-eng-team] [Bug 1418384] [NEW] document show --domain option but openstack cannot change project Domain ID
Public bug reported: (openstack) project set admin-apal -h usage: project set [-h] [--name name] [--domain domain] [--description description] [--enable | --disable] [--property key=value] project Set project properties positional arguments: project Project to modify (name or ID) optional arguments: -h, --help show this help message and exit --name name Set project name --domain domain Set domain owning project (name or ID) --description description Set project description --enable Enable project --disable Disable project --property key=value Set a property on project (repeat option to set multiple properties) (openstack) project set admin-apal --domain admin-apal ERROR: openstack Cannot change Domain ID (HTTP 400) ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1418384 Title: document show --domain option but openstack cannot change project Domain ID Status in OpenStack Identity (Keystone): New Bug description: (openstack) project set admin-apal -h usage: project set [-h] [--name name] [--domain domain] [--description description] [--enable | --disable] [--property key=value] project Set project properties positional arguments: project Project to modify (name or ID) optional arguments: -h, --help show this help message and exit --name name Set project name --domain domain Set domain owning project (name or ID) --description description Set project description --enable Enable project --disable Disable project --property key=value Set a property on project (repeat option to set multiple properties) (openstack) project set admin-apal --domain admin-apal ERROR: openstack Cannot change Domain ID (HTTP 400) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1418384/+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 1413459] Re: test_ec2_list_credentials does a wrong test
** 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/1413459 Title: test_ec2_list_credentials does a wrong test Status in OpenStack Identity (Keystone): Fix Released Bug description: https://github.com/openstack/keystone/blob/master/keystone/tests/test_v3_credential.py#L370 def test_ec2_list_credentials(self): Test ec2 credential listing. self._get_ec2_cred_uri() uri = self._get_ec2_cred_uri() r = self.get(uri) cred_list = r.result self.assertEqual(1, len(cred_list)) According to current code, I think the test steps is: 1. create a ec2 credential 2. list all credentials 3. assert that list method can get the ec2 credential created before But, the author used a wrong method to create ec2 credential and asserted the wrong data: 1. The method which creates a ec2 credential is self._get_ec2_cred() 2. cred_list should be r.result['credentials'] To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1413459/+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 1415190] Re: list_user_projects method at assignment manager needs to be removed
** 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/1415190 Title: list_user_projects method at assignment manager needs to be removed Status in OpenStack Identity (Keystone): Fix Released Bug description: The method list_user_projects at assignment manager [1] is not called anywhere. In addition, it makes a call to list_user_projects on assignment drivers, which does not exist at all. The equivalent call in the controller layer calls the list_projects_for_user method instead. [1] https://github.com/openstack/keystone/blob/master/keystone/assignment/core.py#L679-L681 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1415190/+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 1415271] Re: user_enabled_attribute string support is poor
** 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/1415271
Title:
user_enabled_attribute string support is poor
Status in OpenStack Identity (Keystone):
Fix Released
Status in Keystone juno series:
In Progress
Bug description:
When attempting to authenticate with our ldap, we were running into
trouble getting the right value to show up for the user's enabled
attribute.
The result from ldap was:
[('uid=123456789,c=us,ou=our_ldap,o=ibm.com', {'mail': ['sh...@acme.com'],
'passwordisexpired': ['false'], 'uid': ['123456789']})]
which is turned into:
[(u'uid=123456789,c=us,ou=our_ldap,o=ibm.com', {'mail': [u'sh...@acme.com'],
'passwordisexpired': [u'false'], 'uid': [123456789]})]
the _ldap_res_to_model function in ldap/core.py seems to be OK, but
the same one at the identity backend for ldap seems to have a few
bugs:
the object before:
{'email': u'sh...@acme.com', 'enabled': u'false', 'id': 123456789, 'name':
u'sh...@acme.com'}
the object after:
{'dn': u'uid=123456789,c=us,ou=our_ldap,o=ibm.com', 'email':
u'sh...@acme.com', 'enabled': False, 'id': 123456789, 'name':
u'sh...@acme.com'}
Note that the enabled field is still False, just a boolean now instead
of string.
Looks like at:
https://github.com/openstack/keystone/blob/stable/juno/keystone/identity/backends/ldap.py#L223-L227
The check for if type(str) is insufficient, and calling lower, without
the parentheses is pointless.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1415271/+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 1417835] Re: for CADF notifications, the initiator's ID (not name) should be user_id
** 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/1417835 Title: for CADF notifications, the initiator's ID (not name) should be user_id Status in OpenStack Identity (Keystone): Fix Released Bug description: Currently, when emitting CADF notifications the initiator portion of the payload contains an ID field, and an optional Name field. We have been setting the initiators name to the user_id, we should be setting the initiators ID to that value To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1417835/+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 1410750] Re: test_backend has an sql specific test in it
** 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/1410750 Title: test_backend has an sql specific test in it Status in OpenStack Identity (Keystone): Fix Released Bug description: As part of the filter tests in test_backend.py there is a test called test_filter_sql_injection_attack() [1] which ensures we are not susceptible to sql injection attacks. This test should really be in test_backend_sql.py [1] https://github.com/openstack/keystone/blob/31807b4cd69c9ffe08b416505eedb4729aab746f/keystone/tests/test_backend.py#L5365 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1410750/+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 1415959] Re: Role cache details are actually using the assignment values
** 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/1415959 Title: Role cache details are actually using the assignment values Status in OpenStack Identity (Keystone): Fix Released Bug description: When we split the role manager into a separate backend inside the assignment component, we also gave the role manager its own cache config values. However, the actual code still uses the assignment cache values. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1415959/+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 1416459] Re: Disabling identity providers doesn't work
** 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/1416459 Title: Disabling identity providers doesn't work Status in OpenStack Identity (Keystone): Fix Released Bug description: During federated authentication we don't check if the identity provider is disabled or not. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1416459/+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 1405673] Re: db_sync downgrade from 44 to 43 fails
** 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/1405673
Title:
db_sync downgrade from 44 to 43 fails
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
(.venv)breton@bbobrov-pc ~/src/keystone (master*) $ keystone-manage db_sync 44
(.venv)breton@bbobrov-pc ~/src/keystone (master*) $ keystone-manage db_sync 43
2014-12-25 22:18:38.190 31044 CRITICAL keystone [-] NoSuchTableError:
orig_service
2014-12-25 22:18:38.190 31044 TRACE keystone Traceback (most recent call
last):
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/bin/keystone-manage, line 6, in module
2014-12-25 22:18:38.190 31044 TRACE keystone
exec(compile(open(__file__).read(), __file__, 'exec'))
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/bin/keystone-manage, line 44, in module
2014-12-25 22:18:38.190 31044 TRACE keystone cli.main(argv=sys.argv,
config_files=config_files)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/keystone/cli.py, line 311, in main
2014-12-25 22:18:38.190 31044 TRACE keystone CONF.command.cmd_class.main()
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/keystone/cli.py, line 74, in main
2014-12-25 22:18:38.190 31044 TRACE keystone
migration_helpers.sync_database_to_version(extension, version)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/keystone/common/sql/migration_helpers.py, line 204,
in sync_database_to_version
2014-12-25 22:18:38.190 31044 TRACE keystone _sync_common_repo(version)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/keystone/common/sql/migration_helpers.py, line 160,
in _sync_common_repo
2014-12-25 22:18:38.190 31044 TRACE keystone init_version=init_version)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/oslo/db/sqlalchemy/migration.py,
line 82, in db_sync
2014-12-25 22:18:38.190 31044 TRACE keystone version)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/migrate/versioning/api.py,
line 202, in downgrade
2014-12-25 22:18:38.190 31044 TRACE keystone return _migrate(url,
repository, version, upgrade=False, err=err, **opts)
2014-12-25 22:18:38.190 31044 TRACE keystone File string, line 2, in
_migrate
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/migrate/versioning/util/__init__.py,
line 160, in with_engine
2014-12-25 22:18:38.190 31044 TRACE keystone return f(*a, **kw)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/migrate/versioning/api.py,
line 366, in _migrate
2014-12-25 22:18:38.190 31044 TRACE keystone schema.runchange(ver,
change, changeset.step)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/migrate/versioning/schema.py,
line 93, in runchange
2014-12-25 22:18:38.190 31044 TRACE keystone change.run(self.engine, step)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/migrate/versioning/script/py.py,
line 148, in run
2014-12-25 22:18:38.190 31044 TRACE keystone script_func(engine)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/keystone/common/sql/migrate_repo/versions/044_service_enabled.py,
line 143, in downgrade
2014-12-25 22:18:38.190 31044 TRACE keystone
_downgrade_service_table_with_copy(meta, migrate_engine)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/keystone/common/sql/migrate_repo/versions/044_service_enabled.py,
line 120, in _downgrade_service_table_with_copy
2014-12-25 22:18:38.190 31044 TRACE keystone orig_service_table =
sql.Table('orig_service', meta, autoload=True)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/sqlalchemy/sql/schema.py,
line 406, in __new__
2014-12-25 22:18:38.190 31044 TRACE keystone table._init(name, metadata,
*args, **kw)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/sqlalchemy/sql/schema.py,
line 479, in _init
2014-12-25 22:18:38.190 31044 TRACE keystone self._autoload(metadata,
autoload_with, include_columns)
2014-12-25 22:18:38.190 31044 TRACE keystone File
/home/breton/src/keystone/.venv/local/lib/python2.7/site-packages/sqlalchemy/sql/schema.py,
line 503, in _autoload
[Yahoo-eng-team] [Bug 1324610] Re: tools/config/generate_sample.sh has no effect on OS X
** 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/1324610 Title: tools/config/generate_sample.sh has no effect on OS X Status in OpenStack Identity (Keystone): Fix Released Status in The Oslo library incubator: Won't Fix Bug description: Running tools/config/generate_sample.sh doesn't produce a sample conf for me, no matter how I execute it (with or without tox, with a fresh tox env, etc). (os)keystone $ rm etc/keystone.conf.sample (os)keystone $ tox -esample_config sample_config develop-inst-nodeps: /Users/dolph/Projects/keystone sample_config runtests: commands[0] | /Users/dolph/Projects/keystone/tools/config/generate_sample.sh ___ summary ___ sample_config: commands succeeded congratulations :) (os)keystone $ ls -l etc/ total 144 -rw-r--r-- 1 dolph staff 1540 Apr 21 07:14 default_catalog.templates drwxr-xr-x 4 dolph staff136 May 29 10:17 keystone -rw-r--r-- 1 dolph staff 3635 Apr 21 07:14 keystone-paste.ini -rw-r--r-- 1 dolph staff 38278 Apr 29 10:21 keystone.conf -rw-r--r-- 1 dolph staff 1046 Apr 21 07:14 logging.conf.sample -rw-r--r-- 1 dolph staff 6397 Apr 21 07:14 policy.json -rw-r--r-- 1 dolph staff 9032 Apr 21 07:14 policy.v3cloudsample.json (os)keystone $ Note the lack of any keystone.conf.sample! This is on OS X 10.9.3 with: $ bash --version GNU bash, version 3.2.51(1)-release (x86_64-apple-darwin13) Copyright (C) 2007 Free Software Foundation, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1324610/+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 1403929] Re: Improve clarity, encapsulation and performance of assignment type calculation
** 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/1403929 Title: Improve clarity, encapsulation and performance of assignment type calculation Status in OpenStack Identity (Keystone): Fix Released Bug description: There is an assignment type calculation function in: https://github.com/openstack/keystone/blob/master/keystone/assignment/backends/sql.py#L121-L135, which is better to be implemented as an AssignmentType classmethod. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1403929/+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 1403277] Re: should invalidate cache when updating catalog objects successfully
** 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/1403277 Title: should invalidate cache when updating catalog objects successfully Status in OpenStack Identity (Keystone): Fix Released Bug description: Currently, we forgot invalidate cache when updating service, region, endpoint successfully. This leads to a bug: 1. enable the catalog cache 2. create a service 3. get the service 4. update the service 5. get the service again, the service is the one before updating To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1403277/+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 1405710] Re: contrib/endpoint_filter/backends/sql.py should not return db object
** 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/1405710 Title: contrib/endpoint_filter/backends/sql.py should not return db object Status in OpenStack Identity (Keystone): Fix Released Bug description: Manager or controller should adapt different backends. This requires all backends return the same data structure(keystone uses dict). But, currently, some list methods in contrib/endpoint_filter/backends/sql.py return db object. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1405710/+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 1404354] Re: SAWarning using empty IN on assignment.actor_id
** 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/1404354 Title: SAWarning using empty IN on assignment.actor_id Status in OpenStack Identity (Keystone): Fix Released Bug description: Dec 18 02:51:28 ci-overcloud-controller0-nvacfowhjcy2 keystone: /opt/stack/venvs/openstack/local/lib/python2.7/site- packages/sqlalchemy/sql/default_comparator.py:35: SAWarning: The IN- predicate on assignment.actor_id was invoked with an empty sequence. This results in a contradiction, which nonetheless can be expensive to evaluate. Consider alternative strategies for improved performance. This should be fairly straight forward to address. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1404354/+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 1370022] Re: Keystone cannot cope with being behind an SSL terminator for version list
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = kilo-2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1370022
Title:
Keystone cannot cope with being behind an SSL terminator for version
list
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When keystone set up behind SSL termintator then it returns 'http' as
protocol in URLs returned by version list command -
user@host:~$ curl https://MYHOST:5000/
{versions: {values: [{status: stable, updated:
2013-03-06T00:00:00Z, media-types: [{base: application/json,
type: application/vnd.openstack.identity-v3+json}, {base:
application/xml, type:
application/vnd.openstack.identity-v3+xml}], id: v3.0, links:
[{href: http://MYHOST:5000/v3/;, rel: self}]}, {status:
stable, updated: 2014-04-17T00:00:00Z, media-types: [{base:
application/json, type:
application/vnd.openstack.identity-v2.0+json}, {base:
application/xml, type:
application/vnd.openstack.identity-v2.0+xml}], id: v2.0,
links: [{href: http://MYHOST:5000/v2.0/;, rel: self},
{href: http://docs.openstack.org/api/openstack-identity-
service/2.0/content/, type: text/html, rel: describedby},
{href: http://docs.openstack.org/api/openstack-identity-service/2.0
/identity-dev-guide-2.0.pdf, type: application/pdf, rel:
describedby}]}]}}
my ha_proxyconfig -
frontend keystone_main_frontend
bind 172.31.7.253:5000
bind 172.31.7.252:5000 ssl crt /etc/haproxy/certs/runtime
reqadd X-Forwarded-Proto:\ https if { ssl_fc }
default_backend keystone_main_backend
option httpclose
option http-pretend-keepalive
option forwardfor
backend keystone_main_backend
server HOST1 172.31.0.10:5000 check
server HOST2 172.31.0.12:5000 check
server HOST3 172.31.0.16:5000 check
Similar bug is here https://bugs.launchpad.net/heat/+bug/123
And because of this bug last cinder client doesn't work -
user@host:~$cinder --os-username admin --os-tenant-name admin --os-password
password --os-auth-url https://MYHOST:5000/v2.0/ --endpoint-type publicURL
--debug list
ERROR: Unable to establish connection to http://MYHOST:5000/v2.0/tokens
Also - if I set public_endpoint and admin_endpoint in keystone.conf to use
'https' proto then all works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1370022/+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 1406721] Re: RoleNotFound exception not tested for grant APIs
** 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/1406721 Title: RoleNotFound exception not tested for grant APIs Status in OpenStack Identity (Keystone): Fix Released Bug description: In general, our unit testing of granting assignments does not test that we throw a RoleNotFound exception if the role_id supplied does not exit. While it might argued that the assignment APIs shouldn't validate this (like we don't validate user/grouo ids), currently the spec (and the code) says that we do. So we should test for this case. This test will be important to ensure functionality does;t change as we split role management into its own backend (and hence the checking of valid role_id is lifted up into the manager) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1406721/+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 1368772] Re: fakeldap search with SUBTREE scope does not return the base entry
** 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/1368772 Title: fakeldap search with SUBTREE scope does not return the base entry Status in OpenStack Identity (Keystone): Fix Released Bug description: An LDAP search with scope SUBTREE must return the base entry specified in the search request. The BaseLdap.search_s method does not do this. The fix in that method is simple: -results = [] +results = [(base, item_dict)] Unfortunately, there are some tests that fail because they expect the broken behavior. Those tests will also need to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1368772/+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 1406315] Re: multiple non-working migrations
** 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/1406315 Title: multiple non-working migrations Status in OpenStack Identity (Keystone): Fix Released Bug description: bug #1405673 was one of them. bug #1406314 contains a list of migrations tests, which should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1406315/+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 1406393] Re: Doc string info on exceptions incorrect for a number of assignment driver methods
** 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/1406393 Title: Doc string info on exceptions incorrect for a number of assignment driver methods Status in OpenStack Identity (Keystone): Fix Released Bug description: In a number of the doc strings for the assignment driver methods we till list UserNotFound and GroupNotFound as possible exceptions - even though we stopped checking for existence of the user/group in the driver methods a long time ago. Examples are get_grant, list_grants. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1406393/+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 1406627] Re: Inheritance info must be stored inside scope on test_v3_assignment
** 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/1406627 Title: Inheritance info must be stored inside scope on test_v3_assignment Status in OpenStack Identity (Keystone): Fix Released Bug description: The method _build_role_assignment_url_and_entity(..) creates expected role assignments depending on provided parameters. When an inherited role assignment is requested, it is putting 'OS-INHERIT:inherited_to' info inside the main body of the entity, instead of inside the 'scope' key. This reflects on tests, making an assert to never occur [1]. [1] https://github.com/openstack/keystone/blob/f5c06d619c762d5d39e8ec3bc752215ec02b2756/keystone/tests/test_v3.py#L1070-L1071 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1406627/+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 1402916] Re: unable to validate signature from a keystone issued SAML assertion
** 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/1402916 Title: unable to validate signature from a keystone issued SAML assertion Status in OpenStack Identity (Keystone): Fix Released Status in Keystone juno series: Fix Committed Bug description: In the keystone 2 keystone federation workflow, a keystone acting as an SP should be able to validate the signature of a SAML assertion from a keystone acting as an IdP. The current work around is to use the NullSecurity rule in the Security Policy file from Shibboleth (this file is usually located at /etc/shibboleth/security-policy.xml): SecurityPolicies xmlns=urn:mace:shibboleth:2.0:native:sp:config Policy id=default validate=false PolicyRule type=NullSecurity/ /Policy /SecurityPolicies For what it's worth, it seems that mod_shib performs two other checks in a pipeline fashion, the others being ExplicitKey and PKIX checks To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1402916/+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 1418387] [NEW] N/A appear in message instead of id
Public bug reported: In some message it appear N/A, we can use id instead of it. Example: upload image do not enter any character except space in the name, then we can see image id show in the name column. if delete this image, the message appear N/A. I think show id is more useful. ** Affects: horizon Importance: Undecided Assignee: tinytmy (tangmeiyan77) Status: New ** Changed in: horizon Assignee: (unassigned) = tinytmy (tangmeiyan77) ** Summary changed: - id appear in message instead of N/A + N/A appear in message instead of id -- 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/1418387 Title: N/A appear in message instead of id Status in OpenStack Dashboard (Horizon): New Bug description: In some message it appear N/A, we can use id instead of it. Example: upload image do not enter any character except space in the name, then we can see image id show in the name column. if delete this image, the message appear N/A. I think show id is more useful. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1418387/+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 1398656] Re: ceilometer import oslo.concurrency failed issue
** Changed in: cinder 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/1398656 Title: ceilometer import oslo.concurrency failed issue Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Released Status in Designate: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in OpenStack Glance backend store-drivers library (glance_store): In Progress Status in OpenStack Bare Metal Provisioning Service (Ironic): Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): Fix Released Bug description: during ceilometer review and find jenkis failed with following message: 2014-12-03 01:28:04.969 | pep8 runtests: PYTHONHASHSEED='0' 2014-12-03 01:28:04.969 | pep8 runtests: commands[0] | flake8 2014-12-03 01:28:04.970 | /home/jenkins/workspace/gate-ceilometer-pep8$ /home/jenkins/workspace/gate-ceilometer-pep8/.tox/pep8/bin/flake8 2014-12-03 01:28:21.508 | ./ceilometer/utils.py:30:1: H302 import only modules.'from oslo.concurrency import processutils' does not import a module 2014-12-03 01:28:21.508 | from oslo.concurrency import processutils 2014-12-03 01:28:21.508 | ^ 2014-12-03 01:28:21.508 | ./ceilometer/ipmi/platform/ipmitool.py:19:1: H302 import only modules.'from oslo.concurrency import processutils' does not import a module 2014-12-03 01:28:21.508 | from oslo.concurrency import processutils 2014-12-03 01:28:21.508 | ^ 2014-12-03 01:28:21.696 | ERROR: InvocationError: '/home/jenkins/workspace/gate-ceilometer-pep8/.tox/pep8/bin/flake8' 2014-12-03 01:28:21.697 | pep8 runtests: commands[1] | flake8 --filename=ceilometer-* bin This seems https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/processutils.py should change to from oslo_concurrency import processutils To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1398656/+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 1408389] Re: Tests shouldn't rely on provider registration by import
** 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/1408389 Title: Tests shouldn't rely on provider registration by import Status in OpenStack Identity (Keystone): Fix Released Bug description: The tests shouldn't be relying on the provider being loaded by importing a module. When the server is actually run, it only imports the module if the extension is in the paste pipeline, and the tests shoud work similarly. Also, tests shouldn't be using @dependency.requires to inject dependencies -- this is for use by keystone server parts. The tests have their own way of getting dependencies injected by loading the manager, which is similar to how the Keystone server works. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1408389/+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 1407540] Re: Identity driver has unused pointer to assignment
** 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/1407540 Title: Identity driver has unused pointer to assignment Status in OpenStack Identity (Keystone): Fix Released Bug description: During the setup of the identity driver in identity/core, it stores a reference to the assignment_api in the driveralthough this is never used. This should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1407540/+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 1408658] Re: migration 61 downgrade fails using mysql
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1408658 Title: migration 61 downgrade fails using mysql Status in OpenStack Identity (Keystone): Fix Released Bug description: When trying to downgrade from version 61, it fails with an AttributeError. $ keystone-manage db_sync 60 2015-01-08 08:29:56.494 CRITICAL keystone [-] AttributeError: 'MetaData' object has no attribute 'c' 2015-01-08 08:29:56.494 TRACE keystone Traceback (most recent call last): 2015-01-08 08:29:56.494 TRACE keystone File /usr/local/bin/keystone-manage, line 6, in module 2015-01-08 08:29:56.494 TRACE keystone exec(compile(open(__file__).read(), __file__, 'exec')) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/bin/keystone-manage, line 44, in module 2015-01-08 08:29:56.494 TRACE keystone cli.main(argv=sys.argv, config_files=config_files) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 311, in main 2015-01-08 08:29:56.494 TRACE keystone CONF.command.cmd_class.main() 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 74, in main 2015-01-08 08:29:56.494 TRACE keystone migration_helpers.sync_database_to_version(extension, version) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migration_helpers.py, line 204, in sync_database_to_version 2015-01-08 08:29:56.494 TRACE keystone _sync_common_repo(version) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migration_helpers.py, line 160, in _sync_common_repo 2015-01-08 08:29:56.494 TRACE keystone init_version=init_version) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/oslo.db/oslo_db/sqlalchemy/migration.py, line 82, in db_sync 2015-01-08 08:29:56.494 TRACE keystone version) 2015-01-08 08:29:56.494 TRACE keystone File /usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py, line 202, in downgrade 2015-01-08 08:29:56.494 TRACE keystone return _migrate(url, repository, version, upgrade=False, err=err, **opts) 2015-01-08 08:29:56.494 TRACE keystone File string, line 2, in _migrate 2015-01-08 08:29:56.494 TRACE keystone File /usr/local/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py, line 160, in with_engine 2015-01-08 08:29:56.494 TRACE keystone return f(*a, **kw) 2015-01-08 08:29:56.494 TRACE keystone File /usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py, line 366, in _migrate 2015-01-08 08:29:56.494 TRACE keystone schema.runchange(ver, change, changeset.step) 2015-01-08 08:29:56.494 TRACE keystone File /usr/local/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 93, in runchange 2015-01-08 08:29:56.494 TRACE keystone change.run(self.engine, step) 2015-01-08 08:29:56.494 TRACE keystone File /usr/local/lib/python2.7/dist-packages/migrate/versioning/script/py.py, line 148, in run 2015-01-08 08:29:56.494 TRACE keystone script_func(engine) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migrate_repo/versions/061_add_parent_project.py, line 50, in downgrade 2015-01-08 08:29:56.494 TRACE keystone migration_helpers.remove_constraints(list_constraints(meta)) 2015-01-08 08:29:56.494 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migrate_repo/versions/061_add_parent_project.py, line 24, in list_constraints 2015-01-08 08:29:56.494 TRACE keystone 'ref_column': project_table.c.id}] 2015-01-08 08:29:56.494 TRACE keystone AttributeError: 'MetaData' object has no attribute 'c' 2015-01-08 08:29:56.494 TRACE keystone To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1408658/+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 1410182] Re: project schema misses parent_id
** 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/1410182 Title: project schema misses parent_id Status in OpenStack Identity (Keystone): Fix Released Bug description: We forgot to add parent_id parameter check in project schema. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1410182/+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 1407105] Re: Password Change Doesn't Affirmatively Invalidate Sessions
** 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/1407105
Title:
Password Change Doesn't Affirmatively Invalidate Sessions
Status in OpenStack Dashboard (Horizon):
Triaged
Status in OpenStack Identity (Keystone):
Fix Released
Status in Keystone juno series:
Fix Committed
Status in OpenStack Security Advisories:
Won't Fix
Bug description:
This issue is being treated as a potential security risk under
embargo. Please do not make any public mention of embargoed (private)
security vulnerabilities before their coordinated publication by the
OpenStack Vulnerability Management Team in the form of an official
OpenStack Security Advisory. This includes discussion of the bug or
associated fixes in public forums such as mailing lists, code review
systems and bug trackers. Please also avoid private disclosure to
other individuals not already approved for access to this information,
and provide this same reminder to those who are made aware of the
issue prior to publication. All discussion should remain confined to
this private bug report, and any proposed fixes should be added as to
the bug as attachments.
The password change dialog at /horizon/settings/password/ contains the
following code:
code
if user_is_editable:
try:
api.keystone.user_update_own_password(request,
data['current_password'],
data['new_password'])
response = http.HttpResponseRedirect(settings.LOGOUT_URL)
msg = _(Password changed. Please log in again to continue.)
utils.add_logout_reason(request, response, msg)
return response
except Exception:
exceptions.handle(request,
  _('Unable to change password.'))
return False
else:
messages.error(request, _('Changing password is not supported.'))
return False
/code
There are at least two security concerns here:
1) Logout is done by means of an HTTP redirect. Let's say Eve, as MitM, gets
ahold of Alice's token somehow. Alice is worried this may have happened, so
she changes her password. If Eve suspects that the request is a
password-change request (which is the most Eve can do, because we're running
over HTTPS, right? Right!?), then it's a simple matter to block the redirect
from ever reaching the client, or the redirect request from hitting the server.
From Alice's PoV, something weird happened, but her new password works, so
she's not bothered. Meanwhile, Alice's old login ticket continues to work.
2) Part of the purpose of changing a password is generally to block those who
might already have the password from continuing to use it. A password change
should trigger (insofar as is possible) a purging of all active logins/tokens
for that user. That does not happen here.
Frankly, I'm not the least bit sure if I've thought of the worst-case
scenario(s) for point #1. It just strikes me as very strange not to
aggressively/proactively kill the ticket/token(s), instead relying on
the client to do so. Feel free to apply minds smarter and more
devious than my own!
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1407105/+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 1407342] Re: Incorrect comment about circular dependency in assignment manager
** 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/1407342 Title: Incorrect comment about circular dependency in assignment manager Status in OpenStack Identity (Keystone): Fix Released Bug description: The assignment manager has a comment implying that the code in the init() method is working around a circular dependency between identity and assignment. While there is a dependency between assignment and identity in terms of supporting the backward compatibility of the config options for which driver is used, I don't believe there is a circular dependency. The comment should be corrected and be in the init() method itself. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1407342/+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 1407273] Re: Unit tests failing with deprecation errors setuptools 10.2
** 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/1407273 Title: Unit tests failing with deprecation errors setuptools 10.2 Status in OpenStack Identity (Keystone): Fix Released Bug description: setuptools 10.2 was released and it deprecated some commonly used function. Since we recently merged a change to error out when deprecations are used, this causes Keystone unit tests to fail. The gate-keystone-python27 test contains errors like: DeprecationWarning: `require` parameter is deprecated. Use EntryPoint._load instead. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1407273/+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 1409205] Re: Role inheritance section in configuration.rst is outdated
** 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/1409205 Title: Role inheritance section in configuration.rst is outdated Status in OpenStack Identity (Keystone): Fix Released Bug description: Now that hierarchical projects were introduced, inherited role assignments also applies to project hierarchies. The 'Inherited Role Assignment Extension' section at doc/source/configuration.rst needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1409205/+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 1410170] Re: obsolete help text of os_inherit
** 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/1410170 Title: obsolete help text of os_inherit Status in OpenStack Identity (Keystone): Fix Released Bug description: Now, inherited role-assignment also can be from projects higher in the hierarchy. But the help text of os_inherit doesn't mention this, refer to: https://github.com/openstack/keystone/blob/master/etc/keystone.conf.sample#L1192 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1410170/+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 1410748] Re: Incorrectly named test in backend FilterTests
** 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/1410748 Title: Incorrectly named test in backend FilterTests Status in OpenStack Identity (Keystone): Fix Released Bug description: test_list_users_filtered() in FilterTests in test_backend [1] is incorrectly named, since it actually tests uses, groups and projects. [1] https://github.com/openstack/keystone/blob/31807b4cd69c9ffe08b416505eedb4729aab746f/keystone/tests/test_backend.py#L5277 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1410748/+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 1411411] Re: keystone sample config is out of date
** 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/1411411 Title: keystone sample config is out of date Status in OpenStack Identity (Keystone): Fix Released Bug description: A recent change [1] change the keystone config, but didn't update the sample. [1] https://review.openstack.org/#/c/126897/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1411411/+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 1406826] Re: master keystone.conf sample is out of sync
** 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/1406826 Title: master keystone.conf sample is out of sync Status in OpenStack Identity (Keystone): Fix Released Bug description: Looks like an update to keystone.common.policy has not been reflected in our keystone.conf sample, leading to this change being included in other commits. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1406826/+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 1401108] Re: Memcache pool locks on release
** 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/1401108 Title: Memcache pool locks on release Status in OpenStack Identity (Keystone): Fix Released Bug description: At some point Keystone stops processing HTTP requests and HAProxy moves the server out of pool. Once Keystones on all controllers stuck HAProxy starts to respond with HTTP 503 error. Symptoms: ~ HAProxy log: 2014-12-08T11:01:06.135849+00:00 info: 192.168.0.23:34984 [08/Dec/2014:11:01:06.135] keystone-2 keystone-2/NOSRV 0/-1/-1/-1/0 503 212 - - SC-- 366/0/0/0/0 0/0 POST /v2.0/tokens HTTP/1.1 Keystone keeps accepting TCP connection, but hangs at HTTP level (meaning that telnet works, but curl hangs) root@node-21:/var/log/keystone# strace -p 26330 Process 26330 attached - interrupt to quit futex(0xe50420, FUTEX_WAIT_PRIVATE, 0, NULL The last logged message from stuck process: 2014-12-05 17:01:20.749 26330 DEBUG keystone.common.cache._memcache_pool [-] Memcached pool 39391504, thread 139781728069376: Acquiring connection _debug_logger /usr/lib/python2.7/dist-packages/keystone/common/cache/_memcache_pool.py:91 Memcache pool has asymmetric behaviour on aquire and release of a connection: If pool is depleted a new connection is created If pool has reached it's maximum size that connection excess still being pushed back to the pool causing thread lock. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1401108/+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 1393518] Re: v3 service catalog returns services without names, but v2.0 api does not
** 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/1393518
Title:
v3 service catalog returns services without names, but v2.0 api does
not
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
For services without names, it appeared that v2.0 api filtered out
these services (w/o names) from the service catalog. To the contrary,
v3 api presents these services in the service catalog (w/o names)
without filtering them out, which I think is a bug.
Here the dump...
v3
==
$ curl -s -H Content-Type: application/json -d '{ auth: {identity:
{methods: [password],password: {user: {name: admin,domain: {
id: default },password: changemenow}'
http://192.0.2.27:5000/v3/auth/tokens | python -mjson.tool
{
token: {
audit_ids: [
ZVXOhZIzQ_2TRl3FHXs7uQ
],
catalog: [
{ == Service without a
name
endpoints: [],
id: 03759dde22f0498f91ab92fe63da7e37,
type: service-test
},
{
endpoints: [
{
id: 89689c655c194cd1bf2894b798d4fe60,
interface: public,
region: regionOne,
region_id: regionOne,
url: http://192.0.2.27:5000/v2.0;
},
{
id: 927e31c648c24e75b5c28e86da249c37,
interface: internal,
region: regionOne,
region_id: regionOne,
url: http://192.0.2.27:5000/v2.0;
},
{
id: d553b1bebbf84efc96507a5fc353df36,
interface: admin,
region: regionOne,
region_id: regionOne,
url: http://192.0.2.27:35357/v2.0;
}
],
id: 1af4a779d5c6444d885521e1697b3cde,
name: keystone,
type: identity
},
{
endpoints: [
{
id: 75db190e2e3f486c86a948947f1256a9,
interface: admin,
region: regionOne,
region_id: regionOne,
url: http://192.0.2.27:8080/v1;
},
{
id: 826f8098256d46e6b89075b63ccb9a3b,
interface: internal,
region: regionOne,
region_id: regionOne,
url:
http://192.0.2.27:8080/v1/AUTH_edf891223bac4b6ea2a85a15e6ce9cd3;
},
{
id: a9bc3e3ac7c44882aa1f02b0c2940fc8,
interface: public,
region: regionOne,
region_id: regionOne,
url:
http://192.0.2.27:8080/v1/AUTH_edf891223bac4b6ea2a85a15e6ce9cd3;
}
],
id: 301ec05f525d40aaa41be512f820d19a,
name: swift,
type: object-store
},
{== Another service without
a name.
endpoints: [],
id: 5e11382bdd854179b5c3c19f848bf64f,
type: service-test
},
* ommited*
v2.0
$ curl -s -H Content-Type: application/json -d '{auth: {tenantName:
admin, passwordCredentials: {username: admin, password:
changeyourpasswordnow}}}' http://192.0.2.27:5000/v2.0/tokens | python
-mjson.tool
{
access: {
metadata: {
is_admin: 0,
roles: [
9fe2ff9ee4384b1894a90878d3e92bab,
ab13600a7b1f4beab319d0b6860db24b
]
},
serviceCatalog: [
{
endpoints: [
{
adminURL:
http://192.0.2.27:8774/v2/edf891223bac4b6ea2a85a15e6ce9cd3;,
id: 1f999cd0633d409cb477c9343cf747e6,
internalURL:
http://192.0.2.27:8774/v2/edf891223bac4b6ea2a85a15e6ce9cd3;,
publicURL:
http://192.0.2.27:8774/v2/edf891223bac4b6ea2a85a15e6ce9cd3;,
region: regionOne
}
],
endpoints_links: [],
name: nova,
type: compute
},
{
[Yahoo-eng-team] [Bug 1384112] Re: endpoint, service, region can not be updated when using kvs driver
** 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/1384112
Title:
endpoint, service, region can not be updated when using kvs driver
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
region:
curl -i -H X-Auth-Token:$TOKEN -H Content-Type:application/json
http://192.168.70.105:35357/v3/regions/ed5ff7d3e26c48aeaf1f2f9fb2a4ad7e -d
'{region:{description:xxx}}' -X PATCH
{error: {message: An unexpected error prevented the server from
fulfilling your request: 'id' (Disable debug mode to suppress these
details.), code: 500, title: Internal Server Error}}
service:
curl -i -H X-Auth-Token:$TOKEN -H Content-Type:application/json
http://192.168.70.105:35357/v3/services/f101743b55e54d2ba9cbf71d1f3456fc -d
'{service:{type:yy}}' -X PATCH
{error: {message: An unexpected error prevented the server from
fulfilling your request: 'id' (Disable debug mode to suppress these
details.), code: 500, title: Internal Server Error}}
endpoint:
curl -i -H X-Auth-Token:$TOKEN -H Content-Type:application/json
http://192.168.70.105:35357/v3/endpoints/bbe21bf654e442edb21716cc00fb1c58 -d
'{endpoint:{zz:tt}}' -X PATCH
{error: {message: An unexpected error prevented the server from
fulfilling your request: 'region_id' (Disable debug mode to suppress
these details.), code: 500, title: Internal Server Error}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1384112/+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 1398656] Re: ceilometer import oslo.concurrency failed issue
** 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/1398656 Title: ceilometer import oslo.concurrency failed issue Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Committed Status in Designate: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in OpenStack Glance backend store-drivers library (glance_store): In Progress Status in OpenStack Bare Metal Provisioning Service (Ironic): Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): Fix Released Bug description: during ceilometer review and find jenkis failed with following message: 2014-12-03 01:28:04.969 | pep8 runtests: PYTHONHASHSEED='0' 2014-12-03 01:28:04.969 | pep8 runtests: commands[0] | flake8 2014-12-03 01:28:04.970 | /home/jenkins/workspace/gate-ceilometer-pep8$ /home/jenkins/workspace/gate-ceilometer-pep8/.tox/pep8/bin/flake8 2014-12-03 01:28:21.508 | ./ceilometer/utils.py:30:1: H302 import only modules.'from oslo.concurrency import processutils' does not import a module 2014-12-03 01:28:21.508 | from oslo.concurrency import processutils 2014-12-03 01:28:21.508 | ^ 2014-12-03 01:28:21.508 | ./ceilometer/ipmi/platform/ipmitool.py:19:1: H302 import only modules.'from oslo.concurrency import processutils' does not import a module 2014-12-03 01:28:21.508 | from oslo.concurrency import processutils 2014-12-03 01:28:21.508 | ^ 2014-12-03 01:28:21.696 | ERROR: InvocationError: '/home/jenkins/workspace/gate-ceilometer-pep8/.tox/pep8/bin/flake8' 2014-12-03 01:28:21.697 | pep8 runtests: commands[1] | flake8 --filename=ceilometer-* bin This seems https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/processutils.py should change to from oslo_concurrency import processutils To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1398656/+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 1383676] Re: endless loop when deleting region
** 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/1383676
Title:
endless loop when deleting region
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Reproduce:
1. create region A
2. create region B with parent A
3. update the parent of A to B
4. delete A or B
The error message:
{error: {message: An unexpected error prevented the server from
fulfilling your request: maximum recursion depth exceeded while getting the str
of an object (Disable debug mode to suppress these details.), code: 500,
title: Internal Server Error}}
I have two solutions:
1. check circle when creating or updating region
2. do not allow the update of `parent_region_id`
I prefer the second one, it is simple enough. Any suggestion?
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1383676/+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 1210261] Re: remove openstack.common.context
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1210261 Title: remove openstack.common.context Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): Confirmed Status in Logging configuration library for OpenStack: Fix Released Bug description: relates to https://bugs.launchpad.net/neutron/+bug/1208734, and according to https://github.com/openstack/oslo- incubator/blob/master/MAINTAINERS#L87, i think we'd better remove openstack/comon/context To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1210261/+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 1403068] Re: Tests fail with python 2.7.9
** Changed in: cinder
Status: Fix Committed = Fix Released
** Changed in: cinder
Milestone: None = kilo-2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1403068
Title:
Tests fail with python 2.7.9
Status in Cinder:
Fix Released
Status in OpenStack Identity (Keystone):
In Progress
Status in OpenStack Neutron (virtual network service):
Fix Committed
Bug description:
Tests that require SSL fail on python 2.7.9 due to the change in
python uses SSL certificates.
==
FAIL: cinder.tests.test_wsgi.TestWSGIServer.test_app_using_ipv6_and_ssl
cinder.tests.test_wsgi.TestWSGIServer.test_app_using_ipv6_and_ssl
--
_StringException: Traceback (most recent call last):
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 237, in
test_app_using_ipv6_and_ssl
response = open_no_proxy('https://[::1]:%d/' % server.port)
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 47, in
open_no_proxy
return opener.open(*args, **kwargs)
File /usr/lib/python2.7/urllib2.py, line 431, in open
response = self._open(req, data)
File /usr/lib/python2.7/urllib2.py, line 449, in _open
'_open', req)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 1240, in https_open
context=self._context)
File /usr/lib/python2.7/urllib2.py, line 1197, in do_open
raise URLError(err)
URLError: urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
failed (_ssl.c:581)
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 237, in
test_app_using_ipv6_and_ssl
response = open_no_proxy('https://[::1]:%d/' % server.port)
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 47, in
open_no_proxy
return opener.open(*args, **kwargs)
File /usr/lib/python2.7/urllib2.py, line 431, in open
response = self._open(req, data)
File /usr/lib/python2.7/urllib2.py, line 449, in _open
'_open', req)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 1240, in https_open
context=self._context)
File /usr/lib/python2.7/urllib2.py, line 1197, in do_open
raise URLError(err)
URLError: urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
failed (_ssl.c:581)
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 237, in
test_app_using_ipv6_and_ssl
response = open_no_proxy('https://[::1]:%d/' % server.port)
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 47, in
open_no_proxy
return opener.open(*args, **kwargs)
File /usr/lib/python2.7/urllib2.py, line 431, in open
response = self._open(req, data)
File /usr/lib/python2.7/urllib2.py, line 449, in _open
'_open', req)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 1240, in https_open
context=self._context)
File /usr/lib/python2.7/urllib2.py, line 1197, in do_open
raise URLError(err)
URLError: urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
failed (_ssl.c:581)
==
FAIL: cinder.tests.test_wsgi.TestWSGIServer.test_app_using_ssl
cinder.tests.test_wsgi.TestWSGIServer.test_app_using_ssl
--
_StringException: Traceback (most recent call last):
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 212, in
test_app_using_ssl
response = open_no_proxy('https://127.0.0.1:%d/' % server.port)
File /tmp/buildd/cinder-2014.2/cinder/tests/test_wsgi.py, line 47, in
open_no_proxy
return opener.open(*args, **kwargs)
File /usr/lib/python2.7/urllib2.py, line 431, in open
response = self._open(req, data)
File /usr/lib/python2.7/urllib2.py, line 449, in _open
'_open', req)
File /usr/lib/python2.7/urllib2.py, line 409, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 1240, in https_open
context=self._context)
File /usr/lib/python2.7/urllib2.py, line 1197, in do_open
raise URLError(err)
URLError: urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
failed (_ssl.c:581)
Traceback (most recent call last):
[Yahoo-eng-team] [Bug 1418830] [NEW] Document Bug: service API works different than github doc (documented find by name but code work by type) - Openstack CLI
Public bug reported:
In the document it's said:
https://github.com/openstack/keystone/blob/master/doc/source/cli_examples.rst
Services
service create
positional arguments:
service-name New service name
optional arguments:
--type service-type New service type (compute, image, identity, volume, etc)
--description service-description New service description
example:
$ openstack service create nova --type compute --description Nova Compute
Service
But during test, openstack CLI can only find service by 'Type' but not 'Name'.
Is it a doc issue or code issue?
Here's the testing:
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service list
+
ID NameTypeEnabled
+
095c0ff1e4be4126aad6f0a2270db4c4ceilometer meteringTrue
0bf8d9ffa1ad489093f861731bf36e3fheatorchestration True
270bd87014f34142af9a4ce97d85517dsherpa hp-catalog True
34aad9f100194ef0b0f0b819cd418371keystoneidentityTrue
50b54b4a8a88426e841be4f0dda3967bnovacomputev3 True
96084d6e48eb40e8b19df15ab33d3d35glance image True
aada972fb0bb4021b46236bc13dfb832swift object-storeTrue
b2789fb971574f2d82ae9edecd062584cinder volume True
ce17772214884cd0baff1611bbb0a07cneutron network True
eae5cc974ec94d649e24bcf19a406662novacompute True
f2f1590d30d7451ba6a43f5a00a6b607ec2 ec2 True
+
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service show nova
ERROR: openstack No service with a type, name or ID of 'nova' exists.
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service create test
--type compute --description test
usage: openstack service create [-h] [-f
{shell,table,value}] [-c COLUMN]
[--max-width integer] [--prefix PREFIX]
[--name service-name] [--enable | --disable]
service-type
openstack service create: error: unrecognized arguments: --type compute
--description test
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service create compute
--name Test --description test
usage: openstack service create [-h] [-f {shell,table,value}
] [-c COLUMN]
[--max-width integer] [--prefix PREFIX]
[--name service-name] [--enable | --disable]
service-type
openstack service create: error: unrecognized arguments: --description test
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service create compute
--name Test
-+
Field Value
-+
enabled True
id f38310d398b44513b46e8a3eacda4f9a
nameTest
typecompute
-+
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service list
+
ID NameTypeEnabled
+
095c0ff1e4be4126aad6f0a2270db4c4ceilometer meteringTrue
0bf8d9ffa1ad489093f861731bf36e3fheatorchestration True
270bd87014f34142af9a4ce97d85517dsherpa hp-catalog True
34aad9f100194ef0b0f0b819cd418371keystoneidentityTrue
50b54b4a8a88426e841be4f0dda3967bnovacomputev3 True
96084d6e48eb40e8b19df15ab33d3d35glance image True
aada972fb0bb4021b46236bc13dfb832swift object-storeTrue
b2789fb971574f2d82ae9edecd062584cinder volume True
ce17772214884cd0baff1611bbb0a07cneutron network True
eae5cc974ec94d649e24bcf19a406662novacompute True
f2f1590d30d7451ba6a43f5a00a6b607ec2 ec2 True
f38310d398b44513b46e8a3eacda4f9aTestcompute True
+
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service delete
f38310d398b44513b46e8a3eacda4f9a
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service show compute
//show by 'Type' too
-+
Field Value
-+
description Nova Compute Service
enabled True
id eae5cc974ec94d649e24bcf19a406662
namenova
typecompute
-+
(test_venv)cetest@cer106n0001:~/ysong/ysong$ openstack service show nova
ERROR: openstack No service with a type, name or ID of 'nova' exists.
(openstack) service list
+
ID NameTypeEnabled
+
0e28690b0f9e4b7d8935027ab3f426cfneutron network True
57fa94acbef24782b64069035374a7b3cinder volume True
827eba724d814920b34fa7196bb09432sherpa hp-catalog True
90ebb68d1fce4dd99bd37ab0e749a022novacomputev3 True
[Yahoo-eng-team] [Bug 1418837] [NEW] [Document Bug] credential set not work as help document (optional parameters actually required) - openstackcli
Public bug reported:
(openstack) credential set -h
usage: credential set [-h] [--user user] [--type type] [--data data]
[--project project]
credential-id
Set credential command
positional arguments:
credential-id ID of credential to change
optional arguments:
-h, --help show this help message and exit
--user user Name or ID of user that owns the credential
--type type New credential type
--data data New credential data
--project project Project name or ID which limits the scope of the
credential
(openstack) credential set
50002651b7c5887a081b74b80fa0586a493857008c611c1b1e3a25c09d34e0cd --project admin
ERROR: openstack update() takes at least 3 arguments (3 given)
(openstack) credential set
50002651b7c5887a081b74b80fa0586a493857008c611c1b1e3a25c09d34e0cd --type ec2
--user apal-test --project apal-test
ERROR: openstack Credential requires blob to be specified
(openstack) credential set
50002651b7c5887a081b74b80fa0586a493857008c611c1b1e3a25c09d34e0cd --type ec2
--user apal-test --project apal-test --data
{\access\: \testbfec279f1e904166a864bb0a4c4432ac\, \secret\:
\7fd9c120d7f44bc7a491b08cf7792fedtset\}
(openstack) (test_venv)cetest@cer106n0035:~$
** Affects: keystone
Importance: Undecided
Status: New
** Tags: documentation
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1418837
Title:
[Document Bug] credential set not work as help document (optional
parameters actually required) - openstackcli
Status in OpenStack Identity (Keystone):
New
Bug description:
(openstack) credential set -h
usage: credential set [-h] [--user user] [--type type] [--data data]
[--project project]
credential-id
Set credential command
positional arguments:
credential-id ID of credential to change
optional arguments:
-h, --help show this help message and exit
--user user Name or ID of user that owns the credential
--type type New credential type
--data data New credential data
--project project Project name or ID which limits the scope of the
credential
(openstack) credential set
50002651b7c5887a081b74b80fa0586a493857008c611c1b1e3a25c09d34e0cd --project admin
ERROR: openstack update() takes at least 3 arguments (3 given)
(openstack) credential set
50002651b7c5887a081b74b80fa0586a493857008c611c1b1e3a25c09d34e0cd --type ec2
--user apal-test --project apal-test
ERROR: openstack Credential requires blob to be specified
(openstack) credential set
50002651b7c5887a081b74b80fa0586a493857008c611c1b1e3a25c09d34e0cd --type ec2
--user apal-test --project apal-test --data
{\access\: \testbfec279f1e904166a864bb0a4c4432ac\, \secret\:
\7fd9c120d7f44bc7a491b08cf7792fedtset\}
(openstack) (test_venv)cetest@cer106n0035:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1418837/+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 1417539] Re: When trying to delete Trove instance that is in BUILD state, Horizon shows an error, which is ok, but the error message doesn't show real reason of why instance can'
422 is a RecoverableError, no need too detail info.
class BatchAction(Action):
def handle(self, table, request, obj_ids):
action_success = []
action_failure = []
action_not_allowed = []
for datum_id in obj_ids:
datum = table.get_object_by_id(datum_id)
datum_display = table.get_object_display(datum) or _(N/A)
if not table._filter_action(self, request, datum):
action_not_allowed.append(datum_display)
LOG.info('Permission denied to %s: %s' %
(self._get_action_name(past=True).lower(),
datum_display))
continue
try:
self.action(request, datum_id)
# Call update to invoke changes if needed
self.update(request, datum)
action_success.append(datum_display)
self.success_ids.append(datum_id)
LOG.info('%s: %s' %
(self._get_action_name(past=True), datum_display))
except Exception as ex:
# Handle the exception but silence it since we'll display
# an aggregate error message later. Otherwise we'd get
# multiple error messages displayed to the user.
if getattr(ex, _safe_message, None):
ignore = False
else:
ignore = True
action_failure.append(datum_display)
exceptions.handle(request, ignore=ignore)
# Begin with success message class, downgrade to info if problems.
success_message_level = messages.success
if action_not_allowed:
msg = _('You are not allowed to %(action)s: %(objs)s')
params = {action:
self._get_action_name(action_not_allowed).lower(),
objs: functions.lazy_join(, , action_not_allowed)}
messages.error(request, msg % params)
success_message_level = messages.info
if action_failure:
msg = _('Unable to %(action)s: %(objs)s')
params = {action: self._get_action_name(action_failure).lower(),
objs: functions.lazy_join(, , action_failure)}
messages.error(request, msg % params)
success_message_level = messages.info
if action_success:
msg = _('%(action)s: %(objs)s')
params = {action:
self._get_action_name(action_success, past=True),
objs: functions.lazy_join(, , action_success)}
success_message_level(request, msg % params)
return shortcuts.redirect(self.get_success_url(request))
def handle_recoverable(request, message, redirect, ignore, escalate, handled,
force_silence, force_log,
log_method, log_entry, log_level):
if not force_silence and not handled and (not ignore or force_log):
# Default recoverable error to WARN log level
log_method = getattr(LOG, log_level or warning)
log_method(error_color(Recoverable error: %s % log_entry))
if not ignore and not handled:
messages.error(request, message or log_entry)
if redirect:
raise Http302(redirect)
HANDLE_EXC_METHODS = [
{'exc': UNAUTHORIZED, 'handler': handle_unauthorized, 'set_wrap': False},
{'exc': NOT_FOUND, 'handler': handle_notfound, 'set_wrap': True},
{'exc': RECOVERABLE, 'handler': handle_recoverable, 'set_wrap': True},
]
def handle(request, message=None, redirect=None, ignore=False,
escalate=False, log_level=None, force_log=None):
Centralized error handling for Horizon.
Because Horizon consumes so many different APIs with completely
different ``Exception`` types, it's necessary to have a centralized
place for handling exceptions which may be raised.
Exceptions are roughly divided into 3 types:
#. ``UNAUTHORIZED``: Errors resulting from authentication or authorization
problems. These result in being logged out and sent to the login screen.
#. ``NOT_FOUND``: Errors resulting from objects which could not be
located via the API. These generally result in a user-facing error
message, but are otherwise returned to the normal code flow. Optionally
a redirect value may be passed to the error handler so users are
returned to a different view than the one requested in addition to the
error message.
#. RECOVERABLE: Generic API errors which generate a user-facing message
but drop directly back to the regular code flow.
All other exceptions bubble the stack as normal unless the ``ignore``
argument is passed in as ``True``, in which case only unrecognized
errors are bubbled.
If the exception is not re-raised, an appropriate wrapper exception
class indicating the type of exception that was encountered will
[Yahoo-eng-team] [Bug 1418568] [NEW] cannot install cloud-images-utils on precise
Public bug reported: As per https://bugs.launchpad.net/juju-core/+bug/1407699/comments/4, cloud-images-utils cannot be installed on precise. This is blocking the release of Juju 1.22, as that needs to have cloud-images-utils available, and tries to apt-get install it during cloud init, but the apt install doesn't go ahead due to the above problem. As per the above comment: smoser we can fix that with a packaging change to cloud-init in precise. smoser to depend on cloud-image-utils | cloud-utils Could we please get that packaging change done and the new cloud-init apckage propagated to the archives? ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1418568 Title: cannot install cloud-images-utils on precise Status in Init scripts for use on cloud images: New Bug description: As per https://bugs.launchpad.net/juju-core/+bug/1407699/comments/4, cloud-images-utils cannot be installed on precise. This is blocking the release of Juju 1.22, as that needs to have cloud-images-utils available, and tries to apt-get install it during cloud init, but the apt install doesn't go ahead due to the above problem. As per the above comment: smoser we can fix that with a packaging change to cloud-init in precise. smoser to depend on cloud-image-utils | cloud-utils Could we please get that packaging change done and the new cloud-init apckage propagated to the archives? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1418568/+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 1417539] Re: When trying to delete Trove instance that is in BUILD state, Horizon shows an error, which is ok, but the error message doesn't show real reason of why instance can'
i don't get it, why this bug was marked as Invalid ??? Poor exception handling in Horizon leads to such problems. Python-troveclient explicitly says why instance can't be deleted, but Horizon seems like doesn't care about original error message, so that's why it leads to bad user experience with Horizon. ** Changed in: horizon Status: Invalid = New -- 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/1417539 Title: When trying to delete Trove instance that is in BUILD state, Horizon shows an error, which is ok, but the error message doesn't show real reason of why instance can't be deleted Status in OpenStack Dashboard (Horizon): New Bug description: When trying to delete Trove instance that is in BUILD state, Horizon shows an error, which is ok, but the error message doesn't show real reason of why instance can't be delete. Here's what Trove says when user tries to delete instance in BUILD state: ubuntu@ubuntu:~/trove-integration/scripts$ trove delete 4ff27e9b-236d-403c-8127-884f781cfd3d ERROR: Instance 4ff27e9b-236d-403c-8127-884f781cfd3d is not ready. (HTTP 422) Attachment contains screenshot of what Horizon displays to user. This should be fixed. And fix should provide error handing improvement that explicitly shows actual reason instaed of what Horizon have right now. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1417539/+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 1296202] Re: openvswitch is sometimes restarting or times out, and this causes neutron-openvswitch-agent to crash
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1296202 Title: openvswitch is sometimes restarting or times out, and this causes neutron-openvswitch-agent to crash Status in OpenStack Neutron (virtual network service): Fix Released Bug description: This was observed recently durin an Ironic CI run: 2014-03-22 02:38:53.436 7916 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: ovsdb-client: unix:/var/run/openvswitch/db.sock: receive failed (End of file) 2014-03-22 02:38:53.690 7916 ERROR neutron.agent.linux.ovs_lib [-] Unable to execute ['ovs-vsctl', '--timeout=10', 'list-ports', 'br-int']. Exception: Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=10', 'list-ports', 'br-int'] Exit code: 1 Stdout: '' Stderr: '2014-03-22T02:38:53Z|1|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)\novs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)\n' 2014-03-22 02:38:53.693 7916 ERROR neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Error while processing VIF ports 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1212, in rpc_loop 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent port_info = self.scan_ports(ports, updated_ports_copy) 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 815, in scan_ports 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent cur_ports = self.int_br.get_vif_port_set() 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/agent/linux/ovs_lib.py, line 311, in get_vif_port_set 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent port_names = self.get_port_name_list() 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/agent/linux/ovs_lib.py, line 267, in get_port_name_list 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent res = self.run_vsctl([list-ports, self.br_name], check_error=True) 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/agent/linux/ovs_lib.py, line 74, in run_vsctl 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent ctxt.reraise = False 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/openstack/common/excutils.py, line 82, in __exit__ 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent six.reraise(self.type_, self.value, self.tb) 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/agent/linux/ovs_lib.py, line 67, in run_vsctl 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent return utils.execute(full_args, root_helper=self.root_helper) 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File /opt/stack/venvs/neutron/local/lib/python2.7/site-packages/neutron/agent/linux/utils.py, line 76, in execute 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent raise RuntimeError(m) 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent RuntimeError: 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=10', 'list-ports', 'br-int'] 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Exit code: 1 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Stdout: '' 2014-03-22 02:38:53.693 7916 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent
[Yahoo-eng-team] [Bug 1155092] Re: Namespace doesn't get deleted on vip/pool removal
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1155092 Title: Namespace doesn't get deleted on vip/pool removal Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Steps to reproduce (in Horizon): 1. Create one pool. 2. Create vip for it. 3. Create another pool. 4. Create vip for it. 5. Delete one vip. 6. Delete another vip. 7. Delete two pools at once. 8. Check qlbaas- namespaces. One namespace of corresponding pool doesn't get deleted and is unusable because of cleared permissions in /var/run/netns/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1155092/+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 1382064] Re: Failure to allocate tunnel id when creating networks concurrently
** Changed in: neutron
Status: Fix Committed = Fix Released
** Changed in: neutron
Milestone: None = kilo-2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1382064
Title:
Failure to allocate tunnel id when creating networks concurrently
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
When multiple networks are created concurrently, the following trace
is observed:
WARNING neutron.plugins.ml2.drivers.helpers
[req-34103ce8-b6d0-459b-9707-a24e369cf9de None] Allocate gre segment from pool
failed after 10 failed attempts
DEBUG neutron.context [req-2995f877-e3e6-4b32-bdae-da6295e492a1 None]
Arguments dropped when creating context: {u'project_name': None, u'tenant':
None} __init__ /usr/lib/python2.7/dist-packages/neutron/context.py:83
DEBUG neutron.plugins.ml2.drivers.helpers
[req-3541998d-44df-468f-b65b-36504e893dfb None] Allocate gre segment from pool,
attempt 1 failed with segment {'gre_id': 300L}
allocate_partially_specified_segment
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/helpers.py:138
DEBUG neutron.context [req-6dcfb91d-2c5b-4e4f-9d81-55ba381ad232 None]
Arguments dropped when creating context: {u'project_name': None, u'tenant':
None} __init__ /usr/lib/python2.7/dist-packages/neutron/context.py:83
ERROR neutron.api.v2.resource [req-34103ce8-b6d0-459b-9707-a24e369cf9de None]
create failed
TRACE neutron.api.v2.resource Traceback (most recent call last):
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py, line 87, in
resource
TRACE neutron.api.v2.resource result = method(request=request, **args)
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py, line 448, in create
TRACE neutron.api.v2.resource obj = obj_creator(request.context, **kwargs)
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/plugin.py, line 497, in
create_network
TRACE neutron.api.v2.resource tenant_id)
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py, line 160,
in create_network_segments
TRACE neutron.api.v2.resource segment = self.allocate_tenant_segment(session)
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py, line 189,
in allocate_tenant_segment
TRACE neutron.api.v2.resource segment =
driver.obj.allocate_tenant_segment(session)
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/type_tunnel.py,
line 115, in allocate_tenant_segment
TRACE neutron.api.v2.resource alloc =
self.allocate_partially_specified_segment(session)
TRACE neutron.api.v2.resource File
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/helpers.py, line
143, in allocate_partially_specified_segment
TRACE neutron.api.v2.resource raise
exc.NoNetworkFoundInMaximumAllowedAttempts()
TRACE neutron.api.v2.resource NoNetworkFoundInMaximumAllowedAttempts: Unable
to create the network. No available network found in maximum allowed attempts.
TRACE neutron.api.v2.resource
Additional conditions: multiserver deployment and mysql.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1382064/+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 1367039] Re: dvr fips state variables not initialized correctly across restart
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1367039 Title: dvr fips state variables not initialized correctly across restart Status in OpenStack Neutron (virtual network service): Fix Released Bug description: When the l3-agent is restarted, the local variables self.agent_fip_count and ri.dist_fip_count are not properly initialized. Current namespaces and fips are not counted so the variables are initialized to 0. This will result in unwanted behavior like stale or duplicate fg ports or fip namespaces. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1367039/+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 1361540] Re: no mechanism driver calls for gateway port removal
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1361540 Title: no mechanism driver calls for gateway port removal Status in OpenStack Neutron (virtual network service): Fix Released Bug description: MechanismDriver.delete_port_* (gateway port) are not called when the router is being removed. For instance, it remains the network:router_gateway ports in OpenDaylight as its Mechanism Driver is not correctly called. To reproduce it: - create a router and set the gateway - delete this router (without clearing the gateway) It works well if the gateway port is cleared before the router. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1361540/+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 1345947] Re: DHCPNAK after neutron-dhcp-agent restart
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1345947 Title: DHCPNAK after neutron-dhcp-agent restart Status in Grenade - OpenStack upgrade testing: In Progress Status in OpenStack Neutron (virtual network service): Fix Released Bug description: After rolling out a configuration change, we restarted neutron-dhcp-agent service, and then dnsmasq logs start flooding: DHCPNAK ... lease not found. DHCPNAK is replied by dnsmasq for all DHCPREQUEST renews from all VMs. However the MAC and IP pairs exist in host files. The log flooding increases when more and more VMs start renewing and they keep retrying until IP expire and send DHCPDISCOVER and reinit the IP. The log flooding gradually disappears when the VMs IP expire and send DHCPDISCOVER, to which dnsmasq respond DHCPOFFER properly. Analysis: I noticed that option --leasefile-ro is used in dnsmasq command when started by neutron dhcp-agent. According to dnsmasq manual, this option should be used together with --dhcp-script to customize the lease database. However, the option --dhcp-script was removed when fixing bug 1202392. Because of this, dnsmasq will not save lease information in persistent storage, and when it is restarted, lease information is lost. Solution: Simply replace --leasefile-ro by --dhcp-leasefile=path to dhcp runtime files/lease would solve the problem. (patch attached) To manage notifications about this bug go to: https://bugs.launchpad.net/grenade/+bug/1345947/+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 1193861] Re: ML2 plugin needs to override bulk operations
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1193861 Title: ML2 plugin needs to override bulk operations Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Bulk operations on the ML2 plugin will simply call each action sequentially within one transaction. This means that errors raised by a mechanism driver in a _postcommit action will cause all transactions to be undone. The ML2 plugin should override these bulk operations to: * make all pretransaction commit calls (ie call the appropriate _precommit methods on all registered mechansim drivers) * commit the transaction * make all post-transaction commit calls (ie call the appropriate _postcommit methods on all registered mechanism drivers) If an error occurs after committing the transaction, we'll need to decide how to appropriately undo the operations that have been taken so far. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1193861/+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 1377710] Re: ML2 port binding failure logging too subtle
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1377710 Title: ML2 port binding failure logging too subtle Status in OpenStack Neutron (virtual network service): Fix Released Bug description: When manually switching over segmentation method (IE: VXLAN to VLANs), any misconfiguration of the bridge mappings on a hypervisor will result in ML2 port binding failure on that host. The only log message that appears is a warning. I think that it should be raised to an error, and the port binding failure itself via agent based mechanism drivers should say exactly what's wrong. What is the network's physical network, and what physical networks the agent reported. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1377710/+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 1376325] Re: Cannot enable DVR and IPv6 simultaneously
** Changed in: neutron
Status: Fix Committed = Fix Released
** Changed in: neutron
Milestone: None = kilo-2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1376325
Title:
Cannot enable DVR and IPv6 simultaneously
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
While testing out the devstack change to support IPv6,
https://review.openstack.org/#/c/87987/ I tripped-over a DVR error
since I have it enabled by default in local.conf.
I have these two things enabled in local.conf:
Q_DVR_MODE=dvr_snat
IP_VERSION=4+6
After locally fixing lib/neutron to teach it about the DVR snat-
namespace (another bug to be filed for that), stack.sh was able to
complete, but the l3-agent wasn't very happy:
Stderr: '' execute /opt/stack/neutron/neutron/agent/linux/utils.py:81
2014-09-30 12:53:47.511 21778 DEBUG neutron.agent.linux.utils [-] Running
command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec',
'qrouter-95b180a4-9623-4ef9-adda-772ca0838253', 'ip', 'rule', 'add', 'from',
'fd00::1/64', 'lookup', '336294682933583715844663186250927177729', 'priority',
'336294682933583715844663186250927177729'] create_process
/opt/stack/neutron/neutron/agent/linux/utils.py:46
2014-09-30 12:53:47.641 21778 ERROR neutron.agent.linux.utils [-]
Command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec',
'qrouter-95b180a4-9623-4ef9-adda-772ca0838253', 'arping', '-A', '-I',
'qr-3d0eda6e-54', '-c', '3', 'fd00::1']
Exit code: 2
Stdout: ''
Stderr: 'arping: unknown host fd00::1\n'
2014-09-30 12:53:47.643 21778 ERROR neutron.agent.l3_agent [-] Failed sending
gratuitous ARP:
Command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec',
'qrouter-95b180a4-9623-4ef9-adda-772ca0838253', 'arping', '-A', '-I',
'qr-3d0eda6e-54', '-c', '3', 'fd00::1']
Exit code: 2
Stdout: ''
Stderr: 'arping: unknown host fd00::1\n'
2014-09-30 12:53:48.682 21778 ERROR neutron.agent.linux.utils [-]
Command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec',
'qrouter-95b180a4-9623-4ef9-adda-772ca0838253', 'ip', 'rule', 'add', 'from',
'fd00::1/64', 'lookup', '336294682933583715844663186250927177729', 'priority',
'336294682933583715844663186250927177729']
Exit code: 255
Stdout: ''
Stderr: 'Error: argument 336294682933583715844663186250927177729 is wrong:
preference value is invalid\n\n'
2014-09-30 12:53:48.683 21778 ERROR neutron.agent.l3_agent [-] DVR: error
adding redirection logic
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent Traceback (most
recent call last):
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent File
/opt/stack/neutron/neutron/agent/l3_agent.py, line 1443, in _snat_redirect_add
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent
ns_ipr.add_rule_from(sn_port['ip_cidr'], snat_idx, snat_idx)
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent File
/opt/stack/neutron/neutron/agent/linux/ip_lib.py, line 202, in add_rule_from
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent ip =
self._as_root('', 'rule', tuple(args))
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent File
/opt/stack/neutron/neutron/agent/linux/ip_lib.py, line 74, in _as_root
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent
log_fail_as_error=self.log_fail_as_error)
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent File
/opt/stack/neutron/neutron/agent/linux/ip_lib.py, line 86, in _execute
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent
log_fail_as_error=log_fail_as_error)
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent File
/opt/stack/neutron/neutron/agent/linux/utils.py, line 84, in execute
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent raise
RuntimeError(m)
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent RuntimeError:
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent Command: ['sudo',
'/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns',
'exec', 'qrouter-95b180a4-9623-4ef9-adda-772ca0838253', 'ip', 'rule', 'add',
'from', 'fd00::1/64', 'lookup', '336294682933583715844663186250927177729',
'priority', '336294682933583715844663186250927177729']
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent Exit code: 255
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent Stdout: ''
2014-09-30 12:53:48.683 21778 TRACE neutron.agent.l3_agent Stderr: 'Error:
argument 336294682933583715844663186250927177729 is wrong: preference value
is invalid\n\n'
Ignore the ARP failures, there's already an upstream patch proposed
for that.
The fix for now might just
[Yahoo-eng-team] [Bug 1411016] Re: Unblock config restrictions in Arista L3 Service Plugin
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411016 Title: Unblock config restrictions in Arista L3 Service Plugin Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Arista L3 Service Plugin blocks configuring MLAG (High Availability) in a VRF mode. This should not be blocked as this is now a supported feature in Arista HW. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411016/+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 1407024] Re: pep8 H302 failing on stable/juno with latest hacking
** Changed in: nova/juno 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/1407024 Title: pep8 H302 failing on stable/juno with latest hacking Status in OpenStack Compute (Nova): Fix Committed Status in OpenStack Compute (nova) juno series: Fix Released Bug description: mriedem@ubuntu:~/git/nova$ tox -r -e pep8 pep8 recreate: /home/mriedem/git/nova/.tox/pep8 pep8 installdeps: -r/home/mriedem/git/nova/requirements.txt, -r/home/mriedem/git/nova/test-requirements.txt pep8 develop-inst: /home/mriedem/git/nova pep8 runtests: PYTHONHASHSEED='0' pep8 runtests: commands[0] | flake8 ./nova/tests/compute/test_resources.py:30:1: H302 import only modules.'from nova.tests.fake_instance import fake_instance_obj' does not import a module ./nova/tests/compute/test_rpcapi.py:31:1: H302 import only modules.'from nova.tests.fake_instance import fake_instance_obj' does not import a module ERROR: InvocationError: '/home/mriedem/git/nova/.tox/pep8/bin/flake8' ___ summary ___ ERROR: pep8: commands failed I'm not sure what changed, I'm assuming a new version of hacking was released that hits problems in stable/juno. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1407024/+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 1404115] Re: can't copy 'neutron/tests/functional/contrib'
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1404115 Title: can't copy 'neutron/tests/functional/contrib' Status in OpenStack Neutron (virtual network service): Fix Released Status in Taskflow for task-oriented systems.: Fix Released Status in tripleo - openstack on openstack: Fix Released Bug description: This appeared in CI while installing neutron http://logs.openstack.org/17/139217/10/check-tripleo/check-tripleo-ironic-undercloud-precise-nonha/3974020/console.html 2014-12-19 03:48:18.034 | 2014-12-19 03:48:18.034 | creating build/lib.linux-x86_64-2.7/neutron/plugins/cisco/l3/configdrive_templates 2014-12-19 03:48:18.034 | 2014-12-19 03:48:18.034 | copying neutron/plugins/cisco/l3/configdrive_templates/csr1kv_cfg_template - build/lib.linux-x86_64-2.7/neutron/plugins/cisco/l3/configdrive_templates 2014-12-19 03:48:18.034 | 2014-12-19 03:48:18.034 | copying neutron/plugins/ml2/drivers/arista/README - build/lib.linux-x86_64-2.7/neutron/plugins/ml2/drivers/arista 2014-12-19 03:48:18.034 | 2014-12-19 03:48:18.034 | error: can't copy 'neutron/tests/functional/contrib': doesn't exist or not a regular file 2014-12-19 03:48:18.034 | 2014-12-19 03:48:18.034 | 2014-12-19 03:48:18.034 | Cleaning up... probably related to https://review.openstack.org/#/c/142558/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404115/+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 1404341] Re: Spelling error in l3_rpc_agent_api.py
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1404341 Title: Spelling error in l3_rpc_agent_api.py Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Log.debug statement in _notification_host() mis-spells Notify To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404341/+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 1404250] Re: get_binary_name should returns strings without spaces
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1404250 Title: get_binary_name should returns strings without spaces Status in OpenStack Neutron (virtual network service): Fix Released Bug description: get_binary_name() generates a string from sys.argv[0] which could contains spaces: * python -m unittest whatever implies sys.argv[0] = python -m unittest and get_binary_name == 'python -m unitte' But iptables does not support spaces in chain name ... and get_binary_name() is used as prefix in chain name by iptables_manager * python -m unittest whatever implies incorrect iptables chain definition: iptables -N python -m unittest. It typically brakes functional tests runned using python -m unittest $class. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404250/+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 1404688] Re: delete subnet from admin tenant fails for PLUMgrid Plugin
** Changed in: neutron Status: Fix Committed = Fix Released ** Changed in: neutron Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1404688 Title: delete subnet from admin tenant fails for PLUMgrid Plugin Status in OpenStack Neutron (virtual network service): Fix Released Bug description: If a non-admin tenant creates a network and a subnet and delete operation is performed by the admin tenant, PLUMgrid plugin ends up passing incorrect tenant_id to the backend and this fails the calls. Fix would be to get correct tenant UUID in delete subnet operation. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404688/+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 1404605] Re: Prevent symlinks to creep in the tree
** Changed in: neutron Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1404605 Title: Prevent symlinks to creep in the tree Status in OpenStack Neutron (virtual network service): Fix Released Bug description: This change: https://review.openstack.org/#/c/142558/ Caused a bit of grief: https://bugs.launchpad.net/neutron/+bug/1404458 https://bugs.launchpad.net/tripleo/+bug/1404115 Let's make sure it never happens again. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404605/+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 1385533] Re: Domain tokens issued from a saml2 auth incorrectly includes group roles marked as inherited
** Changed in: keystone/juno 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/1385533 Title: Domain tokens issued from a saml2 auth incorrectly includes group roles marked as inherited Status in OpenStack Identity (Keystone): Fix Released Status in Keystone juno series: Fix Released Bug description: When building the roles in a Keystone token from a saml2 token, we call assignment_api.get_roles_for_groups() to add in any group roles. This appears to ignore the inheritance flag on the assignment - and puts in all group roles whether inherited or not. This means the wrong roles can end up in the resulting Keystone token. The implication is that domain scoped tokens would incorrectly get roles that were meant to be inherited (only) to projects within that domain. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1385533/+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 1389880] Re: VM loses connectivity on floating ip association when using DVR
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1389880 Title: VM loses connectivity on floating ip association when using DVR Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: Presence: Juno 2014.2-1 RDO , ubuntu 12.04 openvswitch version on ubuntu is 2.0.2 Description: Whenever create FIP on a VM, it adds the FIP to ALL other compute nodes, a routing prefix in the FIP namespace, and IP interface alias on the qrouter. However, the iptables gets updated normally with only the DNAT for the particular IP of the VM on that compute node This causes the FIP proxy arp to answer ARP requests for ALL VM's on ALL compute nodes which results in compute nodes answering ARPs where they do not have the VM effectively blackholing traffic to that ip. Here is a demonstration of the problem: Before adding a vm+fip on compute4 [root@compute2 ~]# ip netns exec fip-616a6213-c339-4164-9dff-344ae9e04929 ip route show default via 173.209.44.1 dev fg-6ede0596-3a 169.254.31.28/31 dev fpr-3a90aae6-3 proto kernel scope link src 169.254.31.29 173.209.44.0/24 dev fg-6ede0596-3a proto kernel scope link src 173.209.44.6 173.209.44.4 via 169.254.31.28 dev fpr-3a90aae6-3 [root@compute3 neutron]# ip netns exec fip-616a6213-c339-4164-9dff-344ae9e04929 ip route show default via 173.209.44.1 dev fg-26bef858-6b 169.254.31.238/31 dev fpr-3a90aae6-3 proto kernel scope link src 169.254.31.239 173.209.44.0/24 dev fg-26bef858-6b proto kernel scope link src 173.209.44.5 173.209.44.3 via 169.254.31.238 dev fpr-3a90aae6-3 [root@compute4 ~]# ip netns exec fip-616a6213-c339-4164-9dff-344ae9e04929 ip route show default via 173.209.44.1 dev fg-2919b6be-f4 173.209.44.0/24 dev fg-2919b6be-f4 proto kernel scope link src 173.209.44.8 after creating a new vm on compute4 and attaching a floating IP to it, we get this result. of course at this point, only the vm on compute4 is able to ping the public network [root@compute2 ~]# ip netns exec fip-616a6213-c339-4164-9dff-344ae9e04929 ip route show default via 173.209.44.1 dev fg-6ede0596-3a 169.254.31.28/31 dev fpr-3a90aae6-3 proto kernel scope link src 169.254.31.29 173.209.44.0/24 dev fg-6ede0596-3a proto kernel scope link src 173.209.44.6 173.209.44.4 via 169.254.31.28 dev fpr-3a90aae6-3 173.209.44.7 via 169.254.31.28 dev fpr-3a90aae6-3 [root@compute3 neutron]# ip netns exec fip-616a6213-c339-4164-9dff-344ae9e04929 ip route show default via 173.209.44.1 dev fg-26bef858-6b 169.254.31.238/31 dev fpr-3a90aae6-3 proto kernel scope link src 169.254.31.239 173.209.44.0/24 dev fg-26bef858-6b proto kernel scope link src 173.209.44.5 173.209.44.3 via 169.254.31.238 dev fpr-3a90aae6-3 173.209.44.7 via 169.254.31.238 dev fpr-3a90aae6-3 [root@compute4 ~]# ip netns exec fip-616a6213-c339-4164-9dff-344ae9e04929 ip route show default via 173.209.44.1 dev fg-2919b6be-f4 169.254.30.20/31 dev fpr-3a90aae6-3 proto kernel scope link src 169.254.30.21 173.209.44.0/24 dev fg-2919b6be-f4 proto kernel scope link src 173.209.44.8 173.209.44.3 via 169.254.30.20 dev fpr-3a90aae6-3 173.209.44.4 via 169.254.30.20 dev fpr-3a90aae6-3 173.209.44.7 via 169.254.30.20 dev fpr-3a90aae6-3 **when we deleted the extra FIP from each Compute Nodes Namespace, everything starts to work just fine** Following are the router, floating IP information and config files : +---+--+ | Field | Value | +---+--+ | admin_state_up| True | | distributed | True | | external_gateway_info
[Yahoo-eng-team] [Bug 1381238] Re: Race condition on processing DVR floating IPs
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1381238 Title: Race condition on processing DVR floating IPs Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: A race condition can sometimes occur in l-3 agent when a dvr based floatingip is being deleted from one router and another dvr based floatingip is being configured on another router in the same node. Especially if the floatingip being deleted was the last floatingip on the node. Although fix for Bug # 1373100 [1] eliminated frequent observation of this behavior in upstream tests, it still shows up. Couple of recent examples: http://logs.openstack.org/88/128288/1/check/check-tempest-dsvm- neutron-dvr/8fdd1de/ http://logs.openstack.org/03/123403/7/check/check-tempest-dsvm- neutron-dvr/859534a/ Relevant log messages: 2014-10-14 16:06:15.803 22303 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-82fb2751-30ba-4015-a5da-6c8563064db9', 'ip', 'link', 'del', 'fpr-7ed86ca6-b'] create_process /opt/stack/new/neutron/neutron/agent/linux/utils.py:46 2014-10-14 16:06:15.838 22303 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-7ed86ca6-b42d-4ba9-8899-447ff0509174', 'ip', 'addr', 'show', 'rfp-7ed86ca6-b'] Exit code: 0 Stdout: '2: rfp-7ed86ca6-b: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000\nlink/ether c6:88:ee:71:a7:51 brd ff:ff:ff:ff:ff:ff\ninet 169.254.30.212/31 scope global rfp-7ed86ca6-b\n valid_lft forever preferred_lft forever\ninet6 fe80::c488:eeff:fe71:a751/64 scope link \n valid_lft forever preferred_lft forever\n' Stderr: '' execute /opt/stack/new/neutron/neutron/agent/linux/utils.py:81 2014-10-14 16:06:15.839 22303 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-7ed86ca6-b42d-4ba9-8899-447ff0509174', 'ip', '-4', 'addr', 'add', '172.24.4.91/32', 'brd', '172.24.4.91', 'scope', 'global', 'dev', 'rfp-7ed86ca6-b'] create_process /opt/stack/new/neutron/neutron/agent/linux/utils.py:46 2014-10-14 16:06:16.221 22303 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'fip-82fb2751-30ba-4015-a5da-6c8563064db9', 'ip', 'link', 'del', 'fpr-7ed86ca6-b'] Exit code: 0 Stdout: '' Stderr: '' execute /opt/stack/new/neutron/neutron/agent/linux/utils.py:81 2014-10-14 16:06:16.222 22303 DEBUG neutron.agent.l3_agent [-] DVR: unplug: fg-f04e25ef-e3 _destroy_fip_namespace /opt/stack/new/neutron/neutron/agent/l3_agent.py:679 2014-10-14 16:06:16.222 22303 DEBUG neutron.agent.linux.utils [-] Running command: ['ip', '-o', 'link', 'show', 'br-ex'] create_process /opt/stack/new/neutron/neutron/agent/linux/utils.py:46 2014-10-14 16:06:16.251 22303 ERROR neutron.agent.linux.utils [-] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-7ed86ca6-b42d-4ba9-8899-447ff0509174', 'ip', '-4', 'addr', 'add', '172.24.4.91/32', 'brd', '172.24.4.91', 'scope', 'global', 'dev', 'rfp-7ed86ca6-b'] Exit code: 1 Stdout: '' Stderr: 'Cannot find device rfp-7ed86ca6-b\n' [1] https://bugs.launchpad.net/neutron/+bug/1373100 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1381238/+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 1377307] Re: Metadata host route added when DVR and isolated metadata enabled
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1377307 Title: Metadata host route added when DVR and isolated metadata enabled Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: When DVR is enabled and enable_isolated_metadata=True in dhcp_agent.ini, the agent should only inject a metadata host route when there is no gateway on the subnet. But it does it all the time: $ ip r default via 10.0.0.1 dev eth0 10.0.0.0/24 dev eth0 src 10.0.0.5 169.254.169.254 via 10.0.0.4 dev eth0 The opts file for dnsmasq confirms it was the Neutron code that configured this. The code in neutron/agent/linux/dhcp.py:get_isolated_subnets() is only looking at ports where the device_owner field is DEVICE_OWNER_ROUTER_INTF, it also needs to look for DEVICE_OWNER_DVR_INTERFACE. Simlar changes have been made in other code. Making that simple change fixes the problem: $ ip r default via 10.0.0.1 dev eth0 10.0.0.0/24 dev eth0 src 10.0.0.5 I have a patch I'll get out for this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1377307/+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 1377156] Re: fg- device is not deleted after the deletion of the last VM on the compute node
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1377156 Title: fg- device is not deleted after the deletion of the last VM on the compute node Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: The external gateway port in the fip- namespace on a compute node is not removed after the user deleted the last VM running on the node. How to reproduce the problem: 1. SETUP: Â * Use devstack to start up the controller node. In local.conf, Q_DVR_MODE=dvr_snat. Â * Use devstack to setup a compute node. In local.conf, Q_DVR_MODE=dvr. At the start, there are no VMs hosted on the compute node. The fip namespace hasn't been created yet. 1. Create a network and subnet 2. Create a router and dd the subnet to the router 3. Tie the router to the external network 4. Boot up a VM using the network, and assign it a floatingip 5. Ping the floating IP (make sure you open up your SG) 6. Note the fg- device in the fip namespace on the compute node 7. Now delete the VM Expected results: - The VM is deleted. - Neutron port-list shows the gateway port is also deleted. - The FIP namespace is also cleared Experienced results: - The fg- device still remains in the fip namespace on the compute node and the fip namespace isn't removed. For detailed command sequence, see: http://paste.openstack.org/show/118174/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1377156/+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 1333144] Re: Jenkins fails patch verification on: ConnectionError: HTTPConnectionPool(host='public.nova.example.com', port=8774): Max retries exceeded
** Changed in: horizon
Status: Fix Committed = Fix Released
** Changed in: horizon
Milestone: None = kilo-2
--
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/1333144
Title:
Jenkins fails patch verification on: ConnectionError:
HTTPConnectionPool(host='public.nova.example.com', port=8774): Max
retries exceeded
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in OpenStack Dashboard (Horizon) havana series:
Invalid
Status in OpenStack Dashboard (Horizon) icehouse series:
Fix Released
Bug description:
Jenkins fails on three tests:
==
gate-horizon-python26
gate-horizon-python27
gate-horizon-python27-django14
The error that repeats in the log files is:
14-06-22 20:18:42.483 | ERROR:
test_change_password_shows_message_on_login_page
(openstack_dashboard.dashboards.settings.password.tests.ChangePasswordTests)
| --
 Traceback (most recent call last):
   File
/home/jenkins/workspace/gate-horizon-python27/openstack_dashboard/test/helpers.py,
line 81, in instance_stub_out
return fn(self, *args, **kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/openstack_dashboard/dashboards/settings/password/tests.py,
line 65, in test_change_password_shows_message_on_login_page
res = self.client.post(INDEX_URL, formData, follow=True)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/test/client.py,
line 485, in post
response = self._handle_redirects(response, **extra)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/test/client.py,
line 617, in _handle_redirects
 response = self.get(url.path, QueryDict(url.query), follow=False,
**extra)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/test/client.py,
line 473, in get
response = super(Client, self).get(path, data=data, **extra)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/test/client.py,
line 280, in get
return self.request(**r)
  File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/test/client.py,
line 444, in request
 six.reraise(*exc_info)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/core/handlers/base.py,
line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/decorators.py, line 36,
in dec
return view_func(request, *args, **kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/decorators.py, line 52,
in dec
 return view_func(request, *args, **kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/decorators.py, line 36,
in dec
 return view_func(request, *args, **kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/views/generic/base.py,
line 69, in view
 return self.dispatch(request, *args, **kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/.tox/py27/local/lib/python2.7/site-packages/django/views/generic/base.py,
line 87, in dispatch
return handler(request, *args, **kwargs)
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/tables/views.py, line
152, in get
 handled = self.construct_tables()
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/tables/views.py, line
143, in construct_tables
 handled = self.handle_table(table)
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/tables/views.py, line
116, in handle_table
 data = self._get_data_dict()
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/tables/views.py, line
179, in _get_data_dict
 self._data = {self.table_class._meta.name: self.get_data()}
   File
/home/jenkins/workspace/gate-horizon-python27/openstack_dashboard/dashboards/project/overview/views.py,
line 55, in get_data
 super(ProjectOverview, self).get_data()
   File
/home/jenkins/workspace/gate-horizon-python27/openstack_dashboard/usage/views.py,
line 43, in get_data
 self.usage.summarize(*self.usage.get_date_range())
   File
/home/jenkins/workspace/gate-horizon-python27/openstack_dashboard/usage/base.py,
line 195, in summarize
 if not api.nova.extension_supported('SimpleTenantUsage', self.request):
   File
/home/jenkins/workspace/gate-horizon-python27/horizon/utils/memoized.py, line
90, in wrapped
 value = cache[key] = func(*args, **kwargs)
   File
[Yahoo-eng-team] [Bug 1307476] Re: contextual-markers under-usage leads to babble looking translations
** 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/1307476 Title: contextual-markers under-usage leads to babble looking translations Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Contextual markers: https://docs.djangoproject.com/en/dev/topics/i18n/translation/#contextual-markers are used only in horizon.tables.actions.BatchAction._get_action_name in the whole code, and even there, the translation lacks of context. Indeed, we have:: if action_type == past: msgstr = pgettext_lazy(past, %(action)s %(data_type)s) else: msgstr = pgettext_lazy(present, %(action)s %(data_type)s) But %(action)s and %(data_type)s use action and data_types are already translations coming from a context agnostic translation. This leads to buttons in French like Redémarrage à Chaud Instances (which is incorrect and should be Redémarrage à chaud des instances) and Terminer Instances (which should be Terminer les instances) (both the missing les (plural) and l' (singular) and the Camel-Case in the sentence, looks more like babbling rather than speaking in French, but I'm sure many other languages are impacted). Currently The translators can do nothing about it and can not be blamed at all, simply because because the context is not handled, so they have to make a compromise of the less babbling looking translation. So BatchAction sublcasses should also use contextual-markers for their action_* and data_type_* attributes, because even there, translations are correct in a context, and wrong in an other (depending where it will be rendered) since Instance needs to be translated either Instance or L'instance depending on the context (and only Proper nouns have a capital letter inside a sentence in many languages like French so L'instance will also have to be l'instance, etc...). Many Translation errors are due to lack of contextual-markers in the translatable strings. We should therefore add more contextual-markers in the translation strings and handle words which will be isolated or inside a sentence (for the capital letter on non-Nouns). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1307476/+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 1374461] Re: potential lock wait timeout issue when creating a HA router
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1374461 Title: potential lock wait timeout issue when creating a HA router Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: Currently the failures during the creation of resources related to the creation of a HA router are handled my a try/except to avoid a potential lock wait timeout. This has been done in order to keep the RPC calls outside the transactions. All the related resources are created in the _create_router_db but this method is called inside a transaction which is started is the create_router method. Moreover the try/except mechanism used to rollback the router creation will not work since we are in a already opened transaction. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1374461/+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 1372883] Re: DHCP agent should specify prefix-len for IPv6 dhcp-range's
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1372883 Title: DHCP agent should specify prefix-len for IPv6 dhcp-range's Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: If Network contains Subnet smaller than /64, prefix-len should be specified for dnsmasq's --dhcp-range option. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1372883/+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 1415418] Re: Support OVA in images
** 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/1415418 Title: Support OVA in images Status in OpenStack Dashboard (Horizon): Fix Released Bug description: OVA is the abbreviation for Open Virtualization Archive, the single-file version of an Open Virtualization Format image We should support that. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1415418/+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 1417808] Re: Fix extra indention in firewall views.py code
** 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/1417808
Title:
Fix extra indention in firewall views.py code
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
It is not obvious in here, but there are 8 spaces instead of 4 space
in the indent of the code inside the method
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/firewalls/views.py#L175
@memoized.memoized_method
def _get_object(self, *args, **kwargs):
policy_id = self.kwargs['policy_id']
try:
policy = api.fwaas.policy_get(self.request, policy_id)
return policy
except Exception:
redirect = self.success_url
msg = _('Unable to retrieve policy details.')
exceptions.handle(self.request, msg, redirect=redirect)
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1417808/+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 1413550] Re: filter option is missing for network and router tables
** 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/1413550 Title: filter option is missing for network and router tables Status in OpenStack Dashboard (Horizon): Fix Released Bug description: no client side filter for network and router tables on both admin and project. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1413550/+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 1417419] Re: In hypervisors page of tabs compute host when enable sevice the message appear N/A
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1417419 Title: In hypervisors page of tabs compute host when enable sevice the message appear N/A Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In the hypervisors page, when switch to compute host tab, disable the host service, and then enable the service, the message appear N/A To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1417419/+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 1416583] Re: Policy check is missing outer parens
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1416583 Title: Policy check is missing outer parens Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The policy check call seems to be missing another set of parens and a comma resulting in incorrect parsing of the action in the policy.py https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/keystone.py#L147 user = request.user if admin: if not policy.check((identity, admin_required), request): raise exceptions.NotAuthorized endpoint_type = 'adminURL' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416583/+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 1410524] Re: Unused method get_stats in dashboards.info.tables
** 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/1410524 Title: Unused method get_stats in dashboards.info.tables Status in OpenStack Dashboard (Horizon): Fix Released Bug description: It looks like the method get_stats in dashboards.info.tables is not used anywhere in Horizon. The referenced file _stats.html is also not available in the Horizon repository. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1410524/+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 1413068] Re: Edit current project will disable it
** 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/1413068 Title: Edit current project will disable it Status in OpenStack Dashboard (Horizon): Fix Released Bug description: If you edit current project in horizon, the current project will be disabled. Reproduce process: 1. Log into horizon. 2. Click project panel under identity dashboard. 3. Edit the current project, then click update 4. Meet errors, the project has been disabled after re-log in Root Cause: 1. The enabled checkbox in project info step is disabled when user try to edit current project. 2. All the disabled checkbox will be regarded as False when user post the form data. 3. So that, it will disable the current project when try to edit it. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1413068/+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 1413266] Re: Incorrect sorting in section Images
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1413266 Title: Incorrect sorting in section Images Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) juno series: Fix Committed Bug description: Environment: devstack Steps to reproduce: 1. Open Openstack Dashboard 2. Click on Images 3. Click on Size Expected result: correct sorting Actual result: incorrect sorting (attach screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1413266/+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 1410173] Re: Horizon should support subnet update of allocation-pool
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1410173 Title: Horizon should support subnet update of allocation-pool Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The subnet update of allocation-pool not available via Horizon Please see following RFE: https://bugs.launchpad.net/neutron/+bug/572 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1410173/+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 1415775] Re: there is no ram hours in admin overview 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/1415775 Title: there is no ram hours in admin overview page Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In the admin overview page, there has cpu-hours, disk-hours, but has no ram-hours. I think it also need. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1415775/+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 1413480] Re: Incorrect volume snapshot mocking in quota tests
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1413480 Title: Incorrect volume snapshot mocking in quota tests Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In openstack_dashboard/test/tests/quotas.py we're using self.snapshots as the return value for volume_snapshot_list, which is a list of Glance snapshots. It should be self.cinder_volume_snapshots. cinder.volume_snapshot_list(IsA(http.HttpRequest), opts).AndReturn(self.snapshots.list()) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1413480/+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 1416248] Re: 403 page displays trans template tag
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1416248 Title: 403 page displays trans template tag Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When the 403 page is displayed, the trans template tag is not evaluated and instead is displayed with the HTML. Instead, this should be evaluated as part of the template and not displayed to the user. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1416248/+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 1413783] Re: sidebar dropdown obsolete css
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1413783 Title: sidebar dropdown obsolete css Status in OpenStack Dashboard (Horizon): Fix Released Bug description: There is dead in horizon.scss around the project picker. The picker was relocated long ago, this css is no longer used and should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1413783/+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 1418568] Re: depends on cloud-utils without knowledge of cloud-image-utils
This was found in bug 1407699. * on precise juju uses the cloud tools archive (https://wiki.ubuntu.com/ServerTeam/CloudToolsArchive) * precise's version of cloud-init depends on cloud-utils * Juju began installing cloud-image-utils. * cloud-image-utils conflicts with cloud-utils. cloud-image-utils was just a re-packaging for dependency shrink and so it conflicts with older versions of cloud-utils which would include the same set of files. To reproduce, launch precise instance: $ sudo apt-add-repository -y cloud-archive:tools $ sudo apt-get update -qy $ apt-get install --dry-run -q cloud-image-utils NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: distro-info distro-info-data genisoimage libaio1 libnspr4 libnss3 librados2 librbd1 python-distro-info qemu-utils Suggested packages: shunit2 wodim cdrkit-doc The following packages will be REMOVED: cloud-init cloud-initramfs-growroot cloud-utils The following NEW packages will be installed: cloud-image-utils distro-info distro-info-data genisoimage libaio1 libnspr4 libnss3 librados2 librbd1 python-distro-info qemu-utils 0 upgraded, 11 newly installed, 3 to remove and 9 not upgraded. Remv cloud-init [0.6.3-0ubuntu1.15] Remv cloud-initramfs-growroot [0.4ubuntu1] Remv cloud-utils [0.25-0ubuntu5.1] Inst libaio1 (0.3.109-2ubuntu1 Ubuntu:12.04/precise [amd64]) Inst libnspr4 (4.10.7-0ubuntu0.12.04.1 Ubuntu:12.04/precise-updates [amd64]) Inst libnss3 (3.17.1-0ubuntu0.12.04.2 Ubuntu:12.04/precise-updates [amd64]) Inst distro-info-data (0.8ubuntu0.7 Ubuntu:12.04/precise-updates [all]) Inst distro-info (0.8.2 Ubuntu:12.04/precise [amd64]) Inst genisoimage (9:1.1.11-2ubuntu2 Ubuntu:12.04/precise [amd64]) Inst librados2 (0.41-1ubuntu2.1 Ubuntu:12.04/precise-updates [amd64]) Inst librbd1 (0.41-1ubuntu2.1 Ubuntu:12.04/precise-updates [amd64]) Inst python-distro-info (0.8.2 Ubuntu:12.04/precise [all]) Inst qemu-utils (1.0+noroms-0ubuntu14.21 Ubuntu:12.04/precise-updates [amd64]) Inst cloud-image-utils (0.27-0ubuntu9~ctools0 precise-updates [all]) Conf libaio1 (0.3.109-2ubuntu1 Ubuntu:12.04/precise [amd64]) Conf libnspr4 (4.10.7-0ubuntu0.12.04.1 Ubuntu:12.04/precise-updates [amd64]) Conf libnss3 (3.17.1-0ubuntu0.12.04.2 Ubuntu:12.04/precise-updates [amd64]) Conf distro-info-data (0.8ubuntu0.7 Ubuntu:12.04/precise-updates [all]) Conf distro-info (0.8.2 Ubuntu:12.04/precise [amd64]) Conf genisoimage (9:1.1.11-2ubuntu2 Ubuntu:12.04/precise [amd64]) Conf librados2 (0.41-1ubuntu2.1 Ubuntu:12.04/precise-updates [amd64]) Conf librbd1 (0.41-1ubuntu2.1 Ubuntu:12.04/precise-updates [amd64]) Conf python-distro-info (0.8.2 Ubuntu:12.04/precise [all]) Conf qemu-utils (1.0+noroms-0ubuntu14.21 Ubuntu:12.04/precise-updates [amd64]) Conf cloud-image-utils (0.27-0ubuntu9~ctools0 precise-updates [all]) ** Also affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-initramfs-tools (Ubuntu) Status: New = Fix Released ** Changed in: cloud-initramfs-tools (Ubuntu Precise) Status: New = Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: cloud-initramfs-tools (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1418568 Title: depends on cloud-utils without knowledge of cloud-image-utils Status in Init scripts for use on cloud images: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in cloud-init source package in Precise: Confirmed Status in cloud-initramfs-tools source package in Precise: Confirmed Bug description: As per https://bugs.launchpad.net/juju-core/+bug/1407699/comments/4, cloud-images-utils cannot be installed on precise. This is blocking the release of Juju 1.22, as that needs to have cloud-images-utils available, and tries to apt-get install it during cloud init, but the apt install doesn't go ahead due to the above problem. As per the above comment: smoser we can fix that with a packaging change to cloud-init in precise. smoser to depend on cloud-image-utils | cloud-utils Could we please get that packaging change done and the new cloud-init apckage propagated to the archives? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1418568/+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 :
[Yahoo-eng-team] [Bug 1417264] Re: [data processing] The job page references a non-existing template
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1417264 Title: [data processing] The job page references a non-existing template Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The job page is currently referencing project/data_processing.job_binaries/job_binaries_form_script.html, which no longer exists. This needs to be fixed by removing the reference, which is no longer needed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1417264/+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 1409892] Re: docs don't provide all FilterAction attributes
** 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/1409892 Title: docs don't provide all FilterAction attributes Status in OpenStack Dashboard (Horizon): Fix Released Bug description: http://docs.openstack.org/developer/horizon/ref/tables.html#horizon.tables.FilterAction vs https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L407 Also FixedFilterAction (https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L523) is missing from the docs too. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1409892/+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 1410129] Re: null append to primary project dropdown list when a project is created in the create_user_form
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1410129 Title: null append to primary project dropdown list when a project is created in the create_user_form Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Testing step in latest horizon upstream: 1: login as admin 2: create a user then create a new project in this form 3: null append to project list To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1410129/+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 1408297] Re: DHCP agent fails to match IPv6 clients when used with dnsmasq 2.67
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1408297 Title: DHCP agent fails to match IPv6 clients when used with dnsmasq 2.67 Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: DHCP agent fails to match IPv6 clients when used with dnsmasq 2.67. This is because MAC address matching support for IPv6 was added in 2.67 only. We should bump minimal dnsmasq version in DHCP agent. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1408297/+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 1409487] Re: Clarify description in instance Create Snapshot dialog
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1409487 Title: Clarify description in instance Create Snapshot dialog Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The Create Snapshot button under the Actions column in Instances actually creates in image, which is somewhat confusing. The description that appears in the dialog should clarify that it is actually creating an image. The wording from the operator manual [1] is a good starting point. [1] http://docs.openstack.org/openstack-ops/content/snapshots.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1409487/+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 1409184] Re: replace bootstrap icon description with font-awesome in docs
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1409184 Title: replace bootstrap icon description with font-awesome in docs Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Thanks Julie! https://review.openstack.org/#/c/120237/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1409184/+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 1412749] Re: Lack of warning when JavaScript is disabled
** Changed in: horizon
Status: Fix Committed = Fix Released
** Changed in: horizon
Milestone: None = kilo-2
--
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/1412749
Title:
Lack of warning when JavaScript is disabled
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Steps to reproduce:
1) Disable JavaScript in browser settings.
2) Navigate to Horizon.
3) Login to Horizon Dashboard.
Actual: Horizon Dashboard looks usually, but performs malfunction of
most Horizon capabilities.
Expected: to see some warning to enable JavaScript.
Environment:
{build_id: 2014-12-26_14-25-46, ostf_sha:
a9afb68710d809570460c29d6c3293219d3624d4, build_number: 58,
auth_required: true, api: 1.0, nailgun_sha:
5f91157daa6798ff522ca9f6d34e7e135f150a90, production: docker,
fuelmain_sha: 81d38d6f2903b5a8b4bee79ca45a54b76c1361b8, astute_sha:
16b252d93be6aaa73030b8100cf8c5ca6a970a91, feature_groups: [mirantis],
release: 6.0, release_versions: {2014.2-6.0: {VERSION: {build_id:
2014-12-26_14-25-46, ostf_sha: a9afb68710d809570460c29d6c3293219d3624d4,
build_number: 58, api: 1.0, nailgun_sha:
5f91157daa6798ff522ca9f6d34e7e135f150a90, production: docker,
fuelmain_sha: 81d38d6f2903b5a8b4bee79ca45a54b76c1361b8, astute_sha:
16b252d93be6aaa73030b8100cf8c5ca6a970a91, feature_groups: [mirantis],
release: 6.0, fuellib_sha: fde8ba5e11a1acaf819d402c645c731af450aff0}}},
fuellib_sha: fde8ba5e11a1acaf819d402c645c731af450aff0}
Browsers:
Chrome: Version 39.0.2171.99 (64-bit) on Ubuntu 14.04
Firefox: 35.0 on Ubuntu 14.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1412749/+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 1409420] Re: Addition of x-static smart-table cause UncompressableFileError
** 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/1409420
Title:
Addition of x-static smart-table cause UncompressableFileError
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
How to reproduce
1. `git pull` and we will get the latest horizon
2. `pip install -r requirements.txt` to install required packages
3. login the horizon, it will raise UncompressableFileError, just like the
below screenshot
the bug is introduced by the commit
d7df6378a356d19c190440e6446919a58dc7809b
https://github.com/openstack/horizon/commit/d7df6378a356d19c190440e6446919a58dc7809b
the smart-table.js path is not correct.
the xstatic smart-table.js path is : ./.venv/lib/python2.7/site-
packages/xstatic/pkg/angular_smart_table/data/smart-table.js
https://github.com/openstack/horizon/blob/master/horizon/templates/horizon/_conf.html#L11
above line should be
script src={{ STATIC_URL }}horizon/lib/smart-table/smart-table.js
type=text/javascript charset=utf-8/script
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1409420/+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 1410832] Re: User name(with a link) inline edit doesn't work in identity users user table
** 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/1410832 Title: User name(with a link) inline edit doesn't work in identity users user table Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We implement user table inline edit and user detail, so the User Name cell will show input element as text while edting inline because the cell data will be escaped while it has url, we should unescaped inhorizon.tables_inline_edit.js while the cell is link, the patch fix it. Return escaped data while the cell has url: https://github.com/openstack/horizon/blob/master/horizon/tables/base.py#L744 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1410832/+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 1412469] Re: Integration tests sometime fail with WebDriverException: Message: The browser appears to have exited before we could connect.
** 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/1412469 Title: Integration tests sometime fail with WebDriverException: Message: The browser appears to have exited before we could connect. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: For example on test here ( http://logs.openstack.org/04/148204/4/check /gate-horizon-dsvm-integration/5b55890/console.html ) 2015-01-19 10:04:02.134 | 2015-01-19 10:04:02.118 | ERROR: openstack_dashboard.test.integration_tests.tests.test_flavors.TestFlavors.test_flavor_create 2015-01-19 10:04:02.136 | 2015-01-19 10:04:02.119 | -- 2015-01-19 10:04:02.168 | 2015-01-19 10:04:02.121 | _StringException: Traceback (most recent call last): 2015-01-19 10:04:02.168 | 2015-01-19 10:04:02.122 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py, line 72, in setUp 2015-01-19 10:04:02.169 | 2015-01-19 10:04:02.124 | super(AdminTestCase, self).setUp() 2015-01-19 10:04:02.169 | 2015-01-19 10:04:02.125 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py, line 33, in setUp 2015-01-19 10:04:02.169 | 2015-01-19 10:04:02.127 | self.driver = webdriver.WebDriverWrapper() 2015-01-19 10:04:02.169 | 2015-01-19 10:04:02.128 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/webdriver.py, line 59, in __init__ 2015-01-19 10:04:02.170 | 2015-01-19 10:04:02.130 | self.binary, timeout), 2015-01-19 10:04:02.170 | 2015-01-19 10:04:02.131 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/extension_connection.py, line 47, in __init__ 2015-01-19 10:04:02.170 | 2015-01-19 10:04:02.132 | self.binary.launch_browser(self.profile) 2015-01-19 10:04:02.171 | 2015-01-19 10:04:02.134 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/firefox_binary.py, line 66, in launch_browser 2015-01-19 10:04:02.171 | 2015-01-19 10:04:02.135 | self._wait_until_connectable() 2015-01-19 10:04:02.171 | 2015-01-19 10:04:02.137 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/firefox_binary.py, line 100, in _wait_until_connectable 2015-01-19 10:04:02.171 | 2015-01-19 10:04:02.138 | raise WebDriverException(The browser appears to have exited 2015-01-19 10:04:02.172 | 2015-01-19 10:04:02.140 | WebDriverException: Message: The browser appears to have exited before we could connect. If you specified a log_file in the FirefoxBinary constructor, check it for details. 3 tests with that error in http://logs.openstack.org/47/147047/5/gate /gate-horizon-dsvm-integration/2e044be/console.html : 2015-01-19 14:09:49.343 | 2015-01-19 14:09:49.309 | == 2015-01-19 14:09:49.343 | 2015-01-19 14:09:49.310 | ERROR: openstack_dashboard.test.integration_tests.tests.test_keypair.TestKeypair.test_keypair 2015-01-19 14:09:49.343 | 2015-01-19 14:09:49.311 | -- 2015-01-19 14:09:49.343 | 2015-01-19 14:09:49.313 | _StringException: Traceback (most recent call last): 2015-01-19 14:09:49.343 | 2015-01-19 14:09:49.314 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py, line 59, in setUp 2015-01-19 14:09:49.344 | 2015-01-19 14:09:49.315 | super(TestCase, self).setUp() 2015-01-19 14:09:49.344 | 2015-01-19 14:09:49.316 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py, line 33, in setUp 2015-01-19 14:09:49.344 | 2015-01-19 14:09:49.318 | self.driver = webdriver.WebDriverWrapper() 2015-01-19 14:09:49.344 | 2015-01-19 14:09:49.319 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/webdriver.py, line 59, in __init__ 2015-01-19 14:09:49.344 | 2015-01-19 14:09:49.320 | self.binary, timeout), 2015-01-19 14:09:49.345 | 2015-01-19 14:09:49.321 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/extension_connection.py, line 47, in __init__ 2015-01-19 14:09:49.345 | 2015-01-19 14:09:49.323 | self.binary.launch_browser(self.profile) 2015-01-19 14:09:49.345 | 2015-01-19 14:09:49.324 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/firefox_binary.py, line 66, in launch_browser 2015-01-19 14:09:49.345 | 2015-01-19 14:09:49.325 |
[Yahoo-eng-team] [Bug 1413156] Re: Duplicated messages in agent's fanout topic
** Changed in: neutron/juno Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1413156 Title: Duplicated messages in agent's fanout topic Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron juno series: Fix Released Bug description: Steps to reproduce on devstack: 1. Create the router: neutron router-create test 2. Set gateway for the router: neutron router-gateway-set test public 3. Delete the router: neutron router-delete test The notification about router deletion arrives into L3 agent twice: 2015-01-21 10:53:48.401 DEBUG neutron.agent.l3.agent [req-ce68777f-da33-4381-a7ff-9b8c0eaac380 demo bdb38765a9394f2c962b952675f65073] Got router deleted notification for 10bf431d-6c76-4b87-8db1-57e7fb69076 8 from (pid=8310) router_deleted /opt/stack/neutron/neutron/agent/l3/agent.py:969 2015-01-21 10:53:48.402 DEBUG neutron.agent.l3.agent [req-ce68777f-da33-4381-a7ff-9b8c0eaac380 demo bdb38765a9394f2c962b952675f65073] Got router deleted notification for 10bf431d-6c76-4b87-8db1-57e7fb69076 8 from (pid=8310) router_deleted /opt/stack/neutron/neutron/agent/l3/agent.py:969 Notifications are processed sequentially, the first successfully removes the router, while the second results in warning: 2015-01-21 10:53:50.957 WARNING neutron.agent.l3.agent [req-ce68777f-da33-4381-a7ff-9b8c0eaac380 demo bdb38765a9394f2c962b952675f65073] Info for router 10bf431d-6c76-4b87-8db1-57e7fb690768 were not found. Skipping router removal To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1413156/+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 1410583] Re: Metadata widget stopped working
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1410583 Title: Metadata widget stopped working Status in OpenStack Dashboard (Horizon): Fix Released Bug description: I tried the Update Metadata widget in Admin - Flavors and Admin - Images. They both used to display the list of available metadata on the left table. Users can then add them to the Existing Metadata table on the right by clicking on the + icon. Now the available metadata no longer shows up on the left table. Instead, there's a message No available metadata. Another issue is that the Other box is no longer working. I entered a new metadata key into the box and clicked +. The key was not added to the existing metadata list. It was displayed down in the description area below ( see attachment ). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1410583/+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 1404432] Re: Descriptive error message when Create User 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/1404432 Title: Descriptive error message when Create User fails Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Currently, when we try to create a new user with an existing User Name, the process fails and displays an error message Error: Unable to create user.. This error message is insufficient to inform the user about what exactly went wrong ( same User Name). Since we allow users with same email address to exist but not the same User Name, the error message should be specific to the problem Error: User name xyz is already used so that the user knows that its the same User Name thats causing the error and he needs to change the User Name and not worry about changing other fields in the new user creation form. Steps to reproduce the bug: 1. Create new user with User Name xyz (Success) 2. Create another user with User Name xyz1 (Error: Unable to create user) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1404432/+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 1395777] Re: remove current flavor from resize instance, database
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- 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/1395777 Title: remove current flavor from resize instance, database Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The current flavor is kept in the list of options for resize instance and resize database instance. It would be better to remove the current flavor from the list of options. Was observed during a code review https://review.openstack.org/#/c/108793/7/openstack_dashboard/dashboards/project/databases/forms.py To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1395777/+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
