[Yahoo-eng-team] [Bug 1225099] Re: Encoding hard-coded in gettextutils.Message
** Changed in: oslo 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/1225099 Title: Encoding hard-coded in gettextutils.Message Status in Ceilometer: In Progress Status in Cinder: In Progress Status in Orchestration API (Heat): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: The __str__ method in openstack.common.gettextutils.Message is hard- coded to encode to utf-8 which creates problems when other logic goes to decode the string using the default encoding, e.g. when formatting log messages. Message objects with double-byte translations fail to log because of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1225099/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229204] Re: Output for live migration corrupted
** Changed in: oslo
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/1229204
Title:
Output for live migration corrupted
Status in OpenStack Compute (Nova):
Fix Committed
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Bug description:
When performing live migration to the same host the following output
is received:
nicira@os-devstack:~$ nova --os-tenant-name demo live-migration Y os-devstack
ERROR: [u'U', u'n', u'a', u'b', u'l', u'e', u' ', u't', u'o', u' ', u'm',
u'i', u'g', u'r', u'a', u't', u'e', u' ', u'i', u'n', u's', u't', u'a', u'n',
u'c', u'e', u' ', u'(', u'b', u'd', u'7', u'5', u'6', u'1', u'3', u'5', u'-',
u'4', u'5', u'9', u'1', u'-', u'4', u'5', u'5', u'c', u'-', u'a', u'd', u'f',
u'8', u'-', u'c', u'7', u'f', u'a', u'3', u'e', u'8', u'5', u'4', u'4', u'3',
u'1', u')', u' ', u't', u'o', u' ', u'c', u'u', u'r', u'r', u'e', u'n', u't',
u' ', u'h', u'o', u's', u't', u' ', u'(', u'o', u's', u'-', u'd', u'e', u'v',
u's', u't', u'a', u'c', u'k', u')', u'.'] (HTTP 400) (Request-ID:
req-0c12766b-3c0a-4b8b-98bc-aebbb77cdf99)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1229204/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : 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: oslo 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/1182861 Title: Switch to oslo.config 1.2.0 final Status in Ceilometer: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Message Queuing Service (Marconi): Fix Committed 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 Released Status in Python client library for Keystone: Fix Committed Status in Trove - Database as a Service: Fix Committed 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 1226374] Re: misused assertTrue in unit tests
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1226374 Title: misused assertTrue in unit tests Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Orchestration API (Heat): Fix Committed Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Identity (Keystone): Fix Committed Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Keystone: Fix Committed Status in OpenStack Object Storage (Swift): Fix Committed Status in Tempest: Fix Committed Bug description: 1)signature for assertTure: def failUnless(self, expr, msg=None): Fail the test unless the expression is true. if not expr: raise self.failureException, msg assert_ = assertTrue = failUnless 2) signature for assertEqual: def failUnlessEqual(self, first, second, msg=None): Fail if the two objects are unequal as determined by the '==' operator. if not first == second: raise self.failureException, \ (msg or '%r != %r' % (first, second)) ... assertEqual = assertEquals = failUnlessEqual assertTrue used to evaluate one expression assertEqual used to compare two expressions If passed two expressions to assertTrue , it always evaluate first expression . That 's not expected . To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1226374/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1227019] Re: Error with run_tests.sh: Invalid version of six installed
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = havana-rc1 -- 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/1227019 Title: Error with run_tests.sh: Invalid version of six installed Status in OpenStack Compute (Nova): Fix Committed Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: run_tests.sh installs+upgrades the requirements from requirements.txt followed by doing the same for test-requirements.txt test_requirements.txt does not have an upper bound on six and therefore upgrades it beyond the version permitted in requirements.txt. tox installs+upgrades for both files at the same time rather than in serial, therefore identifies a version of six that satisfies all of the requirements. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1227019/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229475] Re: terminate_instance(): RuntimeError: Second simultaneous read on fileno 16 detected
No need for a nova patch ** Changed in: nova Status: Triaged = In Progress ** Changed in: nova Status: In Progress = Invalid ** No longer affects: oslo -- 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/1229475 Title: terminate_instance(): RuntimeError: Second simultaneous read on fileno 16 detected Status in OpenStack Compute (Nova): Invalid Status in Python client library for Neutron: In Progress Bug description: http://logs.openstack.org/59/47659/6/check/gate-tempest-devstack-vm- neutron/fc83d44/logs/screen-n-cpu.txt.gz#_2013-09-23_18_25_06_484 2013-09-23 18:25:06.484 ERROR nova.openstack.common.rpc.amqp [req-3a80ff5a-817b-4eb8-be67-7f180bef8a6e demo demo] Exception during message handling 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/openstack/common/rpc/amqp.py, line 461, in _process_data 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp **args) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/openstack/common/rpc/dispatcher.py, line 172, in dispatch 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 354, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/exception.py, line 90, in wrapped 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp payload) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/exception.py, line 73, in wrapped 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return f(self, context, *args, **kw) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 244, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp pass 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 230, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 295, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 272, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp e, sys.exc_info()) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 259, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1793, in terminate_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp do_terminate_instance(instance, bdms) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/openstack/common/lockutils.py, line 246, in inner 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return f(*args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1785, in do_terminate_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp reservations=reservations) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/hooks.py, line 105, in inner 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp rv = f(*args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1758, in _delete_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp user_id=user_id) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1727, in _delete_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp
[Yahoo-eng-team] [Bug 1231709] Re: oauth controller calls are not protected
** 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/1231709 Title: oauth controller calls are not protected Status in OpenStack Identity (Keystone): Fix Released Bug description: It's open season for the oauth controllers, and anyone can call anything they want. None of the controllers are protected. The policy.json file needs to be updated accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1231709/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1226225] Re: v2 token cache not correctly invalidated when using Belongs To
** 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/1226225 Title: v2 token cache not correctly invalidated when using Belongs To Status in OpenStack Identity (Keystone): Fix Released Bug description: v2 token deletion and validation methods take an optional belongs_to parameter, which is the tenant. Due to how sensitive the dogpile caching is on the parameters to validate_token, this can lead to problems where a token cache is not correctly cleared, for example, the following (pseudo test) will fail: - create a scoped token for a user to a project - check the token is valid, just using the token ID (without passing in belongs_to).[this sets the cache] - delete the token using the driver function delete_tokens, passing in user and tenant - check if token is still valid, just using token ID (it will be return successfully from the cache - which is incorrect) - check if token is still valid, token ID and tenant ID (it will not be found - which is correct) The problem is in invalidate_individual_token_cache in the token provider, which already tries to handle the case of invalidating a token with and without a belongs_to tenantbut doesn't catch the case when dogpile has cached the key as tokenID, None as the parameters. Thanks to morganfainberg for his help in debugging the above. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1226225/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1226475] Re: Update user v2.0 does not automatically assign user on new tenantId
** 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/1226475 Title: Update user v2.0 does not automatically assign user on new tenantId Status in OpenStack Identity (Keystone): Fix Released Bug description: Updating a user's tenantId doesn't assign the user automatically on the new tenant. Even if the tenantId is null before the update, the user is still not assigned. On create user, the new user is automatically assigned to the tenant when the tenantId is provided. Ref: http://docs.openstack.org/api/openstack-identity-service/2.0/content/POST_updateUser_v2.0_users__userId__.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1226475/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1231772] Re: Cannot create a user with LDAP backend
** 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/1231772
Title:
Cannot create a user with LDAP backend
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When running Keystone with the LDAP identity backend, creating a user
fails with 400 and must be string, not None
Set up devstack to use LDAP.
While devstack is running commands fail, like this:
keystone user-create --name=nova --pass=mypwd --tenant_id
948d57ba2523423e96ca2f98c29973a8 --email=n...@example.com
Here's the error in the Keystone log:
(keystone.common.ldap.core): 2013-09-26 21:10:35,701 DEBUG core add_s
LDAP add:
dn=cn=591959d3f2cd42d09230789af9504e12,ou=Users,dc=openstack,dc=org,
attrs=[('objectClass', ['person', 'inetOrgPerson']), ('sn', ['nova']),
('userPassword', ['']), (None,
['948d57ba2523423e96ca2f98c29973a8'])]
(keystone.common.wsgi): 2013-09-26 21:10:35,702 ERROR wsgi __call__ must be
string, not None
Traceback (most recent call last):
File /opt/stack/keystone/keystone/common/wsgi.py, line 238, in __call__
result = method(context, **params)
File /opt/stack/keystone/keystone/identity/controllers.py, line 214, in
create_user
self.identity_api.create_user(user_id, user_ref))
File /opt/stack/keystone/keystone/notifications.py, line 44, in wrapper
result = f(*args, **kwargs)
File /opt/stack/keystone/keystone/identity/core.py, line 177, in wrapper
return f(self, *args, **kwargs)
File /opt/stack/keystone/keystone/identity/core.py, line 322, in
create_user
ref = driver.create_user(user_id, user)
File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 95, in
create_user
user_ref = self.user.create(user)
File /opt/stack/keystone/keystone/identity/backends/ldap.py, line 229, in
create
values = super(UserApi, self).create(values)
File /opt/stack/keystone/keystone/common/ldap/core.py, line 730, in create
return super(EnabledEmuMixIn, self).create(values)
File /opt/stack/keystone/keystone/common/ldap/core.py, line 328, in create
conn.add_s(self._id_to_dn(values['id']), attrs)
File /opt/stack/keystone/keystone/common/ldap/core.py, line 551, in add_s
return self.conn.add_s(dn, ldap_attrs)
File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 193, in
add_s
msgid = self.add(dn,modlist)
File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 190, in add
return self.add_ext(dn,modlist,None,None)
File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 176, in
add_ext
return
self._ldap_call(self._l.add_ext,dn,modlist,EncodeControlTuples(serverctrls),EncodeControlTuples(clientctrls))
File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 96, in
_ldap_call
result = func(*args,**kwargs)
TypeError: must be string, not None
Also, the error should be 500 Internal Server Error and not 400 Bad Request.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1231772/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233228] Re: Last translations refresh before RC1
** 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/1233228 Title: Last translations refresh before RC1 Status in Ceilometer: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Bug description: Before issuing RC1 we need to refresh translations. Those are automatically proposed and can be found at https://review.openstack.org/#/q/topic:transifex/translations,n,z To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1233228/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1227980] Re: Pluggable auth provider: Can't write a custom plugin due to hardcoded check
** 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/1227980
Title:
Pluggable auth provider: Can't write a custom plugin due to hardcoded
check
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Provider plugin provides an interface so that some one customize or
rewrite UUID and PKI providers. But unfortunately there is a hard
coded check which prevents pluggablity
provider.py -- get_provider
if ((CONF.signing.token_format == 'PKI' and
CONF.token.provider != PKI_PROVIDER or
(CONF.signing.token_format == 'UUID' and
CONF.token.provider != UUID_PROVIDER))):
raise exception.UnexpectedError(
_('keystone.conf [signing] token_format (deprecated) '
'conflicts with keystone.conf [token] provider'))
return CONF.token.provider
PKI_PROVIDER and UUID_PROVIDERS are global variable which hold default
provider. Do we need this check?
Ofcourse, I can change the value of the global variable, but that
doesn't fit the pluggable design.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1227980/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1221808] Re: some API responses which should be translated when using accept-language header are not
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1221808
Title:
some API responses which should be translated when using accept-
language header are not
Status in Cinder:
Fix Committed
Status in Orchestration API (Heat):
Fix Committed
Status in OpenStack Identity (Keystone):
Fix Released
Status in OpenStack Neutron (virtual network service):
Fix Committed
Bug description:
1. Update cinder.po file
# vim /usr/lib/python2.6/site-packages/cinder/locale/ja/LC_MESSAGES/cinder.po
#: cinder/volume/flows/create_volume.py:301
#, python-format
msgid Volume size %(size)s must be an integer and greater than 0
msgstr memo memo memo memo memo %(size)s memo memo memo memo memo memo memo
memo memo memo memo memo memomemomeo meomeomeomeo 0.
2. Compile new .mo file, install
# msgfmt -o cinder.mo
/usr/lib/python2.6/site-packages/cinder/locale/ja/LC_MESSAGES/cinder.po
# cp cinder.mo /usr/share/locale/ja_JP/LC_MESSAGES/
# cp cinder.mo /usr/share/locale/ja/LC_MESSAGES/
3. Restart cinder services
# service openstack-cinder-volume restart
# service openstack-cinder-scheduler restart
# service openstack-cinder-api restart
4. API call to trigger translated message
# curl -i http://127.0.0.1:8776/v1/89fb0710a5214d3596fb82e09d40fe4e/volumes
-X POST -H X-Auth-Project-Id: service -H User-Agent: python-cinderclient -H
Content-Type: application/json -H Accept: application/json -H
X-Auth-Token: 347ecfadfc2c4783a9fc0f24729eecaa -d '{volume: {status:
creating, availability_zone: null, source_volid: null,
display_description: null, snapshot_id: null, user_id: null, size: 0,
display_name: volumetest, imageRef: null, attach_status: detached,
volume_type: null, project_id: null, metadata: {}}}' -H Accept-Language:
ja
5. Response still in english'
HTTP/1.1 400
Content-Length: 119
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-b71abcbf-9dfb-4d92-8062-6338438c84a4
Date: Tue, 27 Aug 2013 03:21:05 GMT
{badRequest: {message: Invalid input received: Volume size 0 must
be an integer and greater than 0, code: 400}}
6. Update system locale to make sure error message is properly translated
# cat /etc/sysconfig/i18n
LANG=ja_JP.UTF-8
#LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16
7. Restart servers
# service openstack-cinder-volume restart
# service openstack-cinder-scheduler restart
# service openstack-cinder-api restart
8. Response is partial translated.
[root@localhost locale]# curl -i
http://127.0.0.1:8776/v1/89fb0710a5214d3596fb82e09d40fe4e/volumes -X POST -H
X-Auth-Project-Id: service -H User-Agent: python-cinderclient -H
Content-Type: application/json -H Accept: application/json -H
X-Auth-Token: 347ecfadfc2c4783a9fc0f24729eecaa -d '{volume: {status:
creating, availability_zone: null, source_volid: null,
display_description: null, snapshot_id: null, user_id: null, size: 0,
display_name: volumetest, imageRef: null, attach_status: detached,
volume_type: null, project_id: null, metadata: {}}}' -H Accept-Language:
ja
HTTP/1.1 400
Content-Length: 182
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-49be059a-8e6a-4922-9349-e51028725f26
Date: Tue, 27 Aug 2013 03:28:00 GMT
{badRequest: {message: Invalid input received: memo memo memo
memo memo 0 memo memo memo memo memo memo memo memo memo memo memo
memo memomemomeo meomeomeomeo 0., code: 400}}
9. Expected results:
The response in message should be translated without changing system local
to ja
10. Actual results:
The response in message has not translated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1221808/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1224565] Re: Can't establish qpid connection with impl_qpid.py
** 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/1224565 Title: Can't establish qpid connection with impl_qpid.py Status in OpenStack Identity (Keystone): Fix Released Bug description: The notifier module from Oslo has been sync'd with Keystone and is being used to deliver notifications using the log_notifier and rpc_notifier. By default the rpc_backend is impl_kombu.py and I can verify the notifications arrive on the queue. When using impl_qpid as the rpc_backend and sending a notification, the process hangs attempting to establish a connection with qpid. Steps to reproduce: 1.) Update keystone.conf to send notifications # === NOTIFICATIONS = notification_driver = keystone.openstack.common.notifier.rpc_notifier rpc_backend = keystone.openstack.common.rpc.impl_qpid 2.) restart Keystone 3.) create/update/delete project or a user (both resources will send a notification) $ keystone tenant-create --name my_project After setting a break point I have followed the call in to qpid code before it hangs. I am not sure if the problem here lies in impl_qpid or possibly something with qpid code. I have been able to reproduce this on qpid 0.20 and 0.22. The following is a trace with pdb included: http://paste.openstack.org/show/46886/ I've tried this using config options for qpid username and password and leaving them as default, neither work for establishing a connection. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1224565/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1209440] Re: LDAP identity still allows setting domain via attribute
** 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/1209440 Title: LDAP identity still allows setting domain via attribute Status in OpenStack Identity (Keystone): Fix Released Bug description: At keystone/identity/backends/ldap.py:230 we allow mapping domain_id of a user based on the attribute specified in conf.ldap.user_domain_id_attribute which defaults to 'businessCategory'. My understanding is that this is no longer required and should no longer be allowed and indeed in practice it completely overrides any domain information that is provided in the authentication body. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1209440/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220945] Re: Create user with LDAP enabled_mask, enabled not boolean
** 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/1220945
Title:
Create user with LDAP enabled_mask, enabled not boolean
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When set up Keystone to use the LDAP identity backend and set
user_enabled_mask to non-zero and then create a user with enabled
set to 'false', the enabled value comes back as a number rather than
a boolean. This is unexpected because the SQL backend always returns a
boolean.
Here's an example:
$ curl -s \
-H X-Auth-Token: $TOKEN \
-H Content-Type: application/json \
--data '{user: {name: blk-test1, enabled: false}}' \
http://localhost:35357/v3/users | python -mjson.tool
{
user: {
domain_id: default,
enabled: 514,
id: e5d09e0ff7944b28b151865ed6b300ba,
links: {
self:
http://192.168.122.176:5000/v3/users/e5d09e0ff7944b28b151865ed6b300ba;
},
name: blk-test1
}
}
-- enabled should be false and not 514.
Here's the output when use the SQL identity backend:
{
user: {
domain_id: default,
enabled: false,
id: 73734048e27545f185e2a37eda08f593,
links: {
self:
http://192.168.122.176:5000/v3/users/73734048e27545f185e2a37eda08f593;
},
name: blk-test1
}
}
To recreate, set in keystone.conf.sample:
user_enabled_attribute = employeeType
user_enabled_mask = 2
user_enabled_default = 512
Next,
change devstack to not set enabled in lib/keystone,
configure localrc to use LDAP,
start devstack,
and then run the curl command above.
Note that when do an update, the enabled value is a Boolean and the
enabled_nomask value is returned:
curl -s \
-X PATCH \
-H X-Auth-Token: $TOKEN \
-H Content-Type: application/json \
--data '{user: {enabled: false}}' \
http://localhost:35357/v3/users/$USER_ID | python -mjson.tool
{
user: {
domain_id: default,
enabled: true,
enabled_nomask: 512,
id: 4c6aebecf60e441dbbdb678405d4f5ab,
links: {
self:
http://192.168.122.176:5000/v3/users/4c6aebecf60e441dbbdb678405d4f5ab;
},
name: demo
}
}
Creating a user should probably work similarly to this, although I
don't see how the enabled_nomask value is useful to anyone.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1220945/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1221889] Re: Invalid X-Subject-Token results in HTTP 401 rather than 404
** 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/1221889
Title:
Invalid X-Subject-Token results in HTTP 401 rather than 404
Status in OpenStack Identity (Keystone):
Fix Released
Status in Tempest:
In Progress
Bug description:
While fixing https://bugs.launchpad.net/keystone/+bug/1186059 I observed that
lots of unit tests related to V3 head test is not correct.
e.g. all the below unit test try to make a head call after deleting/revoking
x-subject-token and assumes that it will be unauthorized.
self.head('/auth/tokens', headers={'X-Subject-Token': token2},
expected_status=401)
In reality the above call creates another scoped token and auth passed with
the new token, in that case 401 is not a correct test it should be 404 which is
also aligned with docs
https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3.md#403-forbidden.
test_deleting_group_grant_revokes_tokens
(keystone.tests.test_v3_auth.TestTokenRevoking)
test_deleting_project_revokes_token
(keystone.tests.test_v3_auth.TestTokenRevoking)
test_deleting_user_grant_revokes_token
(keystone.tests.test_v3_auth.TestTokenRevoking)
test_disabling_project_revokes_token
(keystone.tests.test_v3_auth.TestTokenRevoking)
test_group_membership_changes_revokes_token
(keystone.tests.test_v3_auth.TestTokenRevoking)
test_removing_role_assignment_does_not_affect_other_users
(keystone.tests.test_v3_auth.TestTokenRevoking)
I found this issue with lots of V3 token related tests but as per
Morgan Fainberg (morganfainberg) this also affecting V2 auth unit
tests.
I am trying to fix V3 auth unit test issue as part of
https://bugs.launchpad.net/keystone/+bug/1186059
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1221889/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1219739] Re: Inconsistent use of tenant_id, tenantId, default_project_id across identity drivers for the User object/ref
** 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/1219739 Title: Inconsistent use of tenant_id, tenantId, default_project_id across identity drivers for the User object/ref Status in OpenStack Identity (Keystone): Fix Released Bug description: When LDAP backend is configured, keystone user-get user-id can *NOT* display 'tanantId'. I looked up the code, user in LDAP dose not have attribute tenantId, but it has an attribute named tenant_id. This problem blocks us. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1219739/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1210515] Re: keystone chokes on empty description field in active directory
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1210515 Title: keystone chokes on empty description field in active directory Status in OpenStack Identity (Keystone): Fix Released Bug description: I configured keystone (from grizzly) with an active directory backend, following https://wiki.openstack.org/wiki/HowtoIntegrateKeystonewithAD. It works so far. Now I can create projects in horizon (tenants in keystone) with an empty description field. The result is that there is no attribute description for that tenant in AD. When I then try to edit such a project (e.g. add description, or add member), I get an Error: Unable to modify project test02. message from horizon, and in keystone.log I see 2013-08-09 15:07:23ERROR [root] u'description' Traceback (most recent call last): File /usr/lib/python2.6/site-packages/keystone/common/wsgi.py, line 236, in __call__ result = method(context, **params) File /usr/lib/python2.6/site-packages/keystone/identity/controllers.py, line 115, in update_project context, tenant_id, clean_tenant) File /usr/lib/python2.6/site-packages/keystone/common/manager.py, line 47, in _wrapper return f(*args, **kw) File /usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py, line 229, in update_project return self._set_default_domain(self.project.update(tenant_id, tenant)) File /usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py, line 614, in update return super(ProjectApi, self).update(id, values, old_obj) File /usr/lib/python2.6/site-packages/keystone/common/ldap/core.py, line 586, in update object_id, values, old_obj) File /usr/lib/python2.6/site-packages/keystone/common/ldap/core.py, line 328, in update elif old_obj[k] != v: KeyError: u'description' I can add a description attribute to AD via its ldap interface using ldapmodify. Then I can modify the project without problems. I think keystone should be able to deal with a missing description field if its optional at creation time. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1210515/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214016] Re: CA key and signing key are not really password protected
** 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/1214016
Title:
CA key and signing key are not really password protected
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
OpenSSL offers two methods to protect sensitive cryptographic keys.
1) standard file system permissions on key file
2) encrypting the key file with a password, i.e. PBE (Password Passed
Encryption)
The key management code in keystone/common/openssl.py is confused to
to whether it's encrypting keys or not.
The keystone configuration defines a ssl.ca_password and
signing.ca_password configuration option. These are defined in
keystone/common/config.py and etc/keystone.conf.sample.
However these passwords are never actually used to password protect
any of the keys.
The only use of either of the ca_password variables is a no-op when
the CA self-signed cert is created in
BaseCertificateConfigure.build_ca_cert()
if not file_exists(ca_cert):
self.exec_command('openssl req -new -x509 -extensions v3_ca '
'-passin pass:%(ca_password)s '
'-key %(ca_private_key)s -out %(ca_cert)s '
...
In this instance there is no point in passing in a password to
decrypt the ca_private_key file because the ca_private_key file was
never encrypted to begin with.
The ca_private_key file is created a few lines above with this code:
self.exec_command('openssl genrsa -out %(ca_private_key)s '
'%(key_size)d')
To have applied PBE (Password Based Encryption) to the ca_private_key
the openssl genrsa command would need to have included the -passout
arg (i.e. the password to encrypt the output file with, the output
file is the key) and the encryption method which is either DES,
triple-DES, or IDEA (-des, -des3, or -idea respectively).
The same problems exist with respect to the signing key.
Issue:
The point of protecting a key with a password is to further protect
the key (keys are the most security sensitive components, especially
both the CA and signing key). But using PBE on the keys currently
requires storing the password in a configuration file which can only
be protected by file system permissions. Thus using PBE on keys may
not offer much additional security if the configuration file
containing the key password can be read by an unauthorized user. If an
attacker can read the file containing the password they probably also
can read the key file or visa-versa. On the other hand one more layer
of security doesn't hurt (perhaps the attacker only stole the key file
because it's an obvious target but failed to find or obtain the config
file with the password needed to extract the key from the key file.
As to which PBE scheme to use? DES is too weak. It's too bad AES is
not an option. IDEA is faster and probably stronger than triple-DES
(the patent protection on IDEA just recently expired so there
shouldn't be any licensing issues)
Summary:
The the presence of key passwords in the configuration options gives
the false illusion keys are password protected when in fact they
aren't The only use of the password option in the current code is
meaningless because it's being used to unlock a key file that was
never locked in the first place.
Either the key passwords should be removed (because they aren't
actually used) or they should be used consistently to lock and unlock
the keys.
The security vulnerability is probably just do we want to alert folks
that the key passwords are not actually used? and by extension
grabbing the key file is sufficient to initiate an attack because
you'll have immediate access to the key.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1214016/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1201487] Re: listing projects for a user omits those that only have group related roles
** 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/1201487
Title:
listing projects for a user omits those that only have group related
roles
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
The backend drivers currently support two (very similar) functions:
list_user_projects() and get_projects_for_user(). Both claim to
return the list of projects for which a user has a role on. Neither
take into account roles by virtue of group membership. They are used
in the following ways:
uses list_user_projects() is used by:
- The API GET /users/{user_id}/projects
users get_projects_for_user() is used by
- The diablo GET /users/{user_id}/roleRefs (should we still need to support
this?)
- The API GET/tenants, where you get all projects referenced the user in the
token (weird)
- An unused function the v2 controller (which we should delete)
We should rationalize the above to use a single function in the driver
manager (similar to the way we do get_roles_for_user_and_project() ),
that correctly accounts for any projects for a which a user also has
roles by virtue of group membership.
If the os-inherit extension is installed, the above function should
also take into account roles inherited from the domain.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1201487/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1221087] Re: Memcached token backend should work with any timezone
** 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/1221087
Title:
Memcached token backend should work with any timezone
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
In configuration document, it looks like following configuration are
required with memcache token backend.
- Memcached server's timezone is set to UTC.
- Timezone of both Memcached and Keystone server should be same.
So Keystone server's timezone is also set to UTC.
http://docs.openstack.org/developer/keystone/configuration.html
#memcached-and-system-time
I guess this limitation is caused by incorrect expiration time is set
when tokens are generated.
backends/memcache.py call utils.unixtime() and it calls time.mktime().
time.mktime() return localtime, not UTC, so its value depends on time zone.
In my tests, if keystone server runs with UTC + N (N=1), token
authorization failed.
# run keystone server with UTC+1
env TZ='UTC-1' tools/with_venv.sh bin/keystone-all
# get token
env TZ=UTC tools/with_venv.sh keystone .. token-get
+---+--+
| Property | Value |
+---+--+
| expires | 2013-09-05T08:38:14Z |
| id| fecd5f9e1c1842f0a60d86a07584fca4 |
| tenant_id | 7b1abdb5213a4962bcaf04a7e0881a91 |
| user_id | 03a2d2e23ff94bfa908856d2c1081110 |
+---+--+
# use token
env TZ=UTC curl -H X-Auth-Token:$TOKEN http://localhost:5000/v2.0/tenants
{error: {message: Could not find token,
fecd5f9e1c1842f0a60d86a07584fca4., code: 401, title: Unauthorized}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1221087/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : 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: keystone 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/1182861 Title: Switch to oslo.config 1.2.0 final Status in Ceilometer: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Message Queuing Service (Marconi): Fix Committed 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 Released Status in Python client library for Keystone: Fix Committed Status in Trove - Database as a Service: Fix Committed 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 1153645] Re: Deleting a role should revoke any tokens associated with it
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1153645 Title: Deleting a role should revoke any tokens associated with it Status in OpenStack Identity (Keystone): Fix Released Bug description: When we delete a role, we delete all the grants associated with it. Since this is a bit like an enforced revoking of user/groups grants, we should invalidate any tokens: - for users that have had any grant using this role - for users of any group that has had a grant using this role To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1153645/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1172164] Re: Ldap server down error in logs
** 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/1172164
Title:
Ldap server down error in logs
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
We are experiencing some errors in authentication and looking into the
logs we discover ldap server down messages from time to time in the
keystone log.
DEBUG Trace in keystone.log
2013-04-09 06:44:03 ERROR [root]
{'desc': Can't contact LDAP server}
Traceback (most recent call last):
File /usr/lib/python2.6/site-packages/keystone/common/wsgi.py, line 204, in
_call_
File /usr/lib/python2.6/site-packages/keystone/service.py, line 317, in
authenticate
File /usr/lib/python2.6/site-packages/keystone/common/manager.py, line 47,
in _wrapper
File
/usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py,
line 99, in authenticate
File
/usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py,
line 175, in get_tenants_for_user
File
/usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py,
line 137, in get_user
File
/usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py,
line 132, in _get_user
File
/usr/lib/python2.6/site-packages/keystone/identity/backends/ldap/core.py,
line 374, in get
File /usr/lib/python2.6/site-packages/keystone/common/ldap/core.py, line
245, in get
File /usr/lib/python2.6/site-packages/keystone/common/ldap/core.py, line
208, in _ldap_get
File /usr/lib/python2.6/site-packages/keystone/common/ldap/core.py, line
134, in get_connection
File /usr/lib/python2.6/site-packages/keystone/common/ldap/core.py, line
354, in simple_bind_s
File /usr/lib64/python2.6/site-packages/ldap/ldapobject.py, line 206, in
simple_bind_s
File /usr/lib64/python2.6/site-packages/ldap/ldapobject.py, line 200, in
simple_bind
File /usr/lib64/python2.6/site-packages/ldap/ldapobject.py, line 96, in
_ldap_call
SERVER_DOWN:
{'desc': Can't contact LDAP server}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1172164/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1201251] Re: issues of updating user via keystone rest api
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1201251
Title:
issues of updating user via keystone rest api
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
We found two problems related to updating user via keystone.
(1) Via, the instruction of updating user on,
http://docs.openstack.org/api/openstack-identity-
service/2.0/content/POST_updateUser_v2.0_users__userId__.html
It is required POST action to update the existing user email, name, or
description.
Via my verification, POST to update existing user caused
{
error: {
message: The resource could not be found.,
code: 404,
title: Not Found
}
}
The detailed for this test is,
[root@lijunj ~]# curl -i
http://localhost:35357/v3/users/fee07a4ebc014744b31564835b715aa1 -X POST -H
Content-Type: application/json -H Accept: application/json -H
X-Auth-Token: ADMIN --data '
{
user: {
id: fee07a4ebc014744b31564835b715aa1,
description: v3 keystone user test,
email: none@,
enabled: true
}
}'
HTTP/1.1 404 Not Found
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 93
Date: Mon, 15 Jul 2013 02:23:44 GMT
{error: {message: The resource could not be found., code: 404,
title: Not Found}}
I ensure the id fee07a4ebc014744b31564835b715aa1 user which is exisitng
already in environment. Below is the output of listing
v3/users/fee07a4ebc014744b31564835b715aa1
--List user
[root@lijunj ~]# curl -i
http://localhost:35357/v3/users/fee07a4ebc014744b31564835b715aa1 -X GET -H
Content-Type: application/json -H Accept: application/json -H
X-Auth-Token: ADMIN
HTTP/1.1 200 OK
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 349
Date: Mon, 15 Jul 2013 02:24:51 GMT
{user: {aa: 12, name: test, bb: 23, debug-
wrongattribute: 12345, cc: 45, enabled: true, links:
{self:
http://localhost:5000/v3/users/fee07a4ebc014744b31564835b715aa1},
id: fee07a4ebc014744b31564835b715aa1, email:
lijun...@cn.ibm.com, debug_wrongattribute: 12345, domain_id:
default, tenantId: }}
The user fee07a4ebc014744b31564835b715aa1 was created for testing.
We may discuss this document correction-ability. And, POST can not be
used for updating user, but PUT action can.
(2) Document in http://docs.openstack.org/ does mention, updating user
can not support to refresh a user tenant id/ project id. And keystone
user-update command is designed not to allow to have any parameter to
refresh tenant-id / project-id of a user. But REST API keeps silent
for any clients attempt to change a existing user tenant id or project
id. From my test verification, in spite of changing successfully
tenant/project id for a existing user, the user still belongs to the
original tenant / project. That means, updating tenant / project id
for a user is invalid.
--Create user
curl -i http://localhost:35357/v2.0/users/ -X POST -H Content-Type:
application/json -H X-Auth-Token: ADMIN --data '
{
user: {
name: li-03,
description: v2.0 keystone user test,
email: none@,
tenantId: ccaf7621482a41ce91d3ee824ff7c959,
password: passw0rd,
enabled: true
}
}'
Response:
{user: {description: v2.0 keystone user test, name: li-03,
enabled: true, email: none@, id: 00027b03821f4b7590a1a94f865a61ff,
tenantId: ccaf7621482a41ce91d3ee824ff7c959}}
-- List the tenant users.
curl -i
http://localhost:35357/v2.0/tenants/ccaf7621482a41ce91d3ee824ff7c959/users -X
GET -H Content-Type: application/json -H X-Auth-Token: ADMIN
{users: [{name: sceagent, id: 07d544b772ce4ab18592d165cea9b8da,
tenantId:
//The content is not important. li-03 is in tenant
ccaf7621482a41ce91d3ee824ff7c959 already.
{name: li-03, description: v2.0 keystone user test, enabled: true,
email: none@, id: 00027b03821f4b7590a1a94f865a61ff, tenantId:
ccaf7621482a41ce91d3ee824ff7c959}]}
--Update user. Used anther tenant id inside, and rest api does not throw
exception.
curl -i http://localhost:35357/v2.0/users/00027b03821f4b7590a1a94f865a61ff -X
PUT -H Content-Type: application/json -H X-Auth-Token: ADMIN --data '
{
user: {
name: li-03,
description: v2.0 keystone user test 01,
email: none@,
tenantId: e0cdb35aa15d45f998c308eb78407513,
password: passw0rd,
enabled: true
}
}'
Response:
{user: {description: v2.0 keystone user test 01, name: li-03,
extra: {tenantId: e0cdb35aa15d45f998c308eb78407513, description: v2.0
keystone user test 01, email: none@}, enabled: true, email: none@,
id: 00027b03821f4b7590a1a94f865a61ff,
[Yahoo-eng-team] [Bug 1233357] Re: tox config can pull in broken sphinx
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1233357 Title: tox config can pull in broken sphinx Status in OpenStack Identity (Keystone): Fix Released Bug description: The latest version of tox supplies the --pre option to pip which 'helpfully' preserves the old behavior of downloading unrequested pre- release versions of things. We wanted to upgrade tox and pip precisely to get the behavior where we want to explicitly ask for pre-release software. A fix is to override the install command in the tox.ini file so that we're explicit in what we want pip to do. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1233357/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233359] Re: Exclude tests dir from coverage reports
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1233359 Title: Exclude tests dir from coverage reports Status in OpenStack Identity (Keystone): Fix Released Bug description: After moving the tests dir into the package, the code itself is getting found by the coverage reports. Of course, coverage reports on test code is silly, so exclude those dirs. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1233359/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233224] Re: Running individual tests in the test suite is failing
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = havana-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1233224
Title:
Running individual tests in the test suite is failing
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Change I0fd0be98: sync oslo policy
(https://review.openstack.org/#/c/48111/) was merged over the weekend
and broke test functionality for me. Our base TestCase tries to set
the policy_file option before it is declared.
Really there are two reasons for this:
1. Not all of the necessary state is setup before the test run
2. Some of the tests depend on things that are unrelated to the
functionality under test (e.g. why would XML serialization test be broken by
changes to the keystone command-line options?)
When I run:
$ ./run_tests.sh test_serializer.py
I get lots of these:
_StringException: Traceback (most recent call last):
File /opt/stack/keystone/keystone/tests/core.py, line 259, in setUp
self.opt(policy_file=etcdir('policy.json'))
File /opt/stack/keystone/keystone/tests/core.py, line 296, in opt
CONF.set_override(k, v)
File
/opt/stack/keystone/.venv/local/lib/python2.7/site-packages/oslo/config/cfg.py,
line 1579, in __inner
result = f(self, *args, **kwargs)
File
/opt/stack/keystone/.venv/local/lib/python2.7/site-packages/oslo/config/cfg.py,
line 1825, in set_override
opt_info = self._get_opt_info(name, group)
File
/opt/stack/keystone/.venv/local/lib/python2.7/site-packages/oslo/config/cfg.py,
line 2095, in _get_opt_info
raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: policy_file
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1233224/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1223524] Re: Inactive oauth extension creates dependency on httplib2
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1223524 Title: Inactive oauth extension creates dependency on httplib2 Status in OpenStack Identity (Keystone): Fix Released Bug description: The dependency resoution in Keystone requires that an object be explicitly instantiated prior to use. Extensions fall into this category. They are referenced in keystone/serivce.py such as: from keystone.contrib import endpoint_filter from keystone.contrib import oauth1 These components pull in other dependencies. In the case of oauth, it is httplib2. We can extend this method https://github.com/openstack/keystone/blob/master/keystone/common/wsgi.py#L536-L563 here https://github.com/openstack/keystone/blob/master/keystone/contrib/oauth1/routers.py#L21 And activate the Manager upon creating of the routes, which indicates they will actually be used in the deployment. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1223524/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220359] Re: High numbers of revocation events cause excessive cache churn
** 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/1220359 Title: High numbers of revocation events cause excessive cache churn Status in OpenStack Identity (Keystone): Fix Released Bug description: Due to the explicit refresh on the revocation list cache, when a revocation event occurs there is an added extra load to the Keystone processes. This should be changed to an invalidate of cache to ensure that we do not have to regenerate the revocation_list except on actual demand. This reduces overall lock contention when using memcache / redis / external storage as the cache layer. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1220359/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214176] Re: Fix copyright headers to be compliant with Foundation policies
** 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 neutron. https://bugs.launchpad.net/bugs/1214176 Title: Fix copyright headers to be compliant with Foundation policies Status in Ceilometer: Fix Committed Status in devstack - openstack dev environments: In Progress Status in OpenStack Hacking Guidelines: In Progress Status in Orchestration API (Heat): Fix Committed Status in OpenStack Dashboard (Horizon): Fix Committed Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): In Progress Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: In Progress Status in Python client library for Glance: In Progress Status in Python client library for heat: Fix Released Status in Python client library for Keystone: In Progress Status in Trove client binding: Fix Committed Status in OpenStack Object Storage (Swift): In Progress Status in Tempest: In Progress Status in Trove - Database as a Service: Fix Committed Bug description: Correct the copyright headers to be consistent with the policies outlined by the OpenStack Foundation at http://www.openstack.org/brand /openstack-trademark-policy/ Remove references to OpenStack LLC, replace with OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1214176/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1223036] Re: creating project in invalid domain raises SQL exception
** 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/1223036
Title:
creating project in invalid domain raises SQL exception
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
V3 API
export KEYSTONE_TOKEN=`keystone token-get | awk '/ id / { print $4}'`
curl -H X-Auth-Token:$KEYSTONE_TOKEN -d
'{project:{domain_id:invalid-domain, name:projectY}}' -H
Content-Type: application/json http://localhost:35357/v3/projects
{error: {message: Conflict occurred attempting to store project.
(1452, 'Cannot add or update a child row: a foreign key constraint
fails (`keystone`.`project`, CONSTRAINT `project_ibfk_1` FOREIGN KEY
(`domain_id`) REFERENCES `domain` (`id`))'), code: 409, title:
Conflict}}(.venv)[ayoung@ayoung530 keystone
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1223036/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220937] Re: with_venv.sh should enclose command args
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1220937 Title: with_venv.sh should enclose command args Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Orchestration API (Heat): Fix Committed Status in OpenStack Dashboard (Horizon): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Status in Trove - Database as a Service: Fix Released Bug description: $ tools/with_venv.sh neutron --os-username admin 1 net-show net 1 Unknown command [u'1', u'net-show', u'net', u'1'] after enclose command in with_venv.sh $ tools/with_venv.sh neutron --os-username admin 1 net-show net 1 You must provide a password via either --os-password or env[OS_PASSWORD] To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1220937/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1224320] Re: Tests for revocation should be forward-ported to master
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1224320 Title: Tests for revocation should be forward-ported to master Status in OpenStack Identity (Keystone): Fix Released Bug description: The fix for [OSSA 2013-025] PKI tokens are never revoked using memcache token backend (CVE-2013-4294) on bug 1202952 included new tests to check for the revocation behavior. Even if the vulnerability does not affect Havana/master, those tests should be forward-ported. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1224320/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1226374] Re: misused assertTrue in unit tests
** 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/1226374 Title: misused assertTrue in unit tests Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Orchestration API (Heat): Fix Committed Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Keystone: Fix Committed Status in OpenStack Object Storage (Swift): Fix Committed Status in Tempest: Fix Committed Bug description: 1)signature for assertTure: def failUnless(self, expr, msg=None): Fail the test unless the expression is true. if not expr: raise self.failureException, msg assert_ = assertTrue = failUnless 2) signature for assertEqual: def failUnlessEqual(self, first, second, msg=None): Fail if the two objects are unequal as determined by the '==' operator. if not first == second: raise self.failureException, \ (msg or '%r != %r' % (first, second)) ... assertEqual = assertEquals = failUnlessEqual assertTrue used to evaluate one expression assertEqual used to compare two expressions If passed two expressions to assertTrue , it always evaluate first expression . That 's not expected . To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1226374/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1222574] Re: Test for list_users in test_backend is not safe
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1222574 Title: Test for list_users in test_backend is not safe Status in OpenStack Identity (Keystone): Fix Released Bug description: The test for list_users in test_backend is written as: def test_list_users(self): users = self.identity_api.list_users() for test_user in default_fixtures.USERS: self.assertTrue(x for x in users if x['id'] == test_user['id']) This is not safe. You can show this by, for instance, setting users = [] instead of the correct result from self.identity_api.list_users() and no asset is raised To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1222574/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233362] Re: d2to1 triggers setuptools upgrade bug on old pip versions
** 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/1233362 Title: d2to1 triggers setuptools upgrade bug on old pip versions Status in OpenStack Identity (Keystone): Fix Released Bug description: pbr used to be based on d2to1, and we included it in our setup_requires. Then setuptools and distribute re-merged, and a set of depends in d2to1 cause the transient setuptools upgrade issue to surface if the user is running old distribute AND an old version of pip, potentially breaking the system. To fix it, we removed use of d2to1 from pbr, but we're still referencing it in a few places around OpenStack. We need to remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1233362/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1181155] Re: Dashboard doesn't list floating IP associated with VM instance
If we improve the issue reported, it should be fixed in nova not horizon, though I think it is still acceptable. I will mark this bug as Won't fix. ** Changed in: horizon Status: Incomplete = Won't Fix -- 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/1181155 Title: Dashboard doesn't list floating IP associated with VM instance Status in OpenStack Dashboard (Horizon): Won't Fix Status in Ubuntu: Confirmed Bug description: I upgraded my existing setup from folsom to grizzly. Then I was able to successfully associate floating IP to VM instances form dashboard. But dashboard then doesn't list associated floating IP. It is very difficult for user to remember what floating IP is associated with each instance (as our quota per user is really large, it is impossible to remember unless you note down somewhere). So for time being, till this is fixed, pl atleast suggest some workaround as our user base for this setup is high so impact here is also high. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1181155/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229475] Re: terminate_instance(): RuntimeError: Second simultaneous read on fileno 16 detected
Marking Incomplete for Nova, because I don't think we have found the root cause yet, so it still may be nova's fault. ** Changed in: nova Milestone: havana-rc1 = None ** Changed in: nova Status: Invalid = Incomplete ** Tags added: havana-rc-potential ** Changed in: python-neutronclient Importance: Undecided = High -- 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/1229475 Title: terminate_instance(): RuntimeError: Second simultaneous read on fileno 16 detected Status in OpenStack Compute (Nova): Incomplete Status in Python client library for Neutron: In Progress Bug description: http://logs.openstack.org/59/47659/6/check/gate-tempest-devstack-vm- neutron/fc83d44/logs/screen-n-cpu.txt.gz#_2013-09-23_18_25_06_484 2013-09-23 18:25:06.484 ERROR nova.openstack.common.rpc.amqp [req-3a80ff5a-817b-4eb8-be67-7f180bef8a6e demo demo] Exception during message handling 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/openstack/common/rpc/amqp.py, line 461, in _process_data 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp **args) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/openstack/common/rpc/dispatcher.py, line 172, in dispatch 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 354, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/exception.py, line 90, in wrapped 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp payload) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/exception.py, line 73, in wrapped 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return f(self, context, *args, **kw) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 244, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp pass 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 230, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 295, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 272, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp e, sys.exc_info()) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 259, in decorated_function 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1793, in terminate_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp do_terminate_instance(instance, bdms) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/openstack/common/lockutils.py, line 246, in inner 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp return f(*args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1785, in do_terminate_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp reservations=reservations) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/hooks.py, line 105, in inner 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp rv = f(*args, **kwargs) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp File /opt/stack/new/nova/nova/compute/manager.py, line 1758, in _delete_instance 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp user_id=user_id) 2013-09-23 18:25:06.484 3476 TRACE nova.openstack.common.rpc.amqp
[Yahoo-eng-team] [Bug 1223161] Re: FAIL: tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_run_stop_terminate_instance -- Malformed request body: Cannot understand JSON
*** This bug is a duplicate of bug 1229475 ***
https://bugs.launchpad.net/bugs/1229475
Yes, I think this is a side effect of bug 1229475. While investigating
that bug, I saw these types of failures, where neutronclient was getting
data from rabbitmq, due to it using a bogus fd that was in use by the
rpc code at the time.
** This bug has been marked a duplicate of bug 1229475
terminate_instance(): RuntimeError: Second simultaneous read on fileno 16
detected
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1223161
Title:
FAIL:
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_run_stop_terminate_instance
-- Malformed request body: Cannot understand JSON
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
Confirmed
Status in Tempest:
Confirmed
Bug description:
See http://logs.openstack.org/98/44098/11/check/gate-tempest-devstack-
vm-neutron/68c9a41/console.html
2013-09-10 03:26:06.136 |
==
2013-09-10 03:26:06.136 | FAIL:
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_run_stop_terminate_instance[gate,smoke]
2013-09-10 03:26:06.137 |
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_run_stop_terminate_instance[gate,smoke]
2013-09-10 03:26:06.137 |
--
2013-09-10 03:26:06.137 | _StringException: Empty attachments:
2013-09-10 03:26:06.137 | stderr
2013-09-10 03:26:06.138 | stdout
2013-09-10 03:26:06.138 |
2013-09-10 03:26:06.138 | pythonlogging:'': {{{
2013-09-10 03:26:06.139 | 2013-09-10 03:18:40,673 state: pending
2013-09-10 03:26:06.139 | 2013-09-10 03:18:47,211 State transition pending
== error 6 second
2013-09-10 03:26:06.139 | }}}
2013-09-10 03:26:06.140 |
2013-09-10 03:26:06.140 | Traceback (most recent call last):
2013-09-10 03:26:06.140 | File
tempest/thirdparty/boto/test_ec2_instance_run.py, line 150, in
test_run_stop_terminate_instance
2013-09-10 03:26:06.140 | self.assertInstanceStateWait(instance,
running)
2013-09-10 03:26:06.141 | File tempest/thirdparty/boto/test.py, line 356,
in assertInstanceStateWait
2013-09-10 03:26:06.141 | state = self.waitInstanceState(lfunction,
wait_for)
2013-09-10 03:26:06.141 | File tempest/thirdparty/boto/test.py, line 341,
in waitInstanceState
2013-09-10 03:26:06.142 | self.valid_instance_state)
2013-09-10 03:26:06.142 | File tempest/thirdparty/boto/test.py, line 332,
in state_wait_gone
2013-09-10 03:26:06.142 | self.assertIn(state, valid_set | self.gone_set)
2013-09-10 03:26:06.142 | File
/usr/local/lib/python2.7/dist-packages/testtools/testcase.py, line 328, in
assertIn
2013-09-10 03:26:06.143 | self.assertThat(haystack, Contains(needle))
2013-09-10 03:26:06.143 | File
/usr/local/lib/python2.7/dist-packages/testtools/testcase.py, line 417, in
assertThat
2013-09-10 03:26:06.143 | raise MismatchError(matchee, matcher, mismatch,
verbose)
2013-09-10 03:26:06.144 | MismatchError: u'error' not in set(['paused',
'terminated', 'running', 'stopped', 'pending', '_GONE', 'stopping',
'shutting-down'])
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1223161/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233264] Re: stable branch patches failing in check queue due to missing 'find_resourceid_by_name_or_id'
** Also affects: python-neutronclient Importance: Undecided Status: New ** Changed in: neutron Status: In Progress = Invalid ** Changed in: python-neutronclient Status: New = Fix Released ** Changed in: python-neutronclient Importance: Undecided = High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1233264 Title: stable branch patches failing in check queue due to missing 'find_resourceid_by_name_or_id' Status in OpenStack Neutron (virtual network service): Invalid Status in Python client library for Neutron: Fix Released Bug description: Patches on the stable branches (at least stable/grizzly) are failing in Jenkins because this change removed the 'find_resourceid_by_name_or_id' method from the quantumclient: https://github.com/openstack/python- neutronclient/commit/cbb83121c09f95b00720f494ab5f424612ac207d Here is a test report failure: http://logs.openstack.org/00/48300/1/check/gate-nova- python27/e47c623/console.html It's a static method which looks like it just needs to be proxied from python-neutronclient. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1233264/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1182679] Re: tempest.thirdparty.boto tests fail with TearDownException
There are too many reasons why a test can fail TearDown, cases that are covered by more specific bugs. Marking this as invalid ** No longer affects: nova ** Changed in: neutron Status: New = Invalid ** Changed in: tempest Status: Incomplete = Invalid ** Summary changed: - tempest.thirdparty.boto tests fail with TearDownException + tempest.thirdparty.boto tests fail with TearDownException -- Invalid bug report -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1182679 Title: tempest.thirdparty.boto tests fail with TearDownException -- Invalid bug report Status in OpenStack Neutron (virtual network service): Invalid Status in Tempest: Invalid Bug description: Excerpt of log: == ERROR: test suite for class 'tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest' -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/lib/python2.7/dist-packages/nose/util.py, line 478, in try_run return func() File /opt/stack/new/tempest/tempest/thirdparty/boto/test.py, line 263, in tearDownClass raise exceptions.TearDownException(num=fail_count) TearDownException: %(num)d cleanUp operation failed Details: 2 cleanUp operation failed Full log: http://logs.openstack.org/29469/3/check/gate-tempest-devstack-vm- quantum/24106/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1182679/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1213241] Re: Pickled data in Glance database enables remote code execution
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1213241 Title: Pickled data in Glance database enables remote code execution Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Glance uses pickled python objects for the storage of image location metadata in its SQL database backend [1]. In the event that the database server running beneath Glance is compromised, the usage of pickle will allow an attacker to execute untrusted code remotely and further compromise the cloud [2] [3]. [1] https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/models.py#L157 [2] See warning at the top of the pickle module doc: http://docs.python.org/2/library/pickle.html [3] http://blog.nelhage.com/2011/03/exploiting-pickle/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1213241/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233228] Re: Last translations refresh before RC1
** Changed in: glance 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/1233228 Title: Last translations refresh before RC1 Status in Ceilometer: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Identity (Keystone): Fix Released Bug description: Before issuing RC1 we need to refresh translations. Those are automatically proposed and can be found at https://review.openstack.org/#/q/topic:transifex/translations,n,z To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1233228/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : 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: glance 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/1182861 Title: Switch to oslo.config 1.2.0 final Status in Ceilometer: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Message Queuing Service (Marconi): Fix Committed 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 Released Status in Python client library for Keystone: Fix Committed Status in Trove - Database as a Service: Fix Committed 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 1221366] Re: Glance api v2 added features but still at 2.1
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1221366 Title: Glance api v2 added features but still at 2.1 Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Just need to update the version middleware to report the correct latest minor version. This will also be important for the docs we add. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1221366/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1231497] Re: v2 member-create call allows adding an empty tenantId as member
** Changed in: glance
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1231497
Title:
v2 member-create call allows adding an empty tenantId as member
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
This happens with API calls only, the python-glanceclient does not
allow it.
Note the request payload in this request:
curl -i -X POST -H X-Auth-Token: $AUTH_TOKEN \
-H 'Content-Type: application/json' \
-d '{ member: }' \
http://$GLANCE/v2/images/$IMG/members
Response:
HTTP/1.1 200 OK
Content-Length: 198
Content-Type: application/json; charset=UTF-8
X-Openstack-Request-Id: req-54621fca-efc0-4800-a2d0-f25a4ee4671d
Date: Thu, 26 Sep 2013 14:43:25 GMT
{status: pending, created_at: 2013-09-26T14:43:25Z,
updated_at: 2013-09-26T14:43:25Z, image_id: 4551c8ab-ab07-4d4b-
88f0-97be88f1c09b, member_id: , schema: /v2/schemas/member}
demo! curl -X GET -H X-Auth-Token: $AUTH_TOKEN -H 'Content-Type:
application/json' http://$GLANCE/v2/images/$IMG/members | python -m json.tool
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 478 100 4780 0 16296 0 --:--:-- --:--:-- --:--:-- 17071
{
members: [
{
created_at: 2013-09-26T14:43:25Z,
image_id: 4551c8ab-ab07-4d4b-88f0-97be88f1c09b,
member_id: ,
schema: /v2/schemas/member,
status: pending,
updated_at: 2013-09-26T14:43:25Z
},
{
created_at: 2013-09-20T21:16:21Z,
image_id: 4551c8ab-ab07-4d4b-88f0-97be88f1c09b,
member_id: 8989447062e04a818baf9e073fd04fa7,
schema: /v2/schemas/member,
status: pending,
updated_at: 2013-09-20T21:16:21Z
}
],
schema: /v2/schemas/members
}
Problem is that because of the structure of the delete call, you can't delete
such an image member:
DELETE http://$GLANCE/v2/images/$IMG/members/$CONSUMER
Workaround is that this doesn't match any tenant IDs, so it has no
effect, it just takes up space.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1231497/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229042] Re: glance qpid notifier can hang under heavy load
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1229042 Title: glance qpid notifier can hang under heavy load Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Glance qpid notifier can hang under heavy image creation load. The issue happens because of two issse: - The qpid notifier instance can be called by multiple green thread concurrently, one thread may recreate the connection object, while other thread working. The connection object should be local variable instead of object variable, in order to avoid unwanted modification, or replacement. The second issue the python-qpid uses PipeWaiter with a select.select. The select is not monkey patched to the be green thread friendly, is can causes hang issue. All other AMQP user openstack competent monkey patches the thread and select modules, but glance not. Usually good practice to make everything what is possible green thread/eventlet safe and make the application more preemptive. cinder, neutron makes everything evenetlet friend, nova excludes the 'os' module. I would recommend to make everything greenlet friendly. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1229042/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220744] Re: no size check when using http to create an image
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1220744 Title: no size check when using http to create an image Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Python client library for Glance: New Bug description: if I create an image from file and use --size which is smaller than the image on file we would fail with the below error: root@opens- ~(keystone_admin)]# glance image-create --name rhevm_image --disk-format qcow2 --container-format bare --file /tmp/39f89a6a-7fbb-43c0-a5ea-19b271f51829 --size 1 Request returned failure status. 400 Bad Request Supplied size (1) and size generated from uploaded image (1440612352) did not match. Setting image status to 'killed'. (HTTP 400) but if I create an image from http and use a smaller size the image is created: [root@opens-XXX ~(keystone_admin)]# glance image-create --name human --disk-format qcow2 --container-format bare --location http://XXX --human-readable --size 1 +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2013-09-04T14:18:05 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 55d45384-6b4b-40c6-b399-639b03c06c3b | | is_public| False| | min_disk | 0| | min_ram | 0| | name | human| | owner| ad326a6c11a742c6bfdf4ad63be0c889 | | protected| False| | size | 1B | | status | active | | updated_at | 2013-09-04T14:18:05 | +--+--+ [root@opens- ~(keystone_admin)]# glance image-list +--+-+-+--+++ | ID | Name| Disk Format | Container Format | Size | Status | +--+-+-+--+++ | 55d45384-6b4b-40c6-b399-639b03c06c3b | human | qcow2 | bare | 1 | active | |+--+-+-+--+++ if size is too small we should not allow the create of the image from http as well To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1220744/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1224449] Re: Property protections not enforced in order
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1224449 Title: Property protections not enforced in order Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Property protections need to be enforced in the order specified by the configuration file. i.e. [^x_owner.*] should be enforced before [.*] given the example config. This is currently not the case as the rules in property_utils.py is a dict. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1224449/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1215396] Re: emit warning while running flake8 without virtual env
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1215396 Title: emit warning while running flake8 without virtual env Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: run_tests.sh -N -p it will call the flake8 installed on your host to detect PEP8, and the flake8 plugin OpenStack hacking may not installed on your host, so this command may not detect the OpenStack Style Commandment supplied by hacking(e.g H202). run_tests.sh -p it will call the flake8 from virtual env, flake8 plugin OpenStack hacking installed in virtual env will be triggered. The result from run_tests.sh -p should be trusted, and jenkins uses virtual env to run flake8 too. When -N is enabled, emit warning to remind user. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1215396/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1223861] Re: Typo in protected property message
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1223861 Title: Typo in protected property message Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Encountered a malfored property protection rule %s:%s. s/malfored/malformed/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1223861/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1217838] Re: Glance V2 image create does not throw exception when the image is deleted during upload
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1217838 Title: Glance V2 image create does not throw exception when the image is deleted during upload Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Steps to reproduce the bug: 1. Create a image using glance V2 api. 2. delete the image before the create call returns. 3. Verify that the image record is marked as deleted. 4. The create call returns with a success response. This is not the behaviour in V1, where it responds with a 412. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1217838/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229351] Re: v2 image sharing doc incorrect
** Changed in: glance
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1229351
Title:
v2 image sharing doc incorrect
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
The new api calls section:
(1) POST to /v2/.../members: the request body is incorrect
(2) GET /v2/images/{imageId}/members/{memberId} was never implemented
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1229351/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229366] Re: incorrect response code from v2 delete image member call
** Changed in: glance
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1229366
Title:
incorrect response code from v2 delete image member call
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
Currently on success, DELETE /v2/image/{imageId}/members/{memberId}
returns 200 with no response body.
According to the Glance API contract, a 200 means you should expect a
response body. Success with no response body should be 204.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1229366/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1223167] Re: Tests should call get_api instead of importing the module directly
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1223167 Title: Tests should call get_api instead of importing the module directly Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The test_registry , test_simple and test_sqlalchemy tests import the modules directly instead of calling get_api of db/__init__.py With the introduction of db_pool, they should use the get_api method. Also, test_db_api.py, does not set the use_tpool option back to False, which results in failures of tests. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1223167/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1226701] Re: Many typos of v1 image metadata in glanceapi.rst
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1226701 Title: Many typos of v1 image metadata in glanceapi.rst Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: There are lots of typos of v1 image metadata in glanceapi.rst. Such as x-image-meta-min-disk should be x-image-meta-min_disk. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1226701/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1218712] Re: Registry API v1 couldn't work with multiple-location when image metadata encrypting enabled
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1218712 Title: Registry API v1 couldn't work with multiple-location when image metadata encrypting enabled Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Registry API v1 client and service side missing necessary en/decrypting code to handle image's multiple locations property when metadata encrypting option enabled. This will cause image locations metadata be mistakenly saved to database, and glance failing when it be load back. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1218712/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1213880] Re: glance upload to rbd creates zero length image
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1213880 Title: glance upload to rbd creates zero length image Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: If using upload() from V2 Glance API to write data to an RBD image the following problem occurs: A length of zero can be used which means an image of size 0 is created thus resulting in the following exception: 2013-08-19 12:09:36.044 31475 ERROR glance.api.v2.image_data [e9a89f79-d9ed-40b7-a1a0-157f6eb2b3d1 5cdd3419b10e4459a12593282f483331 9f93fd6845f04c6c9b51dcc9e24008a1] Failed to upload image data due to internal error 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data Traceback (most recent call last): 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/api/v2/image_data.py, line 53, in upload 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data image.set_data(data, size) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/domain/proxy.py, line 126, in set_data 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data self.base.set_data(data, size) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/notifier/__init__.py, line 201, in set_data 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data self.image.set_data(data, size) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/domain/proxy.py, line 126, in set_data 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data self.base.set_data(data, size) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/store/__init__.py, line 647, in set_data 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data self.image.image_id, utils.CooperativeReader(data), size) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/store/__init__.py, line 363, in add_to_backend 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data return store_add_to_backend(image_id, data, size, store) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/store/__init__.py, line 341, in store_add_to_backend 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data (location, size, checksum, metadata) = store.add(image_id, data, size) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /opt/stack/glance/glance/store/rbd.py, line 287, in add 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data offset += image.write(chunk, offset) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data File /usr/lib/python2.7/dist-packages/rbd.py, line 648, in write 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data raise make_ex(ret, error writing to %s % (self.name,)) 2013-08-19 12:09:36.044 31475 TRACE glance.api.v2.image_data InvalidArgument: error writing to 4c3712f8-e6ef-4b39-aaf0-975f046252f4 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1213880/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1202098] Re: glance-api failed to startup caused by UnicodeEncodeError in non-English environment
** Changed in: glance
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1202098
Title:
glance-api failed to startup caused by UnicodeEncodeError in non-
English environment
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
root@ubuntu:~/devstack# screen -x stack
There are screens on:
4195.stack(2013年07月17日 08时11分11秒)(Dead ???)
3733.stack(2013年07月17日 08时11分11秒)(Dead ???)
Remove dead screens with 'screen -wipe'.
There is no screen to be attached matching stack.
root@ubuntu:~/devstack# cat /var/log/glance/api.log
2013-07-17 11:26:10.880 14137 ERROR glance.store.sheepdog [-]
储存配置错误：Unexpected error while running command.
Command: collie
Exit code: 127
Stdout: ''
Stderr: '/bin/sh: 1: collie: not found\n'
2013-07-17 11:26:10.881 14137 CRITICAL glance [-] 'ascii' codec can't encode
characters in position 0-7: ordinal not in range(128)
2013-07-17 14:08:33.500 14993 DEBUG glance.store [-] Attempting to import
store glance.store.filesystem.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:143
2013-07-17 14:08:33.501 14993 DEBUG glance.store [-] Registering store class
'glance.store.filesystem.Store' with schemes ('file', 'filesystem')
create_stores /opt/stack/glance/glance/store/__init__.py:173
2013-07-17 14:08:33.507 14993 DEBUG glance.store.base [-] Late loading
location class glance.store.filesystem.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-17 14:08:33.507 14993 DEBUG glance.store.location [-] Registering
scheme file with {'store_class': class 'glance.store.filesystem.Store',
'location_class': class 'glance.store.filesystem.StoreLocation'}
register_scheme_map /opt/stack/glance/glance/store/location.py:85
2013-07-17 14:08:33.507 14993 DEBUG glance.store.location [-] Registering
scheme filesystem with {'store_class': class 'glance.store.filesystem.Store',
'location_class': class 'glance.store.filesystem.StoreLocation'}
register_scheme_map /opt/stack/glance/glance/store/location.py:85
2013-07-17 14:08:33.507 14993 DEBUG glance.store [-] Attempting to import
store glance.store.http.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:143
2013-07-17 14:08:33.508 14993 DEBUG glance.store [-] Registering store class
'glance.store.http.Store' with schemes ('http', 'https') create_stores
/opt/stack/glance/glance/store/__init__.py:173
2013-07-17 14:08:33.508 14993 DEBUG glance.store.base [-] Late loading
location class glance.store.http.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-17 14:08:33.508 14993 DEBUG glance.store.location [-] Registering
scheme http with {'store_class': class 'glance.store.http.Store',
'location_class': class 'glance.store.http.StoreLocation'}
register_scheme_map /opt/stack/glance/glance/store/location.py:85
2013-07-17 14:08:33.509 14993 DEBUG glance.store.location [-] Registering
scheme https with {'store_class': class 'glance.store.http.Store',
'location_class': class 'glance.store.http.StoreLocation'}
register_scheme_map /opt/stack/glance/glance/store/location.py:85
2013-07-17 14:08:33.509 14993 DEBUG glance.store [-] Attempting to import
store glance.store.rbd.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:143
2013-07-17 14:08:33.510 14993 DEBUG glance.store [-] Registering store class
'glance.store.rbd.Store' with schemes ('rbd',) create_stores
/opt/stack/glance/glance/store/__init__.py:173
2013-07-17 14:08:33.514 14993 DEBUG glance.store.base [-] Late loading
location class glance.store.rbd.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-17 14:08:33.514 14993 DEBUG glance.store.location [-] Registering
scheme rbd with {'store_class': class 'glance.store.rbd.Store',
'location_class': class 'glance.store.rbd.StoreLocation'} register_scheme_map
/opt/stack/glance/glance/store/location.py:85
2013-07-17 14:08:33.515 14993 DEBUG glance.store [-] Attempting to import
store glance.store.s3.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:143
2013-07-17 14:08:33.515 14993 DEBUG glance.store [-] Registering store class
'glance.store.s3.Store' with schemes ('s3', 's3+http', 's3+https')
create_stores /opt/stack/glance/glance/store/__init__.py:173
2013-07-17 14:08:33.516 14993 DEBUG glance.store.base [-] Late loading
location class glance.store.s3.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-17 14:08:33.516 14993 DEBUG glance.store.location [-] Registering
scheme s3 with {'store_class': class 'glance.store.s3.Store',
'location_class': class 'glance.store.s3.StoreLocation'} register_scheme_map
/opt/stack/glance/glance/store/location.py:85
[Yahoo-eng-team] [Bug 1207266] Re: glance allows membership access and modify for deleted image
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1207266 Title: glance allows membership access and modify for deleted image Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Currently if I delete an image, I am subsequently still allowed to access and modify members on that image (since it still exists but in a 'deleted' state). This should not be allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1207266/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214830] Re: add missing index for 'owner' column on images table
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1214830 Title: add missing index for 'owner' column on images table Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The image-list query involves fetching of images by images.owner. Because there is an index missing on the owner column, a full table scan is done while filtering for images. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1214830/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1218903] Re: glance-api can't start in non-English env
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = havana-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1218903
Title:
glance-api can't start in non-English env
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
In non-English env, the start of glance-api will fail with below
error:
2013-08-30 04:31:40.830 22137 DEBUG glance.store.base [-] [(')一構ソチ‐ Store
sheepdog could not be configured correctly. Reason: [(')十十一構ソチ‐ Error in store
configuration: Unexpected error while running command.
Command: collie
Exit code: 127
Stdout: ''
Stderr: '/bin/sh: collie:
\xe3\x82\xb3\xe3\x83\x9e\xe3\x83\xb3\xe3\x83\x89\xe3\x81\x8c\xe8\xa6\x8b\xe3\x81\xa4\xe3\x81\x8b\xe3\x82\x8a\xe3\x81\xbe\xe3\x81\x9b\xe3\x82\x93\n']]
_exception_to_str /usr/lib/python2.6/site-packages/glance/store/base.py:41
2013-08-30 04:31:40.831 22137 CRITICAL glance [-] 'ascii' codec can't decode
byte 0xe5 in position 4: ordinal not in range(128)
2013-08-30 04:31:40.831 22137 TRACE glance Traceback (most recent call last):
2013-08-30 04:31:40.831 22137 TRACE glance File /usr/bin/glance-api, line
10, in module
2013-08-30 04:31:40.831 22137 TRACE glance sys.exit(main())
2013-08-30 04:31:40.831 22137 TRACE glance File
/usr/lib/python2.6/site-packages/glance/cmd/api.py, line 57, in main
2013-08-30 04:31:40.831 22137 TRACE glance glance.store.create_stores()
2013-08-30 04:31:40.831 22137 TRACE glance File
/usr/lib/python2.6/site-packages/glance/store/__init__.py, line 165, in
create_stores
2013-08-30 04:31:40.831 22137 TRACE glance store_instance = store_cls()
2013-08-30 04:31:40.831 22137 TRACE glance File
/usr/lib/python2.6/site-packages/glance/store/base.py, line 65, in __init__
2013-08-30 04:31:40.831 22137 TRACE glance Disabling add method.) %
_exception_to_str(e))
2013-08-30 04:31:40.831 22137 TRACE glance UnicodeDecodeError: 'ascii' codec
can't decode byte 0xe5 in position 4: ordinal not in range(128)
2013-08-30 04:31:40.831 22137 TRACE glance
Seems it's injected by patch https://review.openstack.org/#/c/37421
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1218903/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1204359] Re: Duplicate options registered in glance/registry/client/v1/api.py
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1204359 Title: Duplicate options registered in glance/registry/client/v1/api.py Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The same set of options are registered in glance/registry/client/v2/api.py The module glance/registry/client/v1/api.py should use import_opt to import options from glance/registry/client/v2/api.py To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1204359/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1190666] Re: Add swift_store_ssl_compression param
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1190666 Title: Add swift_store_ssl_compression param Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Swift client now allows disabling ssl compression when making requests over https. Add a new param to allow us to use this. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1190666/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1228256] Re: Glance cache cleaner wrongly deletes cache for non invalid images
** Changed in: glance Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1228256 Title: Glance cache cleaner wrongly deletes cache for non invalid images Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The cache cleaner is currently cleaning invalid images like so: def clean(self, stall_time=None): Delete any image files in the invalid directory and any files in the incomplete directory that are older than a configurable amount of time. self.delete_invalid_files() if stall_time is None: stall_time = CONF.image_cache_stall_time now = time.time() older_than = now - stall_time self.delete_stalled_files(older_than) def delete_stalled_files(self, older_than): Removes any incomplete cache entries older than a supplied modified time. :param older_than: Files written to on or before this timestemp will be deleted. for path in self.get_cache_files(self.incomplete_dir): os.unlink(path) LOG.info(_(Removed stalled cache file %s), path) Although the older_than time is passed its not used anywhere, as a result if you run this through a cron, valid images in process for download/getting cached will be deleted from /incomplete since the cleaner does not check for time at all. Glance api log will complain when this happens in the middle of the fetch: Fetch finished, moving '/var/lib/glance/image- cache/incomplete/b9b38c90-cf64-4fa9-9e73-73da77e40074' to '/var/lib/glance/image-cache/b9b38c90-cf64-4fa9-9e73-73da77e40074' commit ERROR glance.image_cache [...] Exception encountered while tee'ing image 'b9b38c90-cf64-4fa9-9e73-73da77e40074' into cache: [Errno 2] No such file or directory. Continuing with response. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1228256/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1233228] Re: Last translations refresh before RC1
** Changed in: ceilometer 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/1233228 Title: Last translations refresh before RC1 Status in Ceilometer: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Identity (Keystone): Fix Released Bug description: Before issuing RC1 we need to refresh translations. Those are automatically proposed and can be found at https://review.openstack.org/#/q/topic:transifex/translations,n,z To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1233228/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1225099] Re: Encoding hard-coded in gettextutils.Message
** Changed in: ceilometer 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/1225099 Title: Encoding hard-coded in gettextutils.Message Status in Ceilometer: Fix Released Status in Cinder: Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: The __str__ method in openstack.common.gettextutils.Message is hard- coded to encode to utf-8 which creates problems when other logic goes to decode the string using the default encoding, e.g. when formatting log messages. Message objects with double-byte translations fail to log because of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1225099/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1217429] Re: Wrong instance_type_id field
** Changed in: ceilometer
Status: Fix Committed = Fix Released
** Changed in: ceilometer
Milestone: None = havana-rc1
--
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/1217429
Title:
Wrong instance_type_id field
Status in Ceilometer:
Fix Released
Status in OpenStack Compute (Nova):
Fix Committed
Bug description:
Reproduce the bug:
** Config
$ nova image-list
+--+-+++
| ID | Name|
Status | Server |
+--+-+++
| c91a4dcc-09f3-47c3-8532-8fa93014267c | cirros-0.3.1-x86_64-uec |
ACTIVE ||
| 65089976-7382-4177-932f-b32503c86c78 | cirros-0.3.1-x86_64-uec-kernel |
ACTIVE ||
| 81ffc23d-9efd-4f32-ac62-dfef9b969241 | cirros-0.3.1-x86_64-uec-ramdisk |
ACTIVE ||
+--+-+++
$ nova flavor-list
++---+---+--+---+--+---+-+---+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor
| Is_Public |
++---+---+--+---+--+---+-+---+
| 1 | m1.tiny | 512 | 1| 0 | | 1 | 1.0
| True |
| 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0
| True |
| 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0
| True |
| 4 | m1.large | 8192 | 80 | 0 | | 4 | 1.0
| True |
| 42 | m1.nano | 64| 0| 0 | | 1 | 1.0
| True |
| 5 | m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0
| True |
| 84 | m1.micro | 128 | 0| 0 | | 1 | 1.0
| True |
++---+---+--+---+--+---+-+---+
** Now boot a VM with flavor 42 (m1.nano):
$ nova boot server1 --image c91a4dcc-09f3-47c3-8532-8fa93014267c --flavor 42
$ nova show server1
+--++
| Property | Value
|
+--++
| status | ACTIVE
|
| updated | 2013-08-27T15:16:10Z
|
| OS-EXT-STS:task_state| None
|
| OS-EXT-SRV-ATTR:host | controller
|
| key_name | None
|
| image| cirros-0.3.1-x86_64-uec
(c91a4dcc-09f3-47c3-8532-8fa93014267c) |
| private network | 10.0.0.2
|
| hostId |
ca0d3c4ec83e031c6117a85e15db2977136d5541494f542f35b49c5a |
| OS-EXT-STS:vm_state | active
|
| OS-EXT-SRV-ATTR:instance_name| instance-0003
|
| OS-SRV-USG:launched_at | 2013-08-27T15:16:10.00
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | controller
|
| flavor | m1.nano (42)
|
| id | 8c20e949-d340-48cc-81cb-a35d1dbef315
|
| security_groups | [{u'name': u'default'}]
|
| OS-SRV-USG:terminated_at | None
|
| user_id | 65604ab0988447738de47bb4f8ff734b
|
| name | server1
|
| created | 2013-08-27T15:15:49Z
|
| tenant_id| 0a9a398a230b445a8968682c72f01d72
|
| OS-DCF:diskConfig| MANUAL
[Yahoo-eng-team] [Bug 1222737] Re: Neutron send 'network' notification without id
** Changed in: ceilometer
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/1222737
Title:
Neutron send 'network' notification without id
Status in Ceilometer:
Fix Released
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
2013-09-09 09:19:21.765 2362 INFO ceilometer.network.notifications [-]
network notification {u'_context_roles': [u'admin'], u'priority': u'INFO',
u'_context_read_deleted': u'no', u'event_type': u'network.create.start',
u'timestamp': u'2013-09-09 09:19:01.895216', u'_context_tenant_id':
u'dd91e0d407164ffca03818278c0b4ad7', u'payload': {u'network': {u'tenant_id':
u'273b10bdfb4148f5a41d28477f8b4137', u'name': u'private', u'admin_state_up':
True}}, u'_unique_id': u'7fb2a2d8a3b2453c85d2331db872b24c',
u'_context_is_admin': True, u'_context_project_id':
u'dd91e0d407164ffca03818278c0b4ad7', u'_context_timestamp': u'2013-09-09
09:19:01.778051', u'_context_user_id': u'a832259047f74538abd0b10cec85cba2',
u'publisher_id': u'network.devstack-precise-hpcloud-az2-234994', u'message_id':
u'e0aa1030-4b21-4731-a4a4-bb8337b2f2b5'}
2013-09-09 09:19:21.765 2362 AUDIT ceilometer.pipeline [-] Flush pipeline
meter_pipeline
2013-09-09 09:19:21.765 2362 AUDIT ceilometer.pipeline [-] Flush pipeline
cpu_pipeline
2013-09-09 09:19:21.765 2362 ERROR stevedore.extension [-] error calling
'network': 'id'
2013-09-09 09:19:21.765 2362 ERROR stevedore.extension [-] 'id'
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension Traceback (most recent
call last):
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension File
/usr/local/lib/python2.7/dist-packages/stevedore/extension.py, line 145, in
_invoke_one_plugin
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension
response_callback(func(e, *args, **kwds))
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension File
/opt/stack/new/ceilometer/ceilometer/collector/service.py, line 258, in
_process_notification_for_ext
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension
p(list(ext.obj.to_samples(notification)))
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension File
/opt/stack/new/ceilometer/ceilometer/network/notifications.py, line 86, in
process_notification
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension
resource_id=message['payload']['id'],
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension KeyError: 'id'
2013-09-09 09:19:21.765 2362 TRACE stevedore.extension
from http://logs.openstack.org/37/39237/7/check/gate-tempest-devstack-
vm-neutron/42d7fba/logs/screen-ceilometer-collector.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1222737/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : 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: ceilometer 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/1182861 Title: Switch to oslo.config 1.2.0 final Status in Ceilometer: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Message Queuing Service (Marconi): Fix Committed 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 Released Status in Python client library for Keystone: Fix Committed Status in Trove - Database as a Service: Fix Committed 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 1226943] Re: Need Use built-in print() function instead of print statement
** Changed in: ceilometer Status: Fix Committed = Fix Released ** Changed in: ceilometer Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1226943 Title: Need Use built-in print() function instead of print statement Status in Ceilometer: Fix Released Status in Cinder: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): Confirmed Status in Tempest: Fix Committed Bug description: In python 3 print statement is not supported, so we should use only print() functions. built-in function was introduce in python 2.6 http://www.python.org/dev/peps/pep-3105/ Note :This function is not normally available as a built-in since the name print is recognized as the print statement. To disable the statement and use the print() function, use this future statement at the top of your module: from __future__ import print_function http://docs.python.org/2/library/functions.html#print To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1226943/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1214176] RC1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 affects ceilometer status fixreleased milestone havana-rc1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSTHC4AAoJEFB6+JAlsQQjdAkQAJEnraDMfHKJwTwaUpNMjGAj qnCFxHyvyQpELEmvghChnBBrlqC459QbwVbFks98tmzOm44WHNBmu/tNMjCjohQB HwoTC/4tiUcueGP4bfleOTs0ivDsw5VJyaWRhy92mt5X71Mw7bFf4dkbcxFVpUaG DshQTupbNWncuL+Hoj1lrPX+BMZlpm0Vo5pAtcpgeEwU7dMGHx5tYYsG6gMUXGsh BWPvKpxcX9u20F9+smDvGs0gT6BYN//EZkkImwG2Z71/CL39tuUcysu37G8n16Wl 7uPLa4dVtSqbM0puuDD+EumFwayQj4QXdJCl4hksJBQGe6WdfOSjZt0a3fa3xz0b 1YfN1d2kHfuTMjWIbNnM1as90qupqNOWKjw5zCrr1V22lADenux6KA1jsHMNKePi FHKs+xja+U3F8iKx9Mr/UuMXzsFlrZmqpTHmejcgDmdIsbpluv3Epz/vVdlBbxTg m3QlbBIQ1y3/RCyZ42PIsVLVm3UG4cwcOf5hbVdEgRhI7xwJd8DaqIKurknYnmz7 gVvNMaPfjCSTMsgWVTEK+26cxblE2YG0MZHhSm+7t8/pB8DXj5FKgCBLwgPu6zIK 4Upxz2qRP/0pk62nA6I/jZ2Q2+MOs0S39XgGG4tdVdSMGf5PjuUpvXiuh29w/Ah5 0wLlAotY/eOTTbmiRP8F =0Twe -END PGP SIGNATURE- ** Changed in: ceilometer Status: Fix Committed = Fix Released ** Changed in: ceilometer Milestone: None = havana-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1214176 Title: Fix copyright headers to be compliant with Foundation policies Status in Ceilometer: Fix Released Status in devstack - openstack dev environments: In Progress Status in OpenStack Hacking Guidelines: In Progress Status in Orchestration API (Heat): Fix Committed Status in OpenStack Dashboard (Horizon): Fix Committed Status in Ironic (Bare Metal Provisioning): Fix Committed Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Neutron (virtual network service): Fix Committed Status in OpenStack Compute (Nova): In Progress Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: In Progress Status in Python client library for heat: Fix Released Status in Python client library for Keystone: In Progress Status in Trove client binding: Fix Committed Status in OpenStack Object Storage (Swift): In Progress Status in Tempest: In Progress Status in Trove - Database as a Service: Fix Committed Bug description: Correct the copyright headers to be consistent with the policies outlined by the OpenStack Foundation at http://www.openstack.org/brand /openstack-trademark-policy/ Remove references to OpenStack LLC, replace with OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1214176/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1224001] Re: test_network_basic_ops fails waiting for network to become available
** Changed in: swift
Status: New = Invalid
** Changed in: tempest
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1224001
Title:
test_network_basic_ops fails waiting for network to become available
Status in OpenStack Neutron (virtual network service):
In Progress
Status in OpenStack Object Storage (Swift):
Invalid
Status in Tempest:
Invalid
Bug description:
See http://logs.openstack.org/25/43125/4/gate/gate-tempest-devstack-
vm-neutron/40f3725/console.html
2013-09-11 16:20:48.981 |
==
2013-09-11 16:20:48.982 | FAIL:
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops[gate,smoke]
2013-09-11 16:20:48.982 |
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops[gate,smoke]
2013-09-11 16:20:48.982 |
--
2013-09-11 16:20:48.982 | _StringException: Empty attachments:
2013-09-11 16:20:48.982 | stderr
2013-09-11 16:20:48.982 | stdout
2013-09-11 16:20:48.982 |
2013-09-11 16:20:48.983 | pythonlogging:'': {{{
2013-09-11 16:20:48.983 | 2013-09-11 16:05:44,209 Starting new HTTP
connection (1): 127.0.0.1
2013-09-11 16:20:48.983 | 2013-09-11 16:05:44,309 Starting new HTTP
connection (1): 127.0.0.1
2013-09-11 16:20:48.983 | 2013-09-11 16:05:52,724 Tenant networks not
configured to be reachable.
2013-09-11 16:20:48.983 | }}}
2013-09-11 16:20:48.983 |
2013-09-11 16:20:48.983 | Traceback (most recent call last):
2013-09-11 16:20:48.984 | File
tempest/scenario/test_network_basic_ops.py, line 262, in
test_network_basic_ops
2013-09-11 16:20:48.984 | self._check_public_network_connectivity()
2013-09-11 16:20:48.984 | File
tempest/scenario/test_network_basic_ops.py, line 251, in
_check_public_network_connectivity
2013-09-11 16:20:48.984 | self._check_vm_connectivity(ip_address,
ssh_login, private_key)
2013-09-11 16:20:48.984 | File tempest/scenario/manager.py, line 579, in
_check_vm_connectivity
2013-09-11 16:20:48.984 | timeout=self.config.compute.ssh_timeout),
2013-09-11 16:20:48.984 | File tempest/scenario/manager.py, line 569, in
_is_reachable_via_ssh
2013-09-11 16:20:48.985 | return ssh_client.test_connection_auth()
2013-09-11 16:20:48.985 | File tempest/common/ssh.py, line 148, in
test_connection_auth
2013-09-11 16:20:48.985 | connection = self._get_ssh_connection()
2013-09-11 16:20:48.985 | File tempest/common/ssh.py, line 76, in
_get_ssh_connection
2013-09-11 16:20:48.985 | password=self.password)
2013-09-11 16:20:48.985 | SSHTimeout: Connection to the 172.24.4.229 via SSH
timed out.
2013-09-11 16:20:48.986 | User: cirros, Password: None
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1224001/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1232748] Re: [Postgres] DB error: (OperationalError) could not translate host name localhost to address
Reviewed: https://review.openstack.org/49409 Committed: http://github.com/openstack-dev/devstack/commit/96ba6ec1bf0b7cc54f9968e4cc3aa80b8f2c368e Submitter: Jenkins Branch:master commit 96ba6ec1bf0b7cc54f9968e4cc3aa80b8f2c368e Author: Matt Riedemann mrie...@us.ibm.com Date: Wed Oct 2 11:08:56 2013 -0700 Change DATABASE_HOST default to 127.0.0.1 Attempt to fix what is suspected to be a DNS resolution issue with postgresql check job. Closes-Bug: #1232748 Change-Id: Ic82e54b2af038e6c21d4f026f3da10f34c3c185c ** Changed in: devstack Status: In Progress = 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/1232748 Title: [Postgres] DB error: (OperationalError) could not translate host name localhost to address Status in devstack - openstack dev environments: Fix Released Status in OpenStack Identity (Keystone): New Status in OpenStack Compute (Nova): Confirmed Status in OpenStack Core Infrastructure: New Bug description: http://logs.openstack.org/81/48581/2/check/check-tempest-devstack-vm- postgres- full/ef4ce76/logs/screen-n-api.txt.gz#_2013-09-28_09_53_39_077 caused the failure of tempest.api.compute.admin.test_flavors.FlavorsAdminTestXML.test_create_flavor. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1232748/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1234455] Re: Tenant delete does not clean up the networks or VMs
This is a known issue with all services in OpenStack. Due to the loose coupling between services there's no way to know a tenant has been removed. This is a cross project issue and would need a blueprint and design discussion in the keystone project. ** Changed in: neutron Status: New = Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1234455 Title: Tenant delete does not clean up the networks or VMs Status in OpenStack Neutron (virtual network service): Won't Fix Bug description: If a tenant has networks and VM instances created under it. If tenant-delete is issued, it should either be rejected as there are objects under it or those objects should be automatically cleaned. Neither of that takes place. To reproduce this bug: - Create a tenant (keystone tenant-create ) - create a network for this tenant (neutron net-create) - Instantiate a VM for this tenant ( nova boot) - Now delete the tenant (keystone tenant-delete) This operation succeeds. However now you are left with a situation where you do not have a tenant, but, networks and VM belonging to it remain active. This whole thing can be created from Horizon as well. The worst part about doing from Horizon is that you do dot see tenant and networks on horizon after the tenant is deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1234455/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1220797] Re: can update image size to smaller number even though cannot create it like that in the first place
Admin is allowed to change the image size. ** Changed in: glance Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1220797 Title: can update image size to smaller number even though cannot create it like that in the first place Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: if you try to create an image from file using the --size and giving a smaller size the source image we would fail but we can use glance image-update to change the file after we create it. so wither we do not need the size check to begin with or both should fail. create image from a file (since this is the only time we currently check the size) glance image-create --name image_size_file --disk-format qcow2 --container-format bare --file /tmp/39f89a6a-7fbb-43c0-a5ea- 19b271f51829 [root@opens-vdsb ~(keystone_admin)]# glance image-list +--+--+-+--+++ | ID | Name | Disk Format | Container Format | Size | Status | +--+--+-+--+++ | 23bf4915-9f83-4eb5-a7c2-702de4d825e7 | image_size_file | qcow2 | bare | 1440612352 | active | [root@opens- ~(keystone_admin)]# glance image-update 23bf4915-9f83-4eb5-a7c2-702de4d825e7 --size 1 +--+--+ | Property | Value| +--+--+ | checksum | 18b7d574b7a1f0093fefc5484d9fb68d | | container_format | bare | | created_at | 2013-09-04T15:47:55 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 23bf4915-9f83-4eb5-a7c2-702de4d825e7 | | is_public| False| | min_disk | 0| | min_ram | 0| | name | image_size_file | | owner| ad326a6c11a742c6bfdf4ad63be0c889 | | protected| False| | size | 1| | status | active | | updated_at | 2013-09-04T15:49:26 | +--+--+ [root@opens-vdsb ~(keystone_admin)]# glance image-list +--+--+-+--+++ | ID | Name | Disk Format | Container Format | Size | Status | +--+--+-+--+++ | 23bf4915-9f83-4eb5-a7c2-702de4d825e7 | image_size_file | qcow2 | bare | 1 | active | To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1220797/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
