[Yahoo-eng-team] [Bug 1257626] [NEW] Timeout while waiting on RPC response - topic: "network", RPC method: "allocate_for_instance" info: ""
Public bug reported: http://logs.openstack.org/21/59121/6/check/gate-tempest-dsvm-large- ops/fdd1002/logs/screen-n-cpu.txt.gz?level=TRACE#_2013-12-04_06_20_16_658 2013-12-04 06:20:16.658 21854 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s) <...> 2013-12-04 06:20:16.658 21854 TRACE nova.compute.manager Timeout: Timeout while waiting on RPC response - topic: "network", RPC method: "allocate_for_instance" info: "" It appears there has been a performance regression and that gate-tempest-dsvm-large-ops is now failing because of RPC timeouts to allocate_for_instance logstash query: message:"nova.compute.manager Timeout: Timeout while waiting on RPC response - topic: \"network\", RPC method: \"allocate_for_instance\"" There seems to have been a major rise in this bug on December 3rd. ** Affects: nova Importance: Critical Status: New ** Changed in: nova Milestone: None => icehouse-2 ** Changed in: nova Importance: Undecided => Critical -- 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/1257626 Title: Timeout while waiting on RPC response - topic: "network", RPC method: "allocate_for_instance" info: "" Status in OpenStack Compute (Nova): New Bug description: http://logs.openstack.org/21/59121/6/check/gate-tempest-dsvm-large- ops/fdd1002/logs/screen-n-cpu.txt.gz?level=TRACE#_2013-12-04_06_20_16_658 2013-12-04 06:20:16.658 21854 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s) <...> 2013-12-04 06:20:16.658 21854 TRACE nova.compute.manager Timeout: Timeout while waiting on RPC response - topic: "network", RPC method: "allocate_for_instance" info: "" It appears there has been a performance regression and that gate-tempest-dsvm-large-ops is now failing because of RPC timeouts to allocate_for_instance logstash query: message:"nova.compute.manager Timeout: Timeout while waiting on RPC response - topic: \"network\", RPC method: \"allocate_for_instance\"" There seems to have been a major rise in this bug on December 3rd. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1257626/+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 1257641] Re: Quota exceeded for instances: Requested 1, but already used 10 of 10 instances
** Also affects: nova Importance: Undecided Status: New -- 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/1257641 Title: Quota exceeded for instances: Requested 1, but already used 10 of 10 instances Status in OpenStack Compute (Nova): New Status in Tempest: New Bug description: Tempest (or nova) appears to be leaking servers. Since we run gate tests with concurrency=4 I don't think we should normally hit a case where we are consuming 10 instances. http://logs.openstack.org/84/59684/4/check/check-tempest-dsvm- postgres-full/9e38ebb/testr_results.html.gz http://logstash.openstack.org/#eyJzZWFyY2giOiJcIlF1b3RhIGV4Y2VlZGVkIGZvciBpbnN0YW5jZXM6IFJlcXVlc3RlZCAxLCBidXQgYWxyZWFkeSB1c2VkIDEwIG9mIDEwIGluc3RhbmNlc1wiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiIxNzI4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzg2MTQ1OTIzMDMwfQ== query: "Quota exceeded for instances: Requested 1, but already used 10 of 10 instances" AND filename:"console.html" First seen on 12/3 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1257641/+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 1257644] [NEW] gate-tempest-dsvm-postgres-full fails - unable to schedule instance
Public bug reported: The trace for the failure is: 2013-12-04 08:01:19.167 INFO nova.filters [req-9b187d9f-258f-42ef-8235-973de78a46d9 InstanceActionsV3TestXML-tempest-1651913648-user InstanceActionsV3TestXML-tempest-1651913648-tenant] Filter ComputeFilter returned 0 hosts 2013-12-04 08:01:19.168 WARNING nova.scheduler.driver [req-9b187d9f-258f-42ef-8235-973de78a46d9 InstanceActionsV3TestXML-tempest-1651913648-user InstanceActionsV3TestXML-tempest-1651913648-tenant] [instance: 78a1af24-f108-404c-a9e8-a021362c206b] Setting instance to ERROR state. 2013-12-04 08:01:27.352 INFO nova.scheduler.filter_scheduler [req-24c3c05c-c371-41b6-a314-3fa91340ed18 ImagesV3TestJSON-tempest-309232411-user ImagesV3TestJSON-tempest-309232411-tenant] Attempting to build 1 instance(s) uuids: [u'7e39573c-4ffd-4405-a109-cdca0685fe9c'] ** Affects: nova Importance: Undecided Status: New ** Affects: tempest Importance: Undecided Status: New ** Also affects: tempest Importance: Undecided Status: New -- 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/1257644 Title: gate-tempest-dsvm-postgres-full fails - unable to schedule instance Status in OpenStack Compute (Nova): New Status in Tempest: New Bug description: The trace for the failure is: 2013-12-04 08:01:19.167 INFO nova.filters [req-9b187d9f-258f-42ef-8235-973de78a46d9 InstanceActionsV3TestXML-tempest-1651913648-user InstanceActionsV3TestXML-tempest-1651913648-tenant] Filter ComputeFilter returned 0 hosts 2013-12-04 08:01:19.168 WARNING nova.scheduler.driver [req-9b187d9f-258f-42ef-8235-973de78a46d9 InstanceActionsV3TestXML-tempest-1651913648-user InstanceActionsV3TestXML-tempest-1651913648-tenant] [instance: 78a1af24-f108-404c-a9e8-a021362c206b] Setting instance to ERROR state. 2013-12-04 08:01:27.352 INFO nova.scheduler.filter_scheduler [req-24c3c05c-c371-41b6-a314-3fa91340ed18 ImagesV3TestJSON-tempest-309232411-user ImagesV3TestJSON-tempest-309232411-tenant] Attempting to build 1 instance(s) uuids: [u'7e39573c-4ffd-4405-a109-cdca0685fe9c'] To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1257644/+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 1254585] Re: Fix typo in keystone
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1254585 Title: Fix typo in keystone Status in OpenStack Identity (Keystone): Fix Released Bug description: Something like this: Validate the user and tenant auth into in order to -> Validate the user and tenant auth info attmepting -> attempting in keystone/catalog/templated.py extnsion -> extension in keystone/common/extension.py identfier -> identifierin keystone/common/cms.py establed -> established in keystone/contrib/endpoint_filter/controllers.py specifc -> specific in keystone/identity/core.py intitalized -> initialized in keystone/identity/core.py combatibility -> compatibility in keystone/middleware/auth_token.py explicity -> explicitly in keystone/openstack/common/db/sqlalchemy/models.py uniq -> unique in keystone/openstack/common/db/sqlalchemy/utils.py To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1254585/+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 1257301] Re: Bump hacking to 0.8
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1257301 Title: Bump hacking to 0.8 Status in OpenStack Identity (Keystone): Fix Released Status in Python client library for Keystone: In Progress Status in Python client library for Swift: In Progress Bug description: Due to Bump hacking dependency is not the 0.8, some compatibility checks with python 3.x are not being done on gate and it is bringing code issues. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1257301/+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 1249117] Re: examples/pki/cms/auth_token_unscoped.json does not parse
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1249117 Title: examples/pki/cms/auth_token_unscoped.json does not parse Status in OpenStack Identity (Keystone): Fix Released Bug description: examples/pki/cms/auth_token_unscoped.json does not parse Problems: 1. uses single quotes 2. has a trailing comma 3. no trailing newline (3) is not a parse problem but some linters don't like it I'll submit a fix shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1249117/+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 1246473] Re: A non-existing tenant can be added to a user
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1246473
Title:
A non-existing tenant can be added to a user
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
1. Create a user without setting the tenantId.
2. Update this user with adding a non-existing tenantId property
http://10.1.0.99:35357/v2.0/users/354eb97979364a368602b7ebf6362617
{
"user": {
"name": "user1",
"email": "us...@host.com",
"tenantId":"55",
"pass": "passw0rd",
"enabled": true
}
}
Actual Results: The user gets updated with the non-existing tenantId
successfully.
[root@vs10 ˜]# keystone user-get user1
+--+--+
| Property | Value |
+--+--+
| email | us...@host.com|
| enabled | True |
|id| 354eb97979364a368602b7ebf6362617 |
| name |user1 |
| pass | passw0rd |
| tenantId | 55 |
+--+--+
Expected Results: Updating the user with the non-existing tenantId
should fail.
Note that if the user already has a tenantId assigned to it, updating
with a non-existing tenantId will fail as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1246473/+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 1255864] Re: need to ignore swap files from getting into repository
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1255864 Title: need to ignore swap files from getting into repository Status in OpenStack Identity (Keystone): Fix Released Bug description: need to ignore swap files from getting into repository currently the implemented ignore in .gitignore is *.swp however vim goes beyond to generate these so to improve it could be done *.sw? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1255864/+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 1247142] Re: Live LDAP tests fail when trying to create user with an arbitrary attribute
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1247142
Title:
Live LDAP tests fail when trying to create user with an arbitrary
attribute
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
I ran _ldap_livetest and it failed with the following traceback:
FAIL:
keystone.tests.test_ldap_livetest.LiveLDAPIdentity.test_arbitrary_attributes_are_returned_from_create_user
tags: worker-0
--
Traceback (most recent call last):
File "keystone/tests/test_backend.py", line 2646, in
test_arbitrary_attributes_are_returned_from_create_user
user = self.identity_api.create_user(user_data['id'], user_data)
File "keystone/notifications.py", line 44, in wrapper
result = f(*args, **kwargs)
File "keystone/identity/core.py", line 179, in wrapper
return f(self, *args, **kwargs)
File "keystone/identity/core.py", line 324, in create_user
ref = driver.create_user(user_id, user)
File "keystone/identity/backends/ldap.py", line 95, in create_user
user_ref = self.user.create(user)
File "keystone/identity/backends/ldap.py", line 229, in create
values = super(UserApi, self).create(values)
File "keystone/common/ldap/core.py", line 738, in create
ref = super(EnabledEmuMixIn, self).create(values)
File "keystone/common/ldap/core.py", line 342, in create
conn.add_s(self._id_to_dn(values['id']), attrs)
File "keystone/common/ldap/core.py", line 565, in add_s
return self.conn.add_s(dn, ldap_attrs)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 194, in
add_s
return self.result(msgid,all=1,timeout=self.timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 422, in
result
res_type,res_data,res_msgid = self.result2(msgid,all,timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 426, in
result2
res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 432, in
result3
ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 96, in
_ldap_call
result = func(*args,**kwargs)
There are four tests in total which work with arbitrary attributes,
but three of them are skipped in test_backend_ldap:
def test_arbitrary_attributes_are_returned_from_get_user(self):
self.skipTest("Using arbitrary attributes doesn't work under LDAP")
def test_new_arbitrary_attributes_are_returned_from_update_user(self):
self.skipTest("Using arbitrary attributes doesn't work under LDAP")
def test_updated_arbitrary_attributes_are_returned_from_update_user(self):
self.skipTest("Using arbitrary attributes doesn't work under LDAP")
So I find it strange that
test_arbitrary_attributes_are_returned_from_create_user is not skipped
like these three.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1247142/+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 1248037] Re: Duplicate delete the user_project_metadata filter with project_id
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1248037 Title: Duplicate delete the user_project_metadata filter with project_id Status in OpenStack Identity (Keystone): Fix Released Bug description: When assignment backend is sql,duplicate delete the user_project_metadata filter with project_id. As follows: @sql.handle_conflicts(type='project') def delete_project(self, tenant_id): session = self.get_session() with session.begin(): tenant_ref = self._get_project(session, tenant_id) q = session.query(UserProjectGrant) q = q.filter_by(project_id=tenant_id) q.delete(False) q = session.query(UserProjectGrant) q = q.filter_by(project_id=tenant_id) q.delete(False) No need to delete the data duplicate. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1248037/+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 1247830] Re: Update role 'NoneType' object has no attribute 'setdefault'
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1247830
Title:
Update role 'NoneType' object has no attribute 'setdefault'
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Havana Keystone configured with LDAP.
When you try to update a role using the API:
curl -X PATCH --insecure -H "X-Auth-Token:the_token" -H "Content-type:
application/json" -d '{"role": {"name": "the new name"}}'
https://localhost:35357/v3/roles/role_id
Keystone server raises an error:
{"error": {"message": "An unexpected error prevented the server from
fulfilling your request. 'NoneType' object has no attribute
'setdefault'", "code": 500, "title": "Internal Server Error"}}
The role information is updated, but keystone server raises that
error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1247830/+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 1252466] Re: rules policy driver does not implement create_policy, delete_policy, get_policy, list_policies, update_policy, crashes on startup
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1252466
Title:
rules policy driver does not implement create_policy, delete_policy,
get_policy, list_policies, update_policy, crashes on startup
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When specifying the rules policy driver, keystone crashes on start up.
(keystone.conf)
[policy]
#driver = keystone.policy.backends.sql.Policy
driver = keystone.policy.backends.rules.Policy
(keystone.log)
2013-11-18 15:04:50.584 23679 INFO keystone.common.environment [-] KS-E2714F7
Environment configured as: eventlet
2013-11-18 15:04:51.156 23679 CRITICAL keystone [-] Can't instantiate
abstract class Policy with abstract methods create_policy, delete_policy,
get_policy, list_policies, update_policy
2013-11-18 15:04:51.156 23679 TRACE keystone Traceback (most recent call
last):
2013-11-18 15:04:51.156 23679 TRACE keystone File "/usr/bin/keystone-all",
line 133, in
2013-11-18 15:04:51.156 23679 TRACE keystone int(CONF.admin_port)))
2013-11-18 15:04:51.156 23679 TRACE keystone File "/usr/bin/keystone-all",
line 59, in create_server
2013-11-18 15:04:51.156 23679 TRACE keystone app =
deploy.loadapp('config:%s' % conf, name=name)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 247, in
loadapp
2013-11-18 15:04:51.156 23679 TRACE keystone return loadobj(APP, uri,
name=name, **kw)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 272, in
loadobj
2013-11-18 15:04:51.156 23679 TRACE keystone return context.create()
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 710, in create
2013-11-18 15:04:51.156 23679 TRACE keystone return
self.object_type.invoke(self)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 144, in invoke
2013-11-18 15:04:51.156 23679 TRACE keystone **context.local_conf)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/util.py", line 59, in fix_call
2013-11-18 15:04:51.156 23679 TRACE keystone reraise(*exc_info)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/compat.py", line 22, in reraise
2013-11-18 15:04:51.156 23679 TRACE keystone exec('raise t, e, tb',
dict(t=t, e=e, tb=tb))
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/util.py", line 56, in fix_call
2013-11-18 15:04:51.156 23679 TRACE keystone val = callable(*args, **kw)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/urlmap.py", line 25, in urlmap_factory
2013-11-18 15:04:51.156 23679 TRACE keystone app =
loader.get_app(app_name, global_conf=global_conf)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 350, in
get_app
2013-11-18 15:04:51.156 23679 TRACE keystone name=name,
global_conf=global_conf).create()
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 362, in
app_context
2013-11-18 15:04:51.156 23679 TRACE keystone APP, name=name,
global_conf=global_conf)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 450, in
get_context
2013-11-18 15:04:51.156 23679 TRACE keystone
global_additions=global_additions)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 559, in
_pipeline_app_context
2013-11-18 15:04:51.156 23679 TRACE keystone APP, pipeline[-1],
global_conf)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 458, in
get_context
2013-11-18 15:04:51.156 23679 TRACE keystone section)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 517, in
_context_from_explicit
2013-11-18 15:04:51.156 23679 TRACE keystone value =
import_string(found_expr)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/paste/deploy/loadwsgi.py", line 22, in
import_string
2013-11-18 15:04:51.156 23679 TRACE keystone return
pkg_resources.EntryPoint.parse("x=" + s).load(False)
2013-11-18 15:04:51.156 23679 TRACE keystone File
"/usr/lib/python2.6/site-packages/pkg_resources.p
[Yahoo-eng-team] [Bug 1246489] Re: races in assignment sql backend cause spurious 404s and transient errors while granting roles
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1246489 Title: races in assignment sql backend cause spurious 404s and transient errors while granting roles Status in OpenStack Identity (Keystone): Fix Released Bug description: There are numerous schedules that lead to inconsistent data in the various grant tables and role table. These races arise from a lack of synchronization during grant table modification (i.e., during grant record creation + deletion and role deletion) and deletions of records that grant records refer to (i.e., user, group, domain, and project records). For example, consider a project and a role that are related by a UserProjectGrant, which are concurrently deleted. In the implementation of delete_role, the project ids that are enumerated in one transaction (in keystone.assignment.backends.sql.Assignment.delete_role) are asserted to exist during another transaction (the call to self._get_project in delete_grant in the same class) and are referred to in two more transactions (_get_metadata and _create_metadata or _update_metadata). Suppose that after the enumeration of a project_id, but before the assertion of its existence, a transaction is committed that deletes the project_id. The result will be a 404 (project not found) and the role isn't deleted. Note that a subsequent delete_role API call will remove the Role record without hitting a 404 since the UserProjectGrant record will have been deleted by the delete_project transaction. Suppose two roles are being granted to the same user on the same project concurrently. Further suppose that prior to these two grants, the user didn't have any roles on that project. In Assignment.create_grant, a UserProjectGrant record is either updated or created anew depending on whether or not a UserProjectGrant record already exists for the (user, project) pair passed in. Since the existence check and the creation of a new record are performed in separate transactions, two (user, project) UserProjectGrant records can be created given the correct interleaving of the concurrent create_grant executions. Having the same user and project values, these two records would violate the primary key constraints on the UserProjectGrant table. Assuming the DBMS enforces the primary key constraints, then one of the create_grant requests will fail. Another example is described in https://review.openstack.org/#/c/50767/. Although I haven't been able to come up with an example yet, I suspect that grants or roles might become undeletable because of inconsistent data. The races pertaining to data owned by the keystone.assignment module (i.e., tenants, roles & grants) can be fixed by judicious use of transactions in keystone.assignment.backends.sql.Assignment. In particular, using a single transaction per API-level operation. The races pertaining to data owned by another module (i.e., groups and users are owned by keystone.identity) can't be fixed with transactions since the other module might be using a different backend (e.g., LDAP). Those races can't be outright eliminated but they can be turned into transient problems by removing existence assertions during deletion operations (such as https://review.openstack.org/#/c/50767/) and adding existence assertions to creation operations. Running multiple keystone processes, which can be done either via apache or https://review.openstack.org/#/c/42967/, aggravates the likelihood of these races. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1246489/+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 1254036] Re: misleading error message when keystone.conf not found
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1254036 Title: misleading error message when keystone.conf not found Status in OpenStack Identity (Keystone): Fix Released Bug description: If you start keystone without an available `keystone.conf`, it fails with this message: 2013-11-22 07:47:05.193 40690 CRITICAL keystone [-] The Keystone paste configuration file keystone.conf could not be found. Note that `keystone.conf` no longer provides paste configuration, as that's been separated into `keystone-paste.ini`. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1254036/+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 1242855] Re: [OSSA 2013-028] Removing role adds role with LDAP backend
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1242855 Title: [OSSA 2013-028] Removing role adds role with LDAP backend Status in OpenStack Identity (Keystone): Fix Released Status in Keystone grizzly series: Fix Committed Status in Keystone havana series: Fix Committed Status in OpenStack Security Advisories: Fix Released Bug description: Using the LDAP assignment backend, if you attempt to remove a role from a user on a tenant and the user doesn't have that role on the tenant then the user is actually granted the role on the tenant. Also, the role must not have been granted to anyone on the tenant before. To recreate 0) Start with devstack, configured with LDAP (note especially to set KEYSTONE_ASSIGNMENT_BACKEND): In localrc, enable_service ldap KEYSTONE_IDENTITY_BACKEND=ldap KEYSTONE_ASSIGNMENT_BACKEND=ldap 1) set up environment with OS_USERNAME=admin export OS_USERNAME=admin ... 2) Create a new user, give admin role, list roles: $ keystone user-create --name blktest1 --pass blkpwd +--+--+ | Property | Value | +--+--+ | email | | | enabled | True | |id| 3b71182dc36e45c6be4733d508201694 | | name | blktest1 | +--+--+ $ keystone user-role-add --user blktest1 --role admin --tenant service (no output) $ keystone --os-user=blktest1 --os-pass=blkpwd --os-tenant-name service user-role-list +--+---+--+--+ |id| name | user_id |tenant_id | +--+---+--+--+ | 1c39fab0fa9a4a68b307e7ce1535c62b | admin | 3b71182dc36e45c6be4733d508201694 | 5b0af1d5013746b286b0d650da73be57 | +--+---+--+--+ 3) Remove a role from that user that they don't have (using otherrole here since devstack sets it up): $ keystone --os-user=blktest1 --os-pass=blkpwd --os-tenant-name service user-role-remove --user blktest1 --role anotherrole --tenant service - Expected to fail with 404, but it doesn't! 4) List roles as that user: $ keystone --os-user=blktest1 --os-pass=blkpwd --os-tenant-name service user-role-list +--+-+--+--+ |id| name| user_id |tenant_id | +--+-+--+--+ | 1c39fab0fa9a4a68b307e7ce1535c62b |admin| 3b71182dc36e45c6be4733d508201694 | 5b0af1d5013746b286b0d650da73be57 | | afe23e7955704ccfad803b4a104b28a7 | anotherrole | 3b71182dc36e45c6be4733d508201694 | 5b0af1d5013746b286b0d650da73be57 | +--+-+--+--+ - Expected to not include the role that was just removed! 5) Remove the role again: $ keystone --os-user=blktest1 --os-pass=blkpwd --os-tenant-name service user-role-remove --user blktest1 --role anotherrole --tenant service - No errors, which I guess is expected since list just said they had the role... 6) List roles, and now it's gone: $ keystone --os-user=blktest1 --os-pass=blkpwd --os-tenant-name service user-role-list +--+---+--+--+ |id| name | user_id |tenant_id | +--+---+--+--+ | 1c39fab0fa9a4a68b307e7ce1535c62b | admin | 3b71182dc36e45c6be4733d508201694 | 5b0af1d5013746b286b0d650da73be57 | +--+---+--+--+ 7) Remove role again: $ keystone --os-user=blktest1 --os-pass=blkpwd --os-tenant-name service user-role-remove --user blktest1 --role anotherrole --tenant service Could not find user, 3b71182dc36e45c6be4733d508201694. (HTTP 404) - Strangely says user not found rather than role not assigned. To manage notificat
[Yahoo-eng-team] [Bug 1246831] Re: Creating trust with invalid expires_at causes 500 error
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1246831 Title: Creating trust with invalid expires_at causes 500 error Status in OpenStack Identity (Keystone): Fix Released Bug description: If you attempt to create a trust with an invalid expires_at field (something which can't be parsed by timeutils.parse_isotime resulting in a ValueError), you get a 500 response https://github.com/openstack/keystone/blob/master/keystone/trust/controllers.py#L172 2013-10-31 18:12:25.365 4359 ERROR keystone.common.wsgi [-] Unable to parse date string u'bad.123Z' 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi Traceback (most recent call last): 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/common/wsgi.py", line 238, in __call__ 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi result = method(context, **params) 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/common/controller.py", line 158, in inner 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi return f(self, context, *args, **kwargs) 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/trust/controllers.py", line 174, in create_trust 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi (trust['expires_at'])) 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi File "/opt/stack/keystone/keystone/openstack/common/timeutils.py", line 52, in parse_isotime 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi raise ValueError(unicode(e)) 2013-10-31 18:12:25.365 4359 TRACE keystone.common.wsgi ValueError: Unable to parse date string u'bad.123Z' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1246831/+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 1239892] Re: Version for python-memcached not specified
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1239892 Title: Version for python-memcached not specified Status in OpenStack Identity (Keystone): Fix Released Bug description: Currently, Fedora ships with python-memcached 1.48. However, Keystone requires a later version, tested with at least 1.52. Only the test-requirements.txt speciefies mecached, as Keystone can be deployed without it, but in practice, memcached is often used for the token backend. At a minimum, test-requires should document the later version. This is what tells the downstream distributions which versions to require. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1239892/+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 1244304] Re: remove old swift port 8888 in sample script
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1244304 Title: remove old swift port in sample script Status in OpenStack Identity (Keystone): Fix Released Bug description: In /tools/sample_data.sh, it generates many data like endpoint for nova, glance and also swift. In old swift documents, they use 8080 port as swift proxy server running with tempauth, and port for swift + keystone environment. It's very old, and now in swift there is no document, sample, or default value using . After running sample_data.sh for generate an example enviornment, we have to switch swift port from 8080 to (default value and sample conf in swift always use 8080). For a newbie, the sample_data.sh doesn't work dericetly from him. So using 8080 here could help this script build an easy and fast test environment. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1244304/+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 1245539] Re: Error running test coverage: "no such option: --coverage"
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1245539 Title: Error running test coverage: "no such option: --coverage" Status in OpenStack Identity (Keystone): Fix Released Bug description: When running the keystone test suite with the coverage option, the following error occurs: http://paste.openstack.org/show/50060/ I can produce this error with either of the following commands: - tox -e cover - python setup.py testr --testr-args=--coverage # run inside the `cover` virtualenv To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1245539/+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 1239476] Re: kvs and sql assignment backend create_grant checks user/group existence
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1239476 Title: kvs and sql assignment backend create_grant checks user/group existence Status in OpenStack Identity (Keystone): Fix Released Bug description: The kvs assignment backend checks that the user and group exists, whereas the SQL backend does not. The contract for both should be the same, so pick one behavior or the other. Seems like we should be checking here, since creating something. kvs: https://github.com/openstack/keystone/blob/master/keystone/assignment/backends/kvs.py#L347 sql: https://github.com/openstack/keystone/blob/master/keystone/assignment/backends/sql.py#L97 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1239476/+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 1244605] Re: Developer docs should include instructions for runnings tests with tox
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1244605 Title: Developer docs should include instructions for runnings tests with tox Status in OpenStack Identity (Keystone): Fix Released Bug description: The current documentation [1] suggests that developers run tests using the `run_tests.sh` script. However, running this script gives the following deprecation message: $ ./run_tests.sh This script is now deprecated. Please use tox instead. Checkout http://tox.readthedocs.org/en/latest/ for information on tox. [press enter to continue] If this script is indeed deprecated, the docs should be updated to reference `tox` instead as the preferred test runner. [1] - http://docs.openstack.org/developer/keystone/developing.html#running-tests To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1244605/+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 1234283] Re: remove string formatting in log statements
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1234283
Title:
remove string formatting in log statements
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
This is based on comments in: https://review.openstack.org/#/c/46822/
The python logging module supports passing args and kwargs to populate
strings AFTER the logging level has been checked. That means that
string formatting can be avoided if it's unnecessary due to the
current logging level.
So, any instance of:
LOG.debug(_('The entity, %s, was not found.') % entity)
Can be replaced with:
LOG.debug(_('The entity, %s, was not found.'), entity)
Which will be slightly more performant when debug logging is disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1234283/+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 1226466] Re: keystone user CRUD uses "password" instead of "OS-KSADM:password"
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1226466
Title:
keystone user CRUD uses "password" instead of "OS-KSADM:password"
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When logging in with a user created with "OS-KSADM:password" instead
of "password" attribute returns:
{"error": {
"message": "An unexpected error prevented the server from fulfilling your
request. no hash specified",
"code": 500,
"title": "Internal Server Error"
}
}
The same error when logging in with a user created without the
"password" or "OS-KSADM:password" attribute.
Ref: http://docs.openstack.org/api/openstack-identity-
service/2.0/content/POST_addUser_v2.0_users_.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1226466/+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 1235778] Re: Keystone docs missing Read Only LDAP Config
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1235778 Title: Keystone docs missing Read Only LDAP Config Status in OpenStack Identity (Keystone): Fix Released Bug description: A subset of the information found in Adam Young's Read Only LDAP in Keystone weblog article (http://adam.younglogic.com/2013/10/read- only-ldap-in-keystone/) should be added to Keystone docs to provide a clear explanation of how to configure Keystone to use a Read Only LDAP with authentication through LDAP and Authorization through the SQL backend To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1235778/+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 1237089] Re: requirements should indicate module six required version #
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1237089 Title: requirements should indicate module six required version # Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Bug description: Some modules in Ceilometer uses library six and uses method add_metaclass, however, that only existed in six 1.3.0 and above. The ceilometer requirements.txt should be updated to reflect that. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1237089/+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 1035326] Re: keystone should allow different bind addresses for admin and public
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1035326 Title: keystone should allow different bind addresses for admin and public Status in OpenStack Identity (Keystone): Fix Released Bug description: Kestone supports configuration of an admin_port and a public_port. Applications may well want the admin port to be open on a different private network. Right now there is a single bind_host used for both so this cannot be done. There should be a public_bind_host and admin_bind_host in the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1035326/+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 1153719] Re: 401 responses do not include WWW-Authenticate header
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1153719
Title:
401 responses do not include WWW-Authenticate header
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When an HTTP 1.1 server responds with 401 status code, it MUST include
a WWW-Authenticate header. Keystone is not including the WWW-
Authenticate header when it responds with 401.
See http://tools.ietf.org/html/rfc2616#section-10.4.2
$ curl -i http://localhost:5000/v3/projects ; echo
HTTP/1.1 401 Not Authorized
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 116
Date: Mon, 11 Mar 2013 18:35:57 GMT
{"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Not Authorized"}}
The server should have included WWW-Authenticate in the response. I don't
know what it should be set to, but according to the HTTP 1.1 RFC, it has to be
set to something.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1153719/+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 1186059] Re: A Keystone user can't perform revoke_token operation due to absence of target in context
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1186059
Title:
A Keystone user can't perform revoke_token operation due to absence
of target in context
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
The default policy file which comes with keystone has
"["user_id:%(user_id)s"]" rule define for "identity:revoke_token" API, but to
trigger this rule the user_id should be the target.
For all the below listed APIs there is not target set, the way it happens for
API like "GET /users/{user_id}", in this case "["user_id:%(user_id)s"]" rule
never triggered and hence a legitimate user can not perform below operations
for his own token.
identity:check_token
identity:validate_token
identity:revoke_token
This issue can lead to a security vulnerability because token will
stay active till its life.
Fix: In my opinion we should use "X-Subject-Token" which is coming in
the header to derive the target for auth check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1186059/+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 1218190] Re: Use assertEqual instead of assertEquals in unitttest
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1218190 Title: Use assertEqual instead of assertEquals in unitttest Status in OpenStack Identity (Keystone): Fix Released Status in Python client library for Keystone: Fix Committed Status in Python client library for Neutron: Fix Committed Bug description: I noticed that [keystone, python-keystoneclient, python-neutronclient] configure tox.ini with py33 test, however, assertEquals is deprecated in py3 but ok with py2, so i think it is better to change all of assertEquals to assertEqual To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1218190/+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 1227507] Re: Not all token drivers have an implementation of delete_tokens()
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1227507 Title: Not all token drivers have an implementation of delete_tokens() Status in OpenStack Identity (Keystone): Fix Released Bug description: The SQL token driver has an implementation of delete_tokens() allowing for, say, efficient deletion of all tokens for a user. Unfortunately the other backend drivers do not...so this method is currently implementation instead in the virtual driver layer. We should fill out the other backends and then make the virtual driver layer what it should be...i.e. virtual and let the call fall through to the appropriate backend. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1227507/+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 1178740] Re: ec2_token middleware importns nova into Keystone project
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1178740 Title: ec2_token middleware importns nova into Keystone project Status in OpenStack Identity (Keystone): Fix Released Bug description: from nova import flags from nova import utils from nova import wsgi these things need to come from common, not another top level project. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1178740/+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 1186394] Re: running keystone-all on already running instance produces stack trace
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1186394 Title: running keystone-all on already running instance produces stack trace Status in OpenStack Identity (Keystone): Fix Released Bug description: Running on an already running instance, produces an exception (port already in use): [root@ykaul-os-keystone ~]# keystone-all -v Traceback (most recent call last): File "/usr/bin/keystone-all", line 104, in serve(*servers) File "/usr/bin/keystone-all", line 52, in serve server.start() File "/usr/lib/python2.6/site-packages/keystone/common/wsgi.py", line 70, in start socket = eventlet.listen((self.host, self.port), backlog=backlog) File "/usr/lib/python2.6/site-packages/eventlet/convenience.py", line 38, in listen sock.bind(addr) File "", line 1, in bind socket.error: [Errno 98] Address already in use To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1186394/+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 1254852] Re: cannot downgrade sql migrations for extensions
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1254852 Title: cannot downgrade sql migrations for extensions Status in OpenStack Identity (Keystone): Fix Released Bug description: Only the common migrations can be downgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1254852/+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 1236648] Re: __metaclass__ is incompatible for python 3
** Changed in: cinder Status: Fix Committed => Fix Released ** Changed in: cinder Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1236648 Title: __metaclass__ is incompatible for python 3 Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in Cinder: Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): Fix Committed Status in Oslo - a Library of Common OpenStack Code: Fix Committed Status in Python client library for Keystone: Fix Committed Status in Python client library for Nova: Fix Committed Bug description: Some class uses __metaclass__ for abc.ABCMeta. six be used in general for python 3 compatibility. For example import abc import six six.add_metaclass(abc.ABCMeta) class FooDriver: @abc.abstractmethod def bar(): pass To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1236648/+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 1245435] Re: Unable to remove aws key as normal user
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1245435 Title: Unable to remove aws key as normal user Status in OpenStack Identity (Keystone): Fix Released Bug description: In devstack as normal user I'm able to create a bunch of AWS key pair. But I'm unable to delete those AWS key pair as normal user. Below are the commands : fabien@devstack-1:~$ . openrc demo demo fabien@devstack-1:~/devstack$ keystone ec2-credentials-create +---+--+ | Property | Value | +---+--+ | access | 11fcd9628779482f9b7971ec0bc69359 | | secret | 4c7aa22f89ba49ce8de67512abf513df | | tenant_id | 53f4610540fd4be7938e65f4c9567e25 | | user_id | 970acc126501440b9bb60b5494b6460c | +---+--+ fabien@devstack-1:~/devstack$ keystone ec2-credentials-get --access 11fcd9628779482f9b7971ec0bc69359 +---+--+ | Property | Value | +---+--+ | access | 11fcd9628779482f9b7971ec0bc69359 | | secret | 4c7aa22f89ba49ce8de67512abf513df | | tenant_id | 53f4610540fd4be7938e65f4c9567e25 | | user_id | 970acc126501440b9bb60b5494b6460c | +---+--+ fabien@devstack-1:~/devstack$ keystone ec2-credentials-delete --access 11fcd9628779482f9b7971ec0bc69359 Unable to delete credential: Could not find credential, 11fcd9628779482f9b7971ec0bc69359. (HTTP 404) As admin user the deletion work as expected: fabien@devstack-1:~$ . openrc admin admin fabien@devstack-1:~/devstack$ . openrc admin admin fabien@devstack-1:~/devstack$ keystone ec2-credentials-delete --access 11fcd9628779482f9b7971ec0bc69359 Credential has been deleted. Is this the normal behavior ? To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1245435/+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 1232878] Re: developer manual for keystone services has broken links
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1232878 Title: developer manual for keystone services has broken links Status in OpenStack Identity (Keystone): Fix Released Bug description: there are broken links on: http://docs.openstack.org/developer/keystone/configuringservices.html like: middlewarearchitecture configuration To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1232878/+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 1235358] Re: invalid volume when source image virtual size is bigger than the requested size
** Changed in: cinder Status: Fix Committed => Fix Released ** Changed in: cinder Milestone: None => icehouse-1 -- 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/1235358 Title: invalid volume when source image virtual size is bigger than the requested size Status in Cinder: Fix Released Status in OpenStack Compute (Nova): Invalid Bug description: I created a volume from an image and booted an instance from it when instance boots I get this: 'selected cylinder exceeds maximum supported by bios' If I boot an instance from the same image I can boot with no issues so its just booting from the volume. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1235358/+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 1254046] Re: openstack.common.local module is out of date
** Changed in: cinder Status: Fix Committed => Fix Released ** Changed in: cinder Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1254046 Title: openstack.common.local module is out of date Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: local has a broken TLS symbol - strong_store, fixed in oslo some time ago in Ib544be1485823f6c619312fdee5a04031f48bbb4. All direct and indirect (lockutils and rpc) usages of strong_store might be potentially affected. Original change to Nova: https://review.openstack.org/#/c/57509/ To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1254046/+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 1250168] Re: gate-tempest-devstack-vm-neutron-large-ops is failing
This returned on December 3rd. ** Changed in: nova Status: Fix Committed => Confirmed ** Changed in: neutron Status: Invalid => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1250168 Title: gate-tempest-devstack-vm-neutron-large-ops is failing Status in OpenStack Neutron (virtual network service): Confirmed Status in OpenStack Compute (Nova): Confirmed Bug description: job 'gate-tempest-devstack-vm-neutron-large-ops' is failing on trunk. This job does the equivalent of 'nova boot --num-instances=150' using nova's fakevirt driver. And the job failing means either not all the VMs are coming up or neutron is taking too long. Sample output http://logs.openstack.org/44/54044/7/check/gate-tempest- devstack-vm-neutron-large-ops/7fdf4a3/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1250168/+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 1222696] Re: V3 Auth Controller calls V2 Token Controller
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1222696 Title: V3 Auth Controller calls V2 Token Controller Status in OpenStack Identity (Keystone): Fix Released Bug description: The V3 Auth Controller makes calls into the V2 Token Controller for the revocation list. This ideally should be self-contained within the V3 controller to allow for sane deprecation of the V2 controller (when appropriate). Likely this can be covered in the revocation refactor in IceHouse. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1222696/+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 1231220] Re: Add notifications for roles and groups
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1231220 Title: Add notifications for roles and groups Status in OpenStack Identity (Keystone): Fix Released Bug description: https://blueprints.launchpad.net/keystone/+spec/notifications only implemented notifications for projects and users. We should add notifications for groups and roles as well. Note https://bugs.launchpad.net/keystone/+bug/1226132 was made to issue notifications for domains To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1231220/+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 1230270] Re: Install guide has compute v1.1 in an endpoint
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1230270 Title: Install guide has compute v1.1 in an endpoint Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Manuals: Fix Released Bug description: Reported at http://docs.openstack.org/grizzly/openstack- compute/install/yum/content/compute-create- network.html#comment-1056259358 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1230270/+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 1152662] Re: sample policy.json should use new format
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1152662
Title:
sample policy.json should use new format
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Keystone's sample policy.json (keystone/etc/policy.json) should switch
to using the new format because it's easier to read and understand.
The new format is used by nova, for example, see
https://github.com/openstack/nova/blob/master/etc/nova/policy.json:
{
"context_is_admin": "role:admin",
"admin_or_owner": "is_admin:True or project_id:%(project_id)s",
"default": "rule:admin_or_owner",
...
vs keystone's:
{
"admin_required": [["role:admin"], ["is_admin:1"]],
"owner" : [["user_id:%(user_id)s"]],
"admin_or_owner": [["rule:admin_required"], ["rule:owner"]],
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1152662/+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 1218596] Re: document extension development
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1218596 Title: document extension development Status in OpenStack Identity (Keystone): Fix Released Bug description: Document how to implement an extension in detail. The documentation and correlated examples will create a boilerplate for new extensions to leverage. This should have all the extensions following the same strategy and produce common strategy as well as a more uniform extensions architecture and design. A further benefit is the easiness in reading code and hence review To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1218596/+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 1220913] Re: bp split-identity left unfinished
** 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/1220913 Title: bp split-identity left unfinished Status in OpenStack Identity (Keystone): Fix Released Bug description: The split backend moved a bunch of apis into 'assignment', but for compatibility identity has cross calls. This complicates our code. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1220913/+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 1240349] Re: publish_errors cfg option is broken
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1240349
Title:
publish_errors cfg option is broken
Status in Cinder:
In Progress
Status in OpenStack Identity (Keystone):
Fix Released
Status in OpenStack Neutron (virtual network service):
Fix Committed
Status in OpenStack Compute (Nova):
Fix Committed
Status in Trove - Database as a Service:
In Progress
Bug description:
Our nova.conf contains a publish_errors option, which doesn't work
because we don't have the necessary oslo modules:
# publish error events (boolean value)
publish_errors=true
[root@ip9-12-17-141 ˜]# Traceback (most recent call last):
File "/usr/bin/nova-api", line 10, in
sys.exit(main())
File "/usr/lib/python2.6/site-packages/nova/cmd/api.py", line 41, in main
logging.setup("nova")
File "/usr/lib/python2.6/site-packages/nova/openstack/common/log.py", line
372, in setup
_setup_logging_from_conf()
File "/usr/lib/python2.6/site-packages/nova/openstack/common/log.py", line
472, in _setup_logging_from_conf
logging.ERROR)
File
"/usr/lib/python2.6/site-packages/nova/openstack/common/importutils.py", line
40, in import_object
return import_class(import_str)(*args, **kwargs)
File
"/usr/lib/python2.6/site-packages/nova/openstack/common/importutils.py", line
30, in import_class
__import__(mod_str)
ImportError: No module named log_handler
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1240349/+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 1182861] Re: Switch to oslo.config 1.2.0 final
** Changed in: trove Status: Fix Committed => Fix Released ** Changed in: trove Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1182861 Title: Switch to oslo.config 1.2.0 final Status in OpenStack Telemetry (Ceilometer): Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Message Queuing Service (Marconi): Fix Committed Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Keystone: Fix Released Status in Trove - Database as a Service: Fix Released Bug description: These commits: https://review.openstack.org/#/q/I7826087147e0713edaaea85a72283998295e2281,n,z mean we're using an oslo.config tarball from http://tarballs.openstack.org/oslo.config/ Once oslo.config-1.2.0 has been published to pypi, we should switch to: oslo.config>=1.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1182861/+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 1177924] Re: Use testr instead of nose as the unittest runner.
** Changed in: keystone Status: Fix Committed => Fix Released ** Changed in: keystone Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1177924 Title: Use testr instead of nose as the unittest runner. Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Dashboard (Horizon): Triaged Status in OpenStack Identity (Keystone): Fix Released Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: Fix Committed Status in Python client library for heat: Fix Released Status in Python client library for Keystone: Fix Released Status in OpenStack Object Storage (Swift): New Status in Trove - Database as a Service: Triaged Bug description: We want to start using testr as our test runner instead of nose so that we can start running tests in parallel. For the projects that have switched we have seen improvements to test speed and quality. As part of getting set for that, we need to start using testtools and fixtures so provide the plumbing and test isolation needed for automatic parallelization. The work can be done piecemeal - with testtools and fixtures being added first, and then tox/run_tests being ported to us testr/subunit instead of nose. This work was semi tracked during Grizzly with this https://blueprints.launchpad.net/openstack-ci/+spec/grizzly-testtools blueprint. I am opening this bug so that we can track migration to testr on a per project basis. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1177924/+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 1257661] [NEW] should handle boolean string parameters through migrate_live API
Public bug reported:
If specifying false string ("False") as "block_migration" parameter of
migrate_live API like the following, nova considers it as True.
$ curl -i 'http://10.21.42.81:8774/v2/[..]/servers/[..]/action' -X POST
[..] -d '{"os-migrateLive": {"disk_over_commit": "False",
"block_migration": "False", "host": "localhost"}}'
On the other hand, nova can consider false string as false in the case of
"on_shared_storage" parameter of evacuate API.
That behavior seems API inconsistency.
** Affects: nova
Importance: Undecided
Status: New
--
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/1257661
Title:
should handle boolean string parameters through migrate_live API
Status in OpenStack Compute (Nova):
New
Bug description:
If specifying false string ("False") as "block_migration" parameter of
migrate_live API like the following, nova considers it as True.
$ curl -i 'http://10.21.42.81:8774/v2/[..]/servers/[..]/action' -X
POST [..] -d '{"os-migrateLive": {"disk_over_commit": "False",
"block_migration": "False", "host": "localhost"}}'
On the other hand, nova can consider false string as false in the case of
"on_shared_storage" parameter of evacuate API.
That behavior seems API inconsistency.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1257661/+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 1254046] Re: openstack.common.local module is out of date
** Changed in: heat Status: Fix Committed => Fix Released ** Changed in: heat Milestone: None => icehouse-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1254046 Title: openstack.common.local module is out of date Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Orchestration API (Heat): Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: local has a broken TLS symbol - strong_store, fixed in oslo some time ago in Ib544be1485823f6c619312fdee5a04031f48bbb4. All direct and indirect (lockutils and rpc) usages of strong_store might be potentially affected. Original change to Nova: https://review.openstack.org/#/c/57509/ To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1254046/+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 1244092] Re: db connection retrying doesn't work against db2
** Changed in: heat Status: Fix Committed => Fix Released ** Changed in: heat Milestone: None => icehouse-1 -- 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/1244092 Title: db connection retrying doesn't work against db2 Status in Orchestration API (Heat): Fix Released Status in OpenStack Compute (Nova): Fix Committed Status in Oslo - a Library of Common OpenStack Code: Fix Committed Bug description: When I start Openstack following below steps, Openstack services can't be started without db2 connection: 1, start openstack services; 2, start db2 service. I checked codes in session.py under nova/openstack/common/db/sqlalchemy, the root cause is db2 connection error code "-30081" isn't in conn_err_codes in _is_db_connection_error function, connection retrying codes are skipped against db2, in order to enable connection retrying function against db2, we need add db2 support in _is_db_connection_error function To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1244092/+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 1255391] Re: I can not see error message when create instance fails
** Changed in: horizon
Status: Fix Committed => Fix Released
** Changed in: horizon
Milestone: None => icehouse-1
--
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/1255391
Title:
I can not see error message when create instance fails
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
When an instance fails to boot, the status can be displayed as "Error"
in instances page.
However, I can not see error message from dashboard to find out why
the instance can not be started.
It should display error message from "Instance Details" page.
For example:
I can see "fault" field in nova client:
| fault| {u'message': u'No valid host was
found. ', u'code': 500, u'created': u'2013-11-27T02:38:21Z'} |
but I can not see it in "Instance Details" page.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1255391/+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 1254714] Re: XenAPI: Cached images are never re-used
** Changed in: nova 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/1254714 Title: XenAPI: Cached images are never re-used Status in OpenStack Compute (Nova): Fix Released Bug description: _create_cached_image_impl uses _find_cached_image to find the image - which in turn relies on the image name_label to be set. However, the bug is that at the end of _create_cached_image_impl the name_label is cleared - thus meaning the cached image is never re-used and always re-downloaded. This has the dual effect of slowing down each server start which could have used the cached image and slowing down the "find_cached_image" function as it needs to search an ever larger number of VDIs. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254714/+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 1255859] Re: need to ignore swap files from getting into repository
code review will prevent this from swap files getting into repositories. And end users can make sure to ignore them using https://help.github.com/articles/ignoring-files#global-gitignore ** Changed in: nova Status: Confirmed => Invalid -- 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/1255859 Title: need to ignore swap files from getting into repository Status in OpenStack Compute (Nova): Invalid Bug description: need to ignore swap files from getting into repository currently the implemented ignore in .gitignore is *.swp and *.swo however vim goes beyond to generate these so to improve it could be done *.sw? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1255859/+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 1255577] Re: Requests to Metadata API fail with 500 if Neutron network plugin is used
** Changed in: nova 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/1255577 Title: Requests to Metadata API fail with 500 if Neutron network plugin is used Status in OpenStack Compute (Nova): Fix Released Bug description: In TripleO devtest story we are using Nova + Baremetal Driver + Neutron. The provisioned baremetal instance obtains its configuration from Metadata API. Currently all requests to Metadata API fail with error 500. In nova-api log I can see the following traceback: 2013-11-27 11:44:01,423.423 5895 ERROR nova.api.metadata.handler [req-0d22f3c7-663e-452e-bfa9-747b728fc13b None None] Failed to get metadata for ip: 192.0.2.2 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler Traceback (most recent call last): 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/api/metadata/handler.py", line 136, in _handle_remote_ip_request 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler meta_data = self.get_metadata_by_remote_address(remote_address) 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/api/metadata/handler.py", line 78, in get_metadata_by_remote_address 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler data = base.get_metadata_by_address(self.conductor_api, address) 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/api/metadata/base.py", line 466, in get_metadata_by_address 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler fixed_ip = network.API().get_fixed_ip_by_address(ctxt, address) 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 680, in get_fixed_ip_by_address 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler uuid_maps = self._get_instance_uuids_by_ip(context, address) 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 582, in _get_instance_uuids_by_ip 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler data = neutronv2.get_client(context).list_ports(**search_opts) 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler File "/opt/stack/venvs/nova/local/lib/python2.7/site-packages/nova/network/neutronv2/__init__.py", line 69, in get_client 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler raise exceptions.Unauthorized() 2013-11-27 11:44:01,423.423 5895 TRACE nova.api.metadata.handler Unauthorized: Unauthorized: bad credentials Analyzing this issue we found that Metadata API stopped working since change https://review.openstack.org/#/c/56174/4 was merged (it seems that change of line 57 in https://review.openstack.org/#/c/56174/4/nova/network/neutronv2/__init__.py is the reason). The commit message looks pretty sane and that fix seems to be the right thing to do, because we don't want to do neutron requests on behalf of neutron service user we have in nova config, but rather on behalf of the admin user instead who made the original request to nova api. So it seems that context.is_admin should be extended to make it possible to distinguish between those two cases of admin users: the real admin users, and the cases when nova api needs to talk to neutron. The problem is that all metadata queries are handled using default admin context (user and other vars are set to None while is_admin=True), so with https://review.openstack.org/#/c/56174/4 applied, get_client() always raises an exception when Metadata API requests are handled. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1255577/+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 1253768] Re: network topology ajax call keeps requesting data even on token errors
** 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/1253768 Title: network topology ajax call keeps requesting data even on token errors Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The network topology panel continues to request data via ajax call regardless of any errors that happen. One example of error is if user's token expires. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1253768/+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 1252881] Re: detach volume dialog contains escaped html
** 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/1252881 Title: detach volume dialog contains escaped html Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: In Progress Bug description: It looks like I went a little to far when cleaning up XSS problems. If you go to volumes panel, bring up assignments page and detach volume, you see an "Are you sure" dialog that contains escaped HTML. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1252881/+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 1252082] Re: Cannot assign different translations for present and past message of BatchAction
** 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/1252082
Title:
Cannot assign different translations for present and past message of
BatchAction
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in OpenStack Dashboard (Horizon) havana series:
In Progress
Bug description:
Message strings of BatchAction (including DeleteAction) is generated
in _conjugate of BatchAction in horizon/tables/actions.py.
_conjugate() generates both "present" message string (which is used as
table action name and confirm dialog) and "past" message strings
(which is displayed as a message popup after the specified operation
is completed).
Iin some languages (at least Japanese) we need to use different
translated strings for "present" and "past" message strings, but The
same string "%(action)s %(data_type)s" is used to generate them. As a
result, either of "present" or "past" message string may become odd
translation string (e.g., Havana Horizon translation in Japanese has
some odd strings due to this issue).
At least it is better "present" and "past" message strings can be
distinguished.
From translation perspective, it is ideal we can define "present" and
"past" strings respectively for each action class rather than
generating strings in _conjugate(). Translator need to use different
strings based on action types. It will be filed as a separate bug.
My idea is to use contextual marker [1] to distinguish them.
I would like to hear opinions before proposing a patch.
@@ -557,8 +558,11 @@ class BatchAction(Action):
data_type = self.data_type_singular
else:
data_type = self.data_type_plural
-return _("%(action)s %(data_type)s") % {'action': action,
-'data_type': data_type}
+if action_type == "past":
+msgstr = pgettext_lazy("past", "%(action)s %(data_type)s")
+else:
+msgstr = pgettext_lazy("present", "%(action)s %(data_type)s")
+return msgstr % {'action': action, 'data_type': data_type}
def action(self, request, datum_id):
"""
After this, we can get the following entries in the PO file and assign
different translations to "past" and "present" strings.
#: tables/actions.py:562
#, python-format
msgctxt "past"
msgid "%(action)s %(data_type)s"
msgstr ""
#: tables/actions.py:564
#, python-format
msgctxt "present"
msgid "%(action)s %(data_type)s"
msgstr ""
[1]
https://docs.djangoproject.com/en/dev/topics/i18n/translation/#contextual-markers
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1252082/+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 1252738] Re: wrong error message after changing admins password
** 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/1252738 Title: wrong error message after changing admins password Status in OpenStack Dashboard (Horizon): Fix Released Bug description: after changing the admin password via admin/users/edit, the (false error message) pops up: Error: Unable to update the user. The password is updated anyways. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1252738/+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 1250581] Re: run_tests.sh fails with a fresh venv due to django 1.6 installed
** 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/1250581 Title: run_tests.sh fails with a fresh venv due to django 1.6 installed Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: In Progress Bug description: Today when i removed the existing vnev and ran run_tests.sh, run_tests.sh failed. run_tests.sh creates a fresh venv. I found Django 1.6 is installed. it seems django-nose dependencies installs django-1.6. It happens when we run "pip install -r requirements.txt" and then run "pip install -r test-requirements.txt" with --upgrade option. Horizon tools/install_venv_common is old and it seems to do so. In the recent tools/install_venv_common both requirements files are evaluated at the same time and it looks the right solution. Updating them to new version (from oslo) addresses this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1250581/+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 1251700] Re: migration error: invalid version number '0.7.3.dev'
** Changed in: nova 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/1251700 Title: migration error: invalid version number '0.7.3.dev' Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: In Progress Status in Tuskar: Fix Released Bug description: Using a tripleO seed VM I hit this issue today when trying to run the nova db migrations: (nova)[root@localhost migrate]# /opt/stack/venvs/nova/bin/nova-manage --debug --verbose db sync Command failed, please check log for more info 2013-11-15 16:53:18,579.579 9082 CRITICAL nova [-] invalid version number '0.7.3.dev' 2013-11-15 16:53:18,579.579 9082 TRACE nova Traceback (most recent call last): 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/bin/nova-manage", line 10, in 2013-11-15 16:53:18,579.579 9082 TRACE nova sys.exit(main()) 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/cmd/manage.py", line 1378, in main 2013-11-15 16:53:18,579.579 9082 TRACE nova ret = fn(*fn_args, **fn_kwargs) 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/cmd/manage.py", line 886, in sync 2013-11-15 16:53:18,579.579 9082 TRACE nova return migration.db_sync(version) 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/db/migration.py", line 31, in db_sync 2013-11-15 16:53:18,579.579 9082 TRACE nova return IMPL.db_sync(version=version) 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/utils.py", line 438, in __getattr__ 2013-11-15 16:53:18,579.579 9082 TRACE nova backend = self.__get_backend() 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/utils.py", line 434, in __get_backend 2013-11-15 16:53:18,579.579 9082 TRACE nova self.__backend = __import__(name, None, None, fromlist) 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/db/sqlalchemy/migration.py", line 52, in 2013-11-15 16:53:18,579.579 9082 TRACE nova dist_version.StrictVersion(migrate.__version__) < MIN_PKG_VERSION): 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/usr/lib64/python2.7/distutils/version.py", line 40, in __init__ 2013-11-15 16:53:18,579.579 9082 TRACE nova self.parse(vstring) 2013-11-15 16:53:18,579.579 9082 TRACE nova File "/usr/lib64/python2.7/distutils/version.py", line 107, in parse 2013-11-15 16:53:18,579.579 9082 TRACE nova raise ValueError, "invalid version number '%s'" % vstring 2013-11-15 16:53:18,579.579 9082 TRACE nova ValueError: invalid version number '0.7.3.dev' To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1251700/+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 1251784] Re: nova+neutron scheduling error: Connection to neutron failed: Maximum attempts reached
** Changed in: nova
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/1251784
Title:
nova+neutron scheduling error: Connection to neutron failed: Maximum
attempts reached
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
Fix Released
Status in tripleo - openstack on openstack:
Fix Released
Bug description:
VMs are failing to schedule with the following error
2013-11-15 20:50:21.405 ERROR nova.scheduler.filter_scheduler [req-
d2c26348-53e6-448a-8975-4f22f4e89782 demo demo] [instance: c8069c13
-593f-48fb-aae9-198961097eb2] Error from last host: devstack-precise-
hpcloud-az3-662002 (node devstack-precise-hpcloud-az3-662002):
[u'Traceback (most recent call last):\n', u' File
"/opt/stack/new/nova/nova/compute/manager.py", line 1030, in
_build_instance\nset_access_ip=set_access_ip)\n', u' File
"/opt/stack/new/nova/nova/compute/manager.py", line 1439, in _spawn\n
LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n',
u' File "/opt/stack/new/nova/nova/compute/manager.py", line 1436, in
_spawn\nblock_device_info)\n', u' File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 2100, in
spawn\nadmin_pass=admin_password)\n', u' File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 2451, in
_create_image\ncontent=files, extra_md=extra_md,
network_info=network_info)\n', u' File
"/opt/stack/new/nova/nova/api/metadata/base.py", line 165, in
__init__\n
ec2utils.get_ip_info_for_instance_from_nw_info(network_info)\n', u'
File "/opt/stack/new/nova/nova/api/ec2/ec2utils.py", line 149, in
get_ip_info_for_instance_from_nw_info\nfixed_ips =
nw_info.fixed_ips()\n', u' File
"/opt/stack/new/nova/nova/network/model.py", line 368, in
_sync_wrapper\nself.wait()\n', u' File
"/opt/stack/new/nova/nova/network/model.py", line 400, in wait\n
self[:] = self._gt.wait()\n', u' File "/usr/local/lib/python2.7/dist-
packages/eventlet/greenthread.py", line 168, in wait\nreturn
self._exit_event.wait()\n', u' File "/usr/local/lib/python2.7/dist-
packages/eventlet/event.py", line 120, in wait\n
current.throw(*self._exc)\n', u' File "/usr/local/lib/python2.7/dist-
packages/eventlet/greenthread.py", line 194, in main\nresult =
function(*args, **kwargs)\n', u' File
"/opt/stack/new/nova/nova/compute/manager.py", line 1220, in
_allocate_network_async\ndhcp_options=dhcp_options)\n', u' File
"/opt/stack/new/nova/nova/network/neutronv2/api.py", line 359, in
allocate_for_instance\nnw_info =
self._get_instance_nw_info(context, instance, networks=nets)\n', u'
File "/opt/stack/new/nova/nova/network/api.py", line 49, in wrapper\n
res = f(self, context, *args, **kwargs)\n', u' File
"/opt/stack/new/nova/nova/network/neutronv2/api.py", line 458, in
_get_instance_nw_info\nnw_info =
self._build_network_info_model(context, instance, networks)\n', u'
File "/opt/stack/new/nova/nova/network/neutronv2/api.py", line 1022,
in _build_network_info_model\nsubnets =
self._nw_info_get_subnets(context, port, network_IPs)\n', u' File
"/opt/stack/new/nova/nova/network/neutronv2/api.py", line 924, in
_nw_info_get_subnets\nsubnets =
self._get_subnets_from_port(context, port)\n', u' File
"/opt/stack/new/nova/nova/network/neutronv2/api.py", line 1066, in
_get_subnets_from_port\ndata =
neutronv2.get_client(context).list_ports(**search_opts)\n', u' File
"/opt/stack/new/python-neutronclient/neutronclient/v2_0/client.py",
line 111, in with_params\nret = self.function(instance, *args,
**kwargs)\n', u' File "/opt/stack/new/python-
neutronclient/neutronclient/v2_0/client.py", line 306, in list_ports\n
**_params)\n', u' File "/opt/stack/new/python-
neutronclient/neutronclient/v2_0/client.py", line 1250, in list\n
for r in self._pagination(collection, path, **params):\n', u' File
"/opt/stack/new/python-neutronclient/neutronclient/v2_0/client.py",
line 1263, in _pagination\nres = self.get(path, params=params)\n',
u' File "/opt/stack/new/python-
neutronclient/neutronclient/v2_0/client.py", line 1236, in get\n
headers=headers, params=params)\n', u' File "/opt/stack/new/python-
neutronclient/neutronclient/v2_0/client.py", line 1228, in
retry_request\nraise exceptions.ConnectionFailed(reason=_("Maximum
attempts reached"))\n', u'ConnectionFailed: Connection to neutron
failed: Maximum attempts reached\n']
Connection to neutron failed: Maximum attempts reached
http://logs.openstack.org/96/56496/1/gate/gate-tempest-devstack-vm-
neutron-
isolated/8df6c6c/logs/screen-n-sch.txt.gz#_2013-11-15_20_50_21_405
logstash query: "Connection to neutron failed: Maximum attempts reached" AND
filename:"logs/screen-n-sch.txt"
To manage notifica
[Yahoo-eng-team] [Bug 1250554] Re: iso8601 debug message is annoying in dashboard unit test
** 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/1250554 Title: iso8601 debug message is annoying in dashboard unit test Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: Fix Committed Bug description: log messages from iso8601 0.1.8 are not masked in openstack_dashboard unit test and output to the console. It makes hard to track the test progress. We need to control the debug level of iso8601 module in settings.py To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1250554/+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 1251374] Re: Errored snapshots shouldn't be shown in the 'Create Volume' menu
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1251374 Title: Errored snapshots shouldn't be shown in the 'Create Volume' menu Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We should filter out snapshots with the status "Error" from the drop- down list when Creating a new Volume since they won't work. https://github.com/openstack/horizon/blob/00f8b11d956cbdee1bbe06a67b79127b6e3e330f/openstack_dashboard/dashboards/project/volumes/forms.py#L110 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1251374/+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 1250237] Re: Use compat trove version to fix incompatibility issue with trove client
** 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/1250237 Title: Use compat trove version to fix incompatibility issue with trove client Status in OpenStack Dashboard (Horizon): Fix Released Bug description: trove-int in horizon is failing due to pip version dependency errors in global-requirement. To get around this, we need to make horizon gate not fail by importing the compat version of the client. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1250237/+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 1249279] Re: Resource Usage Page table views shows statistics in a wrong way
** 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/1249279 Title: Resource Usage Page table views shows statistics in a wrong way Status in OpenStack Dashboard (Horizon): Fix Released Bug description: It was pointed out to me that some of the table columns are displayed in a wrong way, also the table heading Average 30 days won't be usable for all statistics. As I look back on this, almost each column has to be considered separately. So e.g. average over some time make sense only for gauge maybe delta type. Though for the cumulative type max makes much more sense. Also if I want to see a total value of a particular timeframe, I will have to do some extra computation (like max - min) to see e.g. network.incoming.bytes of the last month. (the max is a total of all times) There is e.g. *storage.objects.outgoing.bytes=Delta* but there is a * network. outgoing.bytes=Cumulative* , so there can't be unified approach of getting average over some time from them. Not sure why it is like that, but I am sure it has a good reason. :-) These table stats will be enhanced by the sparklines. So there it will be much more readable. The solution == Here comes the list of all used meters and description how each meter should be properly displayed: Global disk usage "disk.read.bytes", "disk.read.requests", "disk.write.bytes", "disk.write.requests" All above are cumulative. The best here will be show 'total for last 30 days aggregated by project'. But it will have to load all statistics grouped_by resource, computing (min - max) for each resource (gives the total amount in the time period for the one resource=disk). Then sum of them for each project is what we want. Or there can be average of them, not sure what is better. GlobalNetworkTrafficUsage --- "network.incoming.bytes" "network.incoming.packets" "network.outgoing.bytes" "network.outgoing.packets" Same approach as in Global disk usage will be done. GlobalNetworkUsage - "network" "network_create" "subnet" "subnet_create" "port" "port_create" "router" "router_create" "ip_floating" "ip_floating_create" They all follow pattern of these two: "network" - Gauge - Duration - I suspect it doesn't return the time up, but rather 1 or 0, depending whether the network was up or down during sampling. Not sure what to show here. Maybe counting a duration of each network of the tenant in last 30 days and then show average up-time of them? "network_create" - Creation requests: I suspect the samples doesn't show e.g. number of network_creates but there is a one record for each network created. So this should show rather count then avg. The field would show 'total in 30 days aggregated by tenant' GlobalObjectStoreUsage -- "storage.objects" "storage.objects.size" "storage.objects.incoming.bytes" "storage.objects.outgoing.bytes" all above are either delta or gauge and it make sense to leave them 'last 30 days average aggregated by tenant' as it is now Confirmation from Ceilometer Not sure if I understand all of the meters correctly, eglynn please could you confirm or correct the above? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1249279/+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 1247675] Re: Persistent XSS in OpenStack Web UI for Instances (CVE-2013-6858)
** 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/1247675 Title: Persistent XSS in OpenStack Web UI for Instances (CVE-2013-6858) Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) grizzly series: In Progress Status in OpenStack Dashboard (Horizon) havana series: Fix Committed Status in OpenStack Security Advisories: Confirmed Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, My name is Chris Chapman, I am an Incident Manager with Cisco PSIRT. I would like to report the following XSS issue found in the OpenStack WebUI that was reported to Cisco. The details are as follows: The OpenStack web user interface is vulnerable to XSS: While launching (or editing) an instance, injecting
[Yahoo-eng-team] [Bug 1243526] Re: ./templates/base.html.c:6: warning: unterminated string literal
** 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/1243526 Title: ./templates/base.html.c:6: warning: unterminated string literal Status in OpenStack Dashboard (Horizon): Fix Released Bug description: yanglei@yanglei-ThinkCentre-M58:~/community/horizon$ ./run_tests.sh --makemessages -N horizon: /home/yanglei/installed_openstack_devstack/pbr/pbr/version.py:21: UserWarning: Module openstack_dashboard was already imported from /home/yanglei/community/horizon/openstack_dashboard/__init__.pyc, but /home/yanglei/installed_openstack_devstack/horizon is being added to sys.path import pkg_resources WARNING:root:No local_settings file found. processing language en horizon javascript: /home/yanglei/installed_openstack_devstack/pbr/pbr/version.py:21: UserWarning: Module openstack_dashboard was already imported from /home/yanglei/community/horizon/openstack_dashboard/__init__.pyc, but /home/yanglei/installed_openstack_devstack/horizon is being added to sys.path import pkg_resources WARNING:root:No local_settings file found. processing language en Error: errors happened while running xgettext on base.html ./templates/base.html.c:6: warning: unterminated string literal yanglei@yanglei-ThinkCentre-M58:~/community/horizon$ git branch * master yanglei@yanglei-ThinkCentre-M58:~/community/horizon$ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1243526/+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 1241467] Re: precision of floating point metering stats is discarded unnecessarily
** 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/1241467 Title: precision of floating point metering stats is discarded unnecessarily Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: Fix Committed Bug description: Ceilometer returns aggregated statistical values as float, whereas the 'resource usage' panel narrows to int before inserting these data into the line chart. For meters defined over a narrow range (such as cpu_util ranging from 0.0% to 100.0%) this has the effect of unnaturally smoothening the graph by discarding precision. If it really was crucial that the line chart contain only ints, then the float->int conversion should be a round: i = int(round(f, 0)) as opposed to narrowing cast: i = int(f) However, AFAICS there's no reason why these raw data couldn't be represented directly as floats in the line chart. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1241467/+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 1243796] Re: charting of meters for all resource types other than instance is broken when not grouped by project
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1243796 Title: charting of meters for all resource types other than instance is broken when not grouped by project Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: In Progress Bug description: The 'Group by' dropdown on the Stats tab of the admin/Resource Usage panel allows the statistics to be grouped by either Project or '--'. From the code, it seems the intent of the '--' option is to group by resource ID, as opposed to project ID. This works as expected for the Compute (Nova) meters, but is broken for all the meters associated with any other resource type (glance images, swift objects, etc.) This is because the strategy used to query statistics by resource is to first find all the resources of the relevant type, then iterate over the resources separately querying for the statistics associated with the meter in question for each individual resource. The problem is that this initial query to discover the relevant resources is hard-coded in the group-by resource case to only ever identify instances: https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/metering/views.py#L124 As a result, the panel attempts to retrieve statistics for non- instance meters (e.g. 'image.download' or 'storage.objects') constrained to a resource ID associated with an instance. All of those queries are guaranteed never to yield any data. Instead, this iterative strategy should be replaced with a *single* statistics query with the 'groupby=resource_id' param set. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1243796/+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 1242541] Re: Instance DISPLAY_CHOICES not translatable
** Changed in: horizon
Status: Fix Committed => Fix Released
** Changed in: horizon
Milestone: None => icehouse-1
--
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/1242541
Title:
Instance DISPLAY_CHOICES not translatable
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Am I missing something or are these values not translatable?
openstack_dashboard/dashboards/project/instances/tables.py:STATUS_DISPLAY_CHOICES
= (
openstack_dashboard/dashboards/project/instances/tables.py-("resize",
"Resize/Migrate"),
openstack_dashboard/dashboards/project/instances/tables.py-
("verify_resize", "Confirm or Revert Resize/Migrate"),
openstack_dashboard/dashboards/project/instances/tables.py-
("revert_resize", "Revert Resize/Migrate"),
openstack_dashboard/dashboards/project/instances/tables.py-)
openstack_dashboard/dashboards/project/instances/tables.py-
openstack_dashboard/dashboards/project/instances/tables.py-
openstack_dashboard/dashboards/project/instances/tables.py:TASK_DISPLAY_CHOICES
= (
openstack_dashboard/dashboards/project/instances/tables.py-
("image_snapshot", "Snapshotting"),
openstack_dashboard/dashboards/project/instances/tables.py-
("resize_prep", "Preparing Resize or Migrate"),
openstack_dashboard/dashboards/project/instances/tables.py-
("resize_migrating", "Resizing or Migrating"),
openstack_dashboard/dashboards/project/instances/tables.py-
("resize_migrated", "Resized or Migrated"),
openstack_dashboard/dashboards/project/instances/tables.py-
("resize_finish", "Finishing Resize or Migrate"),
openstack_dashboard/dashboards/project/instances/tables.py-
("resize_confirming", "Confirming Resize or Nigrate"),
openstack_dashboard/dashboards/project/instances/tables.py-
("resize_reverting", "Reverting Resize or Migrate"),
openstack_dashboard/dashboards/project/instances/tables.py-("unpausing",
"Resuming"),
openstack_dashboard/dashboards/project/instances/tables.py-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1242541/+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 1243241] Re: missing hover hint for instance: meter in Metric dropdown list
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1243241 Title: missing hover hint for instance: meter in Metric dropdown list Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: Fix Committed Bug description: The Metric dropdown list on the Stats tab of the admin/Resource Usage panel has hover hints with a short description of each meter listed. However the hover hint for instance: meter is missing. This is because tab context_data list of hover hints is seemingly built up from a copy'n'paste from the ceilometer documentation: http://docs.openstack.org/developer/ceilometer/measurements.html #compute-nova in particular, using the literal 'instance:' as the meter name. Whereas in the ceilometer docco, 'instance:' is not intended to be interpreted as a literal meter name. Instead the '' is intended to act as a placeholder for the actual instance type, i.e. the nova flavor name of 'm1.tiny', 'm1.small', etc. So this non-existent 'instance:' meter should be replaced with a set of hints for meters named with a 'instance:' prefix and a flavor name suffix, for each of the current set of flavors known to nova (i.e. both standard and custom instance types). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1243241/+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 1234993] Re: Sort List of Tenants in Sidebar
** 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/1234993 Title: Sort List of Tenants in Sidebar Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We have a few hundred tenants accessible by some of our customers. By default, they are sorted by primary key (UUID), which is not very handy, in the sidebar. The attached patch sorts them by name, which makes them significantly easier to find. It is a straightforward Django template modification. Patch generated against Grizzly. My apologies ahead of time in the very likely case that I got the patch format incorrect; point me in the right direction and I'm happy to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1234993/+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 1236611] Re: Localized string does not render on generated cell links
** 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/1236611
Title:
Localized string does not render on generated cell links
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Localized string have a proxy value and does not render on html.
Example (adding a column "localized_string" that returns a localized
string) :
def get_localized_string(datum):
return _("Localized String")
class TenantsTable(tables.DataTable):
name = tables.Column('name', verbose_name=_('Name'))
description = tables.Column(lambda obj: getattr(obj, 'description', None),
verbose_name=_('Description'))
id = tables.Column('id', verbose_name=_('Project ID'))
enabled = tables.Column('enabled', verbose_name=_('Enabled'), status=True)
localized_string = tables.Column(get_localized_string,
link="horizon:admin:projects:update",
verbose_name=_('Localized'))
The column localized_string does not render at all.
A solution would be to enclose the string in unicode() prior to
displaying.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1236611/+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 1243298] Re: only meters associated with the first instance reported appear in Metric dropdown list
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1243298 Title: only meters associated with the first instance reported appear in Metric dropdown list Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: Fix Committed Bug description: The Compute (Nova) meters list is generally incomplete in the Metric dropdown on the Stats tab of the admin/Resource Usage panel. The content of this dropdown list also changes from time to time. This is because the list is populated from the meter links in the *first* resource reported by the ceilometer API with availability zone metadata (i.e. indicating a nova instance). However, the set of meters associated with instances is not uniform in ceilometer (i.e. a certain meter gathered for one resource may not necessarily be gathered for another). Also the content of this list changes from time to time, depending on the order of sample acquisition (as a different instance, with a different set of associated meters, may be at the head of the resources list reported by the ceilometer API). For example, once instances of different flavors have been spun up in an openstack deployment, the Metric list will not contain all the possible compute meters, nor will it even always be incorrect in the same way. Only the 'instance:' meter relating to the first instance appears in the dropdown, and the identity of this first instance may change over time. So at any given point in time, only a subset of the compute meters are accessible via the dashboard. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1243298/+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 1236677] Re: swift_get_container should use swiftclient.head_container()
** 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/1236677 Title: swift_get_container should use swiftclient.head_container() Status in OpenStack Dashboard (Horizon): Fix Released Bug description: This method is just getting the metadata for the container and never using the data that's returned: def swift_get_container(request, container_name): headers, data = swift_api(request).get_object(container_name, "") Should probably be: headers = swift_api(request).head_container(container_name) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1236677/+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 1242846] Re: filter actions on tables in tabs throw exception
** 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/1242846 Title: filter actions on tables in tabs throw exception Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Key 'action' not found in " To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1242846/+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 1247198] Re: Troveclient requirement update fails due to test_basic_scenario[dashboard]
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1247198 Title: Troveclient requirement update fails due to test_basic_scenario[dashboard] Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Below test is failing consistently and as a result gerrit review https://review.openstack.org/#/c/52137/ is failing, which is blocking my other changes for DBaaS heat resource. 2013-11-01 15:07:09.391 | == 2013-11-01 15:07:09.391 | FAIL: tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard] 2013-11-01 15:07:09.391 | tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard] 2013-11-01 15:07:09.391 | -- 2013-11-01 15:07:09.392 | _StringException: Empty attachments: 2013-11-01 15:07:09.392 | pythonlogging:'' 2013-11-01 15:07:09.392 | stderr 2013-11-01 15:07:09.392 | stdout 2013-11-01 15:07:09.392 | 2013-11-01 15:07:09.392 | Traceback (most recent call last): 2013-11-01 15:07:09.392 | File "tempest/scenario/test_dashboard_basic_ops.py", line 72, in test_basic_scenario 2013-11-01 15:07:09.393 | self.check_login_page() 2013-11-01 15:07:09.393 | File "tempest/scenario/test_dashboard_basic_ops.py", line 43, in check_login_page 2013-11-01 15:07:09.393 | response = urllib2.urlopen(self.config.dashboard.dashboard_url) 2013-11-01 15:07:09.393 | File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen 2013-11-01 15:07:09.393 | return _opener.open(url, data, timeout) 2013-11-01 15:07:09.393 | File "/usr/lib/python2.7/urllib2.py", line 406, in open 2013-11-01 15:07:09.394 | response = meth(req, response) 2013-11-01 15:07:09.394 | File "/usr/lib/python2.7/urllib2.py", line 519, in http_response 2013-11-01 15:07:09.394 | 'http', request, response, code, msg, hdrs) 2013-11-01 15:07:09.394 | File "/usr/lib/python2.7/urllib2.py", line 444, in error 2013-11-01 15:07:09.395 | return self._call_chain(*args) 2013-11-01 15:07:09.395 | File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain 2013-11-01 15:07:09.395 | result = func(*args) 2013-11-01 15:07:09.395 | File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default 2013-11-01 15:07:09.395 | raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) 2013-11-01 15:07:09.396 | HTTPError: HTTP Error 500: Internal Server Error 2013-11-01 15:07:09.396 | 2013-11-01 15:07:09.396 | 2013-11-01 15:07:09.396 | == To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1247198/+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 1247752] Re: Marker could not be found?
** 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/1247752
Title:
Marker could not be found?
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in Python client library for Keystone:
Invalid
Bug description:
I have a problem after grizzly->havana migration where i’m unable to rescue
myself.
When I open the "Admin -> Resource-Usage View i get no results – only a red
error box with the message "Error: Unable to retrieve tenant list.“.
Horizon log:
[Thu Oct 31 11:39:44 2013] [error] Creating a new keystoneclient connection
to http://$controller:35357/v2.0.
[Thu Oct 31 11:39:44 2013] [error] REQ: curl -i -X GET
http://$controller:35357/v2.0/tenants?marker=tenant_marker&limit=21 -H
"User-Agent: python-keystoneclient" -H "Forwarded:
for=131.234.5.178;by=python-keystoneclient" -H "X-Auth-Token: 82[…]f46"
[Thu Oct 31 11:39:44 2013] [error] REQ: curl -i -X GET
http://$controller:35357/v2.0/tenants?marker=tenant_marker&limit=21 -H
"User-Agent: python-keystoneclient" -H "Forwarded:
for=131.234.5.178;by=python-keystoneclient" -H "X-Auth-Token: 82[…]46"
[Thu Oct 31 11:39:44 2013] [error] INFO:urllib3.connectionpool:Starting new
HTTP connection (1): $controller
[Thu Oct 31 11:39:44 2013] [error] DEBUG:urllib3.connectionpool:"GET
/v2.0/tenants?marker=tenant_marker&limit=21 HTTP/1.1" 400 88
[Thu Oct 31 11:39:44 2013] [error] RESP: [400] CaseInsensitiveDict({'date':
'Thu, 31 Oct 2013 11:39:47 GMT', 'vary': 'X-Auth-Token', 'content-length':
'88', 'content-type': 'application/json'})
[Thu Oct 31 11:39:44 2013] [error] RESP BODY: {"error": {"message": "Marker
could not be found", "code": 400, "title": "Bad Request"}}
[Thu Oct 31 11:39:44 2013] [error]
[Thu Oct 31 11:39:44 2013] [error] RESP: [400] CaseInsensitiveDict({'date':
'Thu, 31 Oct 2013 11:39:47 GMT', 'vary': 'X-Auth-Token', 'content-length':
'88', 'content-type': 'application/json'})
[Thu Oct 31 11:39:44 2013] [error] RESP BODY: {"error": {"message": "Marker
could not be found", "code": 400, "title": "Bad Request"}}
[Thu Oct 31 11:39:44 2013] [error]
[Thu Oct 31 11:39:44 2013] [error] Request returned failure status: 400
[Thu Oct 31 11:39:44 2013] [error] Request returned failure status: 400
[Thu Oct 31 11:39:44 2013] [error] Recoverable error: Marker could not be
found (HTTP 400)
Keystone Log:
2013-10-31 12:39:47.352 17187 DEBUG routes.middleware [-] Matched GET
/tenants __call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:100
2013-10-31 12:39:47.352 17187 DEBUG routes.middleware [-] Route path:
'{path_info:.*}', defaults: {'controller':
} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
2013-10-31 12:39:47.352 17187 DEBUG routes.middleware [-] Match dict:
{'controller': ,
'path_info': '/tenants'} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:103
2013-10-31 12:39:47.353 17187 DEBUG routes.middleware [-] Matched GET
/tenants __call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:100
2013-10-31 12:39:47.353 17187 DEBUG routes.middleware [-] Route path:
'{path_info:.*}', defaults: {'controller':
} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
2013-10-31 12:39:47.353 17187 DEBUG routes.middleware [-] Match dict:
{'controller': ,
'path_info': '/tenants'} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:103
2013-10-31 12:39:47.354 17187 DEBUG routes.middleware [-] Matched GET
/tenants __call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:100
2013-10-31 12:39:47.354 17187 DEBUG routes.middleware [-] Route path:
'{path_info:.*}', defaults: {'controller':
} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
2013-10-31 12:39:47.355 17187 DEBUG routes.middleware [-] Match dict:
{'controller': , 'path_info': '/tenants'} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:103
2013-10-31 12:39:47.355 17187 DEBUG routes.middleware [-] Matched GET
/tenants __call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:100
2013-10-31 12:39:47.355 17187 DEBUG routes.middleware [-] Route path:
'{path_info:.*}', defaults: {'controller':
} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
2013-10-31 12:39:47.356 17187 DEBUG routes.middleware [-] Match dict:
{'controller': ,
'path_info': '/tenants'} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:103
2013-10-31 12:39:47.356 17187 DEBUG routes.middleware [-] Matched GET
/tenants __call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:100
2013-10-31 12:39:47.357 17187 DEBUG routes.middleware [-] Route path:
'/tenants', defaults: {'action': u'get_all_projects', 'controller':
} __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
2013-10-31
[Yahoo-eng-team] [Bug 1236681] Re: ObjectDetailView downloads the entire object
** 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/1236681
Title:
ObjectDetailView downloads the entire object
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
This view uses the swift_get_object method, which gets the entire
object, including the data. It should be using HEAD instead. The
object size is in the content-length header.
openstack_dashboard/dashboards/project/containers/views.py:
251 class ObjectDetailView(forms.ModalFormMixin, generic.TemplateView):
252 template_name = 'project/containers/object_detail.html'
253
254 def get_object(self):
255 if not hasattr(self, "_object"):
256 try:
257 self._object = api.swift.swift_get_object(
258 self.request,
259 self.kwargs["container_name"],
260 self.kwargs["object_path"])
261 print self._object.data
262 except Exception:
263 redirect = reverse("horizon:project:containers:index")
264 exceptions.handle(self.request,
265 _('Unable to retrieve details.'),
266 redirect=redirect)
267 return self._object
openstack_dashboard/api/swift.py:
253 def swift_get_object(request, container_name, object_name):
254 headers, data = swift_api(request).get_object(container_name,
object_name)
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1236681/+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 1236168] Re: Show an error message on instance launch error
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1236168 Title: Show an error message on instance launch error Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Since instance creation happens asynchronously, all that currently happens on the Horizon side when an instance launch fails is the state changes from Creating to Error. There's an instance.fault field we could be looking at to give more information to the user about what went wrong. As a first step we could show a regular red error message popup when an Ajax request finds an instance in the ERROR state. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1236168/+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 1237377] Re: LBaaS. HealthMonitor representation should be improved
** 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/1237377 Title: LBaaS. HealthMonitor representation should be improved Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: In Progress Bug description: When associating HealthMonitor to a Pool, theu user needs to select the HealthMonitor from a list. In this list the HealthMonitor is repesented by its UUID. This is not very informative .. We need to improve the HealthMonitor representaion and use some of the HealthMonitor attributes instead of the UUID. See the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1237377/+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 1236621] Re: Disable H803: git commit title should not end with period
** 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/1236621 Title: Disable H803: git commit title should not end with period Status in OpenStack Hacking Guidelines: New Status in OpenStack Dashboard (Horizon): Fix Released Bug description: I think it's a total waste of reviewing time and gating resources for patches to be failing because of a period at the end of a commit title. This makes no difference at all to readability. I propose we disable the check. See here for an example: https://review.openstack.org/#/c/50167 To manage notifications about this bug go to: https://bugs.launchpad.net/hacking/+bug/1236621/+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 1211470] Re: overview landing page produces error if nova extension SimpleTenantUsage is not enabled
** 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/1211470 Title: overview landing page produces error if nova extension SimpleTenantUsage is not enabled Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The initial landing page produces error messages when the nova extension "SimpleTenantUsage" is not enabled. http://docs.openstack.org/developer/nova/api/nova.api.openstack.compute.contrib.simple_tenant_usage.html To fix this, horizon should call the extension_supported() function to determine if a call should be made. A couple of options would be possible once this call is made: 1) show no data in the table, no extra messages 2) show no data in the table, possibly an info message that this information is not available 3) hide the table, just leaving the graphs from the limits call To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1211470/+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 1173870] Re: Error when deleting an attached volume not surfaced well
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1173870 Title: Error when deleting an attached volume not surfaced well Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When deleting a volume that status must be available or error. However when trying to delete a volume with status 'in-use' using the dashboard The error is : "Error: You do not have permission to delete volume: " which is incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1173870/+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 1196541] Re: Docs update: simple_ip_management doesn't work with Quantum
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1196541 Title: Docs update: simple_ip_management doesn't work with Quantum Status in OpenStack Dashboard (Horizon): Fix Released Bug description: At the moment, simple_ip_management is not compatible with Neutron. https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/quantum.py#L197 The comment besides it suggest it may be possible to enable under certain conditions, however this is not the case at the moment. We should update the documentation page at http://docs.openstack.org/developer/horizon/topics/settings.html #simple-ip-management so it becomes clearer that simple_ip_management is not expected to work with Neutron at this stage. Perhaps another bug should also be opened to track the work required to get it working. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1196541/+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 1195500] Re: quota/limit graphs don't work in IE 9
** 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/1195500 Title: quota/limit graphs don't work in IE 9 Status in OpenStack Dashboard (Horizon): Fix Released Bug description: On the project/overview page there is a javascript error: SCRIPT5007: Unable to get property 'used' of undefined or null reference b3e0be1a9529.js, line 239 character 329 pointing to for(var i=0;ihttps://bugs.launchpad.net/horizon/+bug/1195500/+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 1208734] target
affects heat status fixreleased ** Changed in: heat 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/1208734 Title: Drop openstack.common.exception Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in Cinder: Fix Released Status in Orchestration API (Heat): Fix Released Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Neutron: Fix Committed Status in OpenStack Data Processing (Savanna): In Progress Status in Taskflow for task-oriented systems.: Fix Committed Bug description: The library openstack.common.exceptions is deprecated in Oslo and should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1208734/+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 1207770] Re: Standardize name display on detail pages for instance, volume and image
** 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/1207770 Title: Standardize name display on detail pages for instance, volume and image Status in OpenStack Dashboard (Horizon): Fix Released Bug description: This appearance is different from Instances and Images. On the Volume Detail page, the Volume Overview header contains the name of the volume against is, like so: "Volume Overview: testvol" In my opinion , there is no need to display the name on the "Volume Overview: " header as the name is already specified in the Info section. This is how the Instance Detail and Image Detail To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1207770/+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 1178103] Re: can't disable file injection for bare metal
** Changed in: nova 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/1178103 Title: can't disable file injection for bare metal Status in Ironic (Bare Metal Provisioning): Triaged Status in OpenStack Compute (Nova): Fix Released Status in tripleo - openstack on openstack: Fix Released Bug description: For two reasons : a) until we have quantum-pxe done, it won't work, and b) file injection always happens. One of the reasons to want to disable file injection is to work with hardware that gets a ethernet interface other than 'eth0' - e.g. if only eth1 is plugged in on the hardware, file injection with it's hardcoded parameters interferes with network bringup. A workaround for homogeneous environments is to change the template to hardcode the interface name (s/iface.name/eth2/) To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1178103/+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 1187576] Re: Need a Selenium javascript sanity test
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1187576 Title: Need a Selenium javascript sanity test Status in OpenStack Dashboard (Horizon): Fix Released Bug description: There have been more than one occasion where javascript python- compression has been broken when new libraries are included. There needs to be a better javascript sanity test to verify that core behavior still works. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1187576/+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 1257030] Re: Increase Keypair name size to 255
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1257030 Title: Increase Keypair name size to 255 Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The keypair name in horizon has a max_length of 20 characters, it seems short. We should just match the nova data model length, and set the max_length to 255 for consistency. Link to nova code: https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L721 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1257030/+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 1256756] Re: No parse_isotime filter added to Image created and updated date strings.
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1256756 Title: No parse_isotime filter added to Image created and updated date strings. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: No parse_isotime filter added to Image created and updated date strings. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1256756/+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 1255004] Re: I18n: Localization of the role "Member"
** 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/1255004 Title: I18n: Localization of the role "Member" Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: In Progress Status in OpenStack I18n & L10n: New Bug description: Hi, There is a very strange thing happened to role "Member" when I set Horizon to use my local language. In the dialog "Domain Groups", it is translated. But in the dialog of "Project Members" and "Project Groups", it is not translated. From my point of view, if we can localize role names, it will be wonderful. If we are not able to localize role names, it is acceptable. But we need to make them consistent. Hope somebody can take a look at this interested issue. Thanks. Daisy To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1255004/+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 1254026] Re: Subnet / Subnet details not marked as translatable
** 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/1254026 Title: Subnet / Subnet details not marked as translatable Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: Fix Committed Bug description: When trying to create or update a subnet from the Networks details page, the tab titles 'Subnet' and 'Subnet details' are not showing as translated. This is because when defining the names, the leading underscore were missed in several places in order to mark the string as translatable, cf. https://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/dashboards/project/networks/subnets/workflows.py Steps to reproduce: 1. On the left side panel, select the Networks menu. 2. Click on a network name to open the Network Details page. 3. Click the "Create Subnet" or "Edit Subnet" button and check the tabs To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1254026/+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 1254484] Re: Meaningless name "NT_*" in network topology tables
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1254484 Title: Meaningless name "NT_*" in network topology tables Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Tables in network topology have names with prefix "NT_*". The table names in network topology are not visible to end users and there is no need to use different names from normal tables. It is confusing to translators too. I would suggest to remove "NT_" prefix from network topology tables. openstack_dashboard/dashboards/project/network_topology/instances/tables.py openstack_dashboard/dashboards/project/network_topology/ports/tables.py openstack_dashboard/dashboards/project/network_topology/routers/tables.py To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1254484/+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 1254985] Re: "Edit subnet" & "Update subnet"
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1254985 Title: "Edit subnet" & "Update subnet" Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Hi. In the page of "Network Detail", there is a table to list all subnets. In this table, there is a button in every row to "Edit Subnet". When I click "Edit Subnet", there will be a dialog shown with title "Update Subnet." But in other tables, like network table or port table, clicking "Edit Network" will promote a dialog with title "Edit Network"; clicking "Edit Port" will promote a dialog with title "Edit Port". So I think, "Edit Subnet" will promote a dialog with title "Edit Subnet". We should change "Update Subnet" to "Edit Subnet" Regards Daisy To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1254985/+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 1254212] Re: Heat Stack name not validated
** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Milestone: None => icehouse-1 -- 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/1254212 Title: Heat Stack name not validated Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When creating a new stack, if the name does not start with [a-zA-Z] the creation fails with a generic message. Ideally, we should add the same regexp used in Heat into the form to avoid an extra request just to fail and improve the error message. Steps: 1) Stack 2) Create Stack ( use minimum template example ) 3) Name: _Stack or _Stack or ...Stack To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1254212/+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 1254049] Re: English string for "Injected File Path Bytes" is wrong
** 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/1254049 Title: English string for "Injected File Path Bytes" is wrong Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Dashboard (Horizon) havana series: In Progress Bug description: It looks like the string for injected_file_path_bytes was accidentally copied over from the Injected File Content Bytes, leading to a confusing display in the Default Quotas page where the injected file content bytes limit reads as both 10240 and 255. The fix will be safe to backport for other languages too, as translation for the correct string is already available. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1254049/+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 1229671] Re: Deploy instances failed on Hyper-V with Chinese locale
** Changed in: nova 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/1229671 Title: Deploy instances failed on Hyper-V with Chinese locale Status in OpenStack Compute (Nova): Fix Released Bug description: I am deploying instances on my Hyper-V host but I met the below error. I remember in the past, vmops.py calls vhdutils.py but now it calls vhdutilsv2.py. Not sure if that is the correct place that caused this issue. Please help to check. 2013-09-24 18:46:47.079 2304 WARNING nova.network.neutronv2.api [-] [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] No network configured! 2013-09-24 18:46:47.734 2304 INFO nova.virt.hyperv.vmops [req-474eb715-9048-475f-9734-7b5fdc005a64 b13861ca49f641d7a818e6b8335f2351 29db386367fa4c4e9ffb3c369a46ee90] [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] Spawning new instance 2013-09-24 18:46:49.996 2304 ERROR nova.compute.manager [req-474eb715-9048-475f-9734-7b5fdc005a64 b13861ca49f641d7a818e6b8335f2351 29db386367fa4c4e9ffb3c369a46ee90] [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] Instance failed to spawn 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] Traceback (most recent call last): 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\compute\manager.py", line 1431, in _spawn 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] block_device_info) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\driver.py", line 55, in spawn 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] admin_password, network_info, block_device_info) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 90, in wrapper 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] return function(self, *args, **kwds) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 208, in spawn 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] root_vhd_path = self._create_root_vhd(context, instance) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 177, in _create_root_vhd 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] self._pathutils.remove(root_vhd_path) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 161, in _create_root_vhd 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] base_vhd_info = self._vhdutils.get_vhd_info(base_vhd_path) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vhdutilsv2.py", line 124, in get_vhd_info 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] et = ElementTree.fromstring(vhd_info_xml) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\xml\etree\ElementTree.py", line 1301, in XML 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] parser.feed(text) 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] File "C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\xml\etree\ElementTree.py", line 1641, in feed 2013-09-24 18:46:49.996 2304 TRACE nova.compute.manager [instance: 973ff9d0-fb57-4ca6-a3ba-7b08783bcb9f] self._
