[Yahoo-eng-team] [Bug 1447380] Re: wrong cinder.conf.sample generation: missing directives for keystone_authtoken (at least)
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1447380 Title: wrong cinder.conf.sample generation: missing directives for keystone_authtoken (at least) Status in Cinder: Fix Released Status in Cinder kilo series: Fix Released Status in OpenStack Compute (Nova): Confirmed Bug description: Hi, When building the Debian Kilo RC1 package of Cinder, I'm generating the cinder.conf.sample file using (the same way tox would do): tools/config/generate_sample.sh -b . -p cinder -o etc/cinder Unfortunately, this resulted in a broken cinder.conf.sample, with at least keystone_authtoken missing directives. It stops at #hash_algorithms = md5 and all what's after is now missing. auth_host, auth_port, auth_protocol, identity_uri, admin_token, admin_user, admin_password and admin_tenant_name are missing directives from the configuration file. patrickeast on IRC gave me a file (which I supposed was generated using devstack) and latest trunk, and it seems there's the exact same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1447380/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440773] Re: Remove WritableLogger as eventlet has a real logger interface in 0.17.2
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1440773 Title: Remove WritableLogger as eventlet has a real logger interface in 0.17.2 Status in Cinder: Fix Released Status in Manila: Fix Committed Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): Fix Committed Status in Logging configuration library for OpenStack: Fix Released Bug description: Info from Sean on IRC: the patch to use a real logger interface in eventlet has been released in 0.17.2, which means we should be able to phase out https://github.com/openstack/oslo.log/blob/master/oslo_log/loggers.py Eventlet PR was: https://github.com/eventlet/eventlet/pull/75 thanks, dims To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1440773/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1459051] Re: Glance v2 Tasks Creation should be non-blocking
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1459051 Title: Glance v2 Tasks Creation should be non-blocking Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The glance v2 tasks creation api is blocking, in the sense, when a task is created the 201 response is not received until the task is complete. Also, when the response is received the task is in the pending state while the task in-effect could have succeeded or failed. We need to make it non-blocking by either running the executor in a separate eventlet thread or offload it to a task worker. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1459051/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1459015] Re: Tasks stuck in processing state when import to filesystem fails
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1459015 Title: Tasks stuck in processing state when import to filesystem fails Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: In general, when a glance v2 task runs into an error during the flow execution, the task gets stuck in the processing state. We are currently not marking the task as failed. I specifically ran into an issue where the import was failing due to a permission issue on the task.work_dir which was masked by the following exception :- File /opt/stack/glance/glance/async/__init__.py, line 64, in begin_processing self._run(task_id, task.type) File /opt/stack/glance/glance/async/taskflow_executor.py, line 133, in _run self.task_repo.save(task) File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 85, in __exit__ six.reraise(self.type_, self.value, self.tb) File /opt/stack/glance/glance/async/taskflow_executor.py, line 127, in _run engine.run() File /usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/engine.py, line 96, in run for _state in self.run_iter(): File /usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/engine.py, line 146, in run_iter self._change_state(states.FAILURE) File /usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 85, in __exit__ six.reraise(self.type_, self.value, self.tb) File /usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/engine.py, line 130, in run_iter failure.Failure.reraise_if_any(failures) File /usr/local/lib/python2.7/dist-packages/taskflow/types/failure.py, line 244, in reraise_if_any failures[0].reraise() File /usr/local/lib/python2.7/dist-packages/taskflow/types/failure.py, line 251, in reraise six.reraise(*self._exc_info) File /usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/executor.py, line 86, in _revert_task result = task.revert(**arguments) File /opt/stack/glance/glance/async/flows/base_import.py, line 158, in revert if os.path.exists(result.split(file://)[-1]): AttributeError: 'Failure' object has no attribute 'split' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1459015/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1463466] Re: Option use_user_token is created twice
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1463466 Title: Option use_user_token is created twice Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: In glance we have two places where we register use_user_token option: https://github.com/openstack/glance/blob/stable/kilo/glance/common/store_utils.py#L33 https://github.com/openstack/glance/blob/stable/kilo/glance/registry/client/__init__.py#L55 oslo.config considers them as one, because they have the same name and help string, but changing help string in one of them leads to an exception DuplicateOptError: duplicate option: use_user_token It seems that we should remove the option creation in store_utils and left only one declaration in registry client. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1463466/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467676] Re: OS-Brick connector needs to add HGST Solutions shim
This is not a bug. You should write a blueprint for nova that adds the HGST libvirt volume driver shim and your blueprint should depend on blueprint use-os-brick-library - there are others already doing this today for liberty that have specs. I'm not sure you need a spec for this since it's pretty mechanical, but you should have a blueprint, it's definitely not a bug. ** Changed in: nova Importance: Undecided = Wishlist ** Changed in: nova Status: In Progress = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1467676 Title: OS-Brick connector needs to add HGST Solutions shim Status in OpenStack Compute (Nova): Invalid Bug description: When Nova is patched to use os-brick, there will be a couple changes required to support the HGST Solutions connector type in it. Three very minor changes need to be made to make this happen: 1) Because os-brick is a library and not an application, the rootwrap for Nova will need to include the required CLI commands to attach/detach volumes as it can't live in os-brick's repository 2) libvirt_volume_types needs to include the HGST= LibvirtHGSTVolumeDriver mapping, because os-brick doesn't support discovery of supported types 3) A small shim LibvirtHGSTVolumeDriver calling the os-brick library needs to be added, again because there is no generic way presently for os-brick to map to specific volume types in libvirtvolumetype. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1467676/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1286528] Re: guru-meditation fails on Windows due to non portable signal handling
** Changed in: cinder
Status: Fix Committed = Fix Released
** Changed in: cinder
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1286528
Title:
guru-meditation fails on Windows due to non portable signal handling
Status in Cinder:
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Status in The Oslo library incubator:
Fix Released
Bug description:
The guru-meditation report fails on Hyper-V due to missing signal
handling.
This is a blocking issue on Windows.
http://64.119.130.115/74060/3/Hyper-V_logs/hv-compute1/nova-
console.log.gz
Traceback (most recent call last):
File c:\OpenStack\virtualenv\Scripts\nova-compute-script.py, line 9, in
module
load_entry_point('nova==2014.1.dev954.g3a611cc', 'console_scripts',
'nova-compute')()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
353, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
2321, in load_entry_point
return ep.load()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
2048, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File c:\OpenStack\virtualenv\lib\site-packages\nova\cmd\compute.py, line
32, in module
from nova.openstack.common.report import guru_meditation_report as gmr
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 63, in module
class GuruMeditation(object):
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 100, in GuruMeditation
def setup_autorun(cls, version, signum=signal.SIGUSR1):
AttributeError: 'module' object has no attribute 'SIGUSR1'
Nova patch that introduced the issue:
https://github.com/openstack/nova/commit/cec532848f569afb4832029bce4969578472a57a
Review link:
https://review.openstack.org/#/c/69058/
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1286528/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1304099] Re: link prefixes are truncated
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1304099 Title: link prefixes are truncated Status in Cinder: Fix Released Status in OpenStack Compute (Nova): Fix Released Bug description: The osapi_glance_link_prefix and osapi_compute_link_prefix configuration parameters have their paths removed. For instance, if nova.conf contains osapi_compute_link_prefix = http:/127.0.0.1/compute/ the values displayed in the API response exclude the compute/ component. Other services, such as keystone, retain the path. This bit of code is where the bug occurs: https://github.com/openstack/nova/blob/673ecaea3935b6a50294f24f8a964590ca07a959/nova/api/openstack/common.py#L568-L582 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1304099/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461931] Re: __init__ method should not return any value explicitly
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1461931 Title: __init__ method should not return any value explicitly Status in Cinder: Fix Released Status in OpenStack Compute (Nova): Fix Committed Bug description: As per python documentation [1], __init__ method should not return any value explicitly, doing so will raise TypeError. [1] https://docs.python.org/2/reference/datamodel.html#object.__init__ To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1461931/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1421863] Re: Can not find policy directory: policy.d spams the logs
** Changed in: cinder Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1421863 Title: Can not find policy directory: policy.d spams the logs Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Released Status in devstack - openstack dev environments: In Progress Status in Orchestration API (Heat): Fix Committed Status in OpenStack Compute (Nova): Fix Released Status in The Oslo library incubator: Triaged Status in Oslo Policy: Fix Released Status in Openstack Database (Trove): New Bug description: This hits over 118 million times in 24 hours in Jenkins runs: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQ2FuIG5vdCBmaW5kIHBvbGljeSBkaXJlY3Rvcnk6IHBvbGljeS5kXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6Ijg2NDAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQyMzg2Njk0MTcxOH0= We can probably just change something in devstack to avoid this. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1421863/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1449639] Re: RBD: On image creation error, image is not deleted
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1449639 Title: RBD: On image creation error, image is not deleted Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance icehouse series: Fix Released Status in OpenStack Glance backend store-drivers library (glance_store): Fix Released Bug description: When an exception rises while adding/creating an image, and the image has been created, this new image is not properly deleted. The fault lies in the `_delete_image` call of the Store.add method that is providing incorrect arguments. This also affects Glance (Icehouse), since back then glance_store functionality was included there. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1449639/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1270229] Re: No logging occurs when user is forbidden to perform an action
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1270229 Title: No logging occurs when user is forbidden to perform an action Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: In both glance v1 and v2, if policies forbide an action, when it occurs there are no logs. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1270229/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1455141] Re: tox -egenconfig failure (no glance-search.conf)
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1455141 Title: tox -egenconfig failure (no glance-search.conf) Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: I tried to generate the config samples but ended up with: $ tox -e genconfig [...] genconfig runtests: commands[5] | oslo-config-generator --config-file etc/oslo-config-generator/glance-search.conf Traceback (most recent call last): File .tox/genconfig/bin/oslo-config-generator, line 11, in module sys.exit(main()) File /home/gpocentek/Workspace/OpenStack/glance/.tox/genconfig/local/lib/python2.7/site-packages/oslo_config/generator.py, line 331, in main conf(args, version=version) File /home/gpocentek/Workspace/OpenStack/glance/.tox/genconfig/local/lib/python2.7/site-packages/oslo_config/cfg.py, line 1853, in __call__ raise ConfigFilesNotFoundError(self._namespace._files_not_found) oslo_config.cfg.ConfigFilesNotFoundError: Failed to find some config files: /home/gpocentek/Workspace/OpenStack/glance/etc/oslo-config-generator/glance-search.conf I couldn't find a reference to glance-search.conf in the git history. This happens on master and stable/kilo. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1455141/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1452447] Re: is_public is not v2 reserved prop but domain marks it otherwise
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1452447 Title: is_public is not v2 reserved prop but domain marks it otherwise Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: https://review.openstack.org/#/c/154704/ modifies is_public to be non- reserved. However, the list -- _reserved_properties = ['owner', 'is_public', 'locations', does not have it removed. https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L56 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1452447/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1371022] Re: Idle client connections can persist indefinitely
** 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/1371022 Title: Idle client connections can persist indefinitely Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance juno series: New Status in Glance kilo series: Fix Committed Bug description: Idle client socket connections can persist forever, eg: $ nc localhost 8776 [never returns] To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1371022/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1460060] Re: Glance v1 and v2 api returns 500 while passing --min-ram and --min-disk greater than 2^(31) max value
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1460060 Title: Glance v1 and v2 api returns 500 while passing --min-ram and --min- disk greater than 2^(31) max value Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Python client library for Glance: New Bug description: glance image-create --name test --container-format bare --disk-format raw --file delete_images.py --min-disk 100 HTTPInternalServerError (HTTP 500) glance image-create --name test --container-format bare --disk-format raw --file delete_images.py --min-ram 100 HTTPInternalServerError (HTTP 500) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1460060/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1456800] Re: issue with pbr 1.0 release
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1456800
Title:
issue with pbr 1.0 release
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
gate-glance-python27 of https://review.openstack.org/#/c/184304/ failed with:
ft1.1178:
glance.tests.unit.test_opts.OptsTestCase.test_list_manage_opts_StringException:
Traceback (most recent call last):
File glance/tests/unit/test_opts.py, line 301, in test_list_manage_opts
expected_opt_groups, expected_opt_names)
File glance/tests/unit/test_opts.py, line 45, in _test_entry_point
list_fn = ep.load()
File
/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/pkg_resources/__init__.py,
line 2344, in load
self.require(*args, **kwargs)
File
/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/pkg_resources/__init__.py,
line 2361, in require
items = working_set.resolve(reqs, env, installer)
File
/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/pkg_resources/__init__.py,
line 838, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (pbr 1.0.0
(/home/jenkins/workspace/gate-glance-python27/.tox/py27/lib/python2.7/site-packages),
Requirement.parse('pbr!=0.7,1.0,=0.6'), set(['oslo.log',
'sqlalchemy-migrate', 'oslo.context', 'oslo.serialization', 'stevedore',
'keystonemiddleware', 'oslo.messaging', 'oslo.config', 'oslo.concurrency',
'oslo.i18n', 'python-keystoneclient', 'oslo.utils', 'oslo.db', 'oslo.vmware',
'taskflow', 'python-cinderclient']))
See: http://logs.openstack.org/04/184304/1/check/gate-glance-
python27/a9278fa/
According to logs, pbr 1.0 and hacking 0.10.2 were installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1456800/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1419823] Re: Nullable image description crashes v2 client
** 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/1419823
Title:
Nullable image description crashes v2 client
Status in Ubuntu Cloud Archive:
Confirmed
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Status in Glance kilo series:
Fix Committed
Status in glance package in Ubuntu:
Confirmed
Bug description:
When you somehow set the image description to None the glanceclient v2
image-list crashes (as well as image-show, image-update for this
particular image). The only way to show all images now is to use
client v1, because it's more stable in this case.
Steps to reproduce:
1. Open Horizon and go to the edit page of any image.
2. Set description to anything eg. 123 and save.
3. Open image edit page again, remove description and save it.
4. List all images using glanceclient v2: glance --os-image-api-version 2
image-list
5. Be sad, because of raised exception:
None is not of type u'string'
Failed validating u'type' in schema[u'additionalProperties']:
{u'type': u'string'}
On instance[u'description']:
None
During investigating the issue I've found that the
additionalProperties schema is set to accept only string values, so it
should be expanded to allow for null values as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1419823/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1441764] Re: Cleanup TODO in glance/gateway.py for elasticsearch being unavailable
** 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/1441764 Title: Cleanup TODO in glance/gateway.py for elasticsearch being unavailable Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: This came up in this change https://review.openstack.org/#/c/171279/4/glance/gateway.py to fix bug 1441239. We are going to merge that change with a debug level log message to avoid a string freeze exception in kilo, but then we need to use this bug to close the TODO when liberty opens up. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1441764/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1439951] Re: glance.tests.unit.test_artifacts_plugin_loader unit test failed
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1439951
Title:
glance.tests.unit.test_artifacts_plugin_loader unit test failed
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
The unit tests in glance.tests.unit.test_artifacts_plugin_loader was
failed.
# ./run_tests.sh -N glance.tests.unit.test_artifacts_plugin_loader
glance.tests.unit.test_artifacts_plugin_loader.TestArtifactsLoader
test_config_validationFAIL
test_check_function FAIL
test_basic_loader_funcOK 0.01
test_load FAIL
Below is the result of test_load() unit test.
==
FAIL:
glance.tests.unit.test_artifacts_plugin_loader.TestArtifactsLoader.test_load
--
Traceback (most recent call last):
testtools.testresult.real._StringException: Traceback (most recent call last):
File
/home/jenkins/glance/glance/tests/unit/test_artifacts_plugin_loader.py, line
67, in test_load
'MyArtifact=%s.v1.artifact:MyArtifact' % self.path]),
File
/home/jenkins/glance/glance/tests/unit/test_artifacts_plugin_loader.py, line
49, in _setup_loader
pkg_resources.EntryPoint.parse(art) for art in artifacts]
File /usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py,
line 2366, in parse
return cls(res['name'], res['module'], attrs, extras, dist)
File /usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py,
line 2289, in __init__
raise ValueError(Invalid module name, module_name)
ValueError: ('Invalid module name',
'.home.jenkins.glance.glance.tests.unit.test_artifacts_plugin_loader')
---
other results were same to the test_load() test.
The reason why is that I performs unit tests as jenkins user.
Therefore my working directory is /home/jenkins/glance/ .
when getting the path for _setup_loader()
It gets full path of file which means,
path = os.path.splitext(__file__)[0].replace('/', '.')
The full path is raised ValueError for module validation check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1439951/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1276207] Re: vmware driver does not validate server certificates
** Changed in: ceilometer Status: Fix Committed = Fix Released ** Changed in: ceilometer Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1276207 Title: vmware driver does not validate server certificates Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Committed Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Compute (Nova): Fix Committed Status in Oslo VMware library for OpenStack projects: Fix Released Bug description: The VMware driver establishes connections to vCenter over HTTPS, yet the vCenter server certificate is not verified as part of the connection process. I know this because my vCenter server is using a self-signed certificate which always fails certification verification. As a result, someone could use a man-in-the-middle attack to spoof the vcenter host to nova. The vmware driver has a dependency on Suds, which I believe also does not validate certificates because hartsock and I noticed it uses urllib. For reference, here is a link on secure connections in OpenStack: https://wiki.openstack.org/wiki/SecureClientConnections Assuming Suds is fixed to provide an option for certificate verification, next step would be to modify the vmware driver to provide an option to override invalid certificates (such as self- signed). In other parts of OpenStack, there are options to bypass the certificate check with a insecure option set, or you could put the server's certificate in the CA store. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1276207/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1446583] Re: services no longer reliably stop in stable/kilo
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1446583 Title: services no longer reliably stop in stable/kilo Status in Cinder: Fix Released Status in Cinder kilo series: Fix Released Status in OpenStack Identity (Keystone): Fix Committed Status in Keystone kilo series: Fix Released Status in OpenStack Compute (Nova): Fix Committed Status in The Oslo library incubator: Fix Released Bug description: In attempting to upgrade the upgrade branch structure to support stable/kilo - master in devstack gate, we found the project could no longer pass Grenade testing. The reason is because pkill -g is no longer reliably killing off the services: http://logs.openstack.org/91/175391/5/gate/gate-grenade- dsvm/0ad4a94/logs/grenade.sh.txt.gz#_2015-04-21_03_15_31_436 It has been seen with keystone-all and cinder-api on this patch series: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVGhlIGZvbGxvd2luZyBzZXJ2aWNlcyBhcmUgc3RpbGwgcnVubmluZ1wiIEFORCBtZXNzYWdlOlwiZGllXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0Mjk2MTU0NTQ2MzB9 There were a number of changes to the oslo-incubator service.py code during kilo, it's unclear at this point which is the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1446583/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1415087] Re: [OSSA 2015-011] Format-guessing and file disclosure in image convert (CVE-2015-1850, CVE-2015-1851)
** Changed in: cinder Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1415087 Title: [OSSA 2015-011] Format-guessing and file disclosure in image convert (CVE-2015-1850, CVE-2015-1851) Status in Cinder: Fix Released Status in Cinder icehouse series: Fix Released Status in Cinder juno series: Fix Committed Status in Cinder kilo series: Fix Committed Status in OpenStack Compute (Nova): Triaged Status in OpenStack Security Advisories: Fix Committed Bug description: Cinder does not provide input format to several calls of qemu-img convert. This allows the attacker to play the format guessing by providing a volume with a qcow2 signature. If this signature contains a base file, this file will be read by a process running as root and embedded in the output. This bug is similar to CVE-2013-1922. Tested with: lvm backed volume storage, it may apply to others as well Steps to reproduce: - create volume and attach to vm, - create a qcow2 signature with base-file[1] from within the vm and - trigger upload to glance with cinder upload-to-image --disk-type qcow2[2]. The image uploaded to glance will have /etc/passwd from the cinder-volume host embedded. Affected versions: tested on 2014.1.3, found while reading 2014.2.1 Fix: Always specify both input -f and output format -O to qemu- img convert. The code is in module cinder.image.image_utils. Bastian Blank [1]: qemu-img create -f qcow2 -b /etc/passwd /dev/vdb [2]: The disk-type != raw triggers the use of qemu-img convert To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1415087/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445026] Re: glance-manage db load_metadefs does not load tags correctly
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1445026 Title: glance-manage db load_metadefs does not load tags correctly Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: Fix Released Bug description: Script which populates DB with metadefs does not load tags correctly. It looks for ID in .json file while it should look for name of a tag. In result user can't load tags to database without providing unnecessary ID in .json file. It also may lead to conflicts in DB and unhandled exceptions. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1445026/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1454730] Re: Glance v1 registry returns 500 when passing --checksum over 32 characters long on image-create
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1454730 Title: Glance v1 registry returns 500 when passing --checksum over 32 characters long on image-create Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: glance --os-image-api-version 1 image-create --name created_by_demo --container-format bare --disk-format raw --file MANIFEST.in --checksum 2 Raises 500 InternalServerError due to DbError on save in db. File /home/ina/projects/glance/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py, line 1063, in _execute_context context) File /home/ina/projects/glance/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py, line 442, in do_execute cursor.execute(statement, parameters) File /home/ina/projects/glance/.venv/local/lib/python2.7/site-packages/MySQLdb/cursors.py, line 205, in execute self.errorhandler(self, exc, value) File /home/ina/projects/glance/.venv/local/lib/python2.7/site-packages/MySQLdb/connections.py, line 36, in defaulterrorhandler raise errorclass, errorvalue DBError: (DataError) (1406, Data too long for column 'checksum' at row 1) 'INSERT INTO images (created_at, updated_at, deleted_at, deleted, id, name, disk_format, container_format, size, virtual_size, status, is_public, checksum, min_disk, min_ram, owner, protected) VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s)' (datetime.datetime(2015, 5, 13, 14, 24, 22, 621502), datetime.datetime(2015, 5, 13, 14, 24, 22, 621515), None, 0, '6ea28b08-0131-431c-add3-9278cfb424c7', 'created_by_demo', 'raw', 'bare', 529, None, 'queued', 0, '2', 0, 0, '0e12fbc7a63c44f1b078d96e0979be8e', 0) 2015-05-13 17:24:22.630 17212 INFO eventlet.wsgi.server [req-163e1c08-3ea1-47a1-ae5b-e27f522c0453 8773a0d6190d4190808c7669d0d7adc6 0e12fbc7a63c44f1b078d96e0979be8e - - -] 127.0.0.1 - - [13/May/2015 17:24:22] POST /images HTTP/1.1 500 139 0.076708 v2 api is not affected, the 32-characters maxLength constraint is validated by jsonschema. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1454730/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1447327] Re: Glance v1 should now be in SUPPORTED status
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1447327 Title: Glance v1 should now be in SUPPORTED status Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: Fix Released Bug description: As per title To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1447327/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1430804] Re: Protected properties rules roles check is case-sensitive
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1430804 Title: Protected properties rules roles check is case-sensitive Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Hi , when glance image properties are protected, the check that handles the match between the user roles and CRUD rules with roles is case-sensitive. The check should be case-insensitive since https://bugs.launchpad.net/glance/+bug/1010519 Example: I have an image property operator_property_name: [operator_property_name] create: admin, Member read: admin, Member update: admin, Member delete: admin, Member This gives the user with the role Member the possibility to create/read/update/delete this image property. However all these operations will fail, because protected properties rules roles check is case-sensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1430804/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268680] Re: Creating an image without container format queues image and fails with 400
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1268680 Title: Creating an image without container format queues image and fails with 400 Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Description of problem: Creating an image from CLI without --container format queued the image and fails with 400. Request returned failure status. 400 Bad Request Invalid container format 'None' for image. (HTTP 400) How reproducible: # glance --debug image-create --name cirros --disk-format qcow2 --file /tmp/cirros-image.qcow2 --progress snip [=] 100% HTTP/1.1 400 Bad Request date: Tue, 07 Jan 2014 14:13:54 GMT content-length: 64 content-type: text/plain; charset=UTF-8 x-openstack-request-id: req-11b4ecad-3a8d-4e44-9c37-a4d843805889 400 Bad Request Invalid container format 'None' for image. # glance image-list +---+---+-+++---+ | ID | Name| Disk Format | Container Format | Size | Status| +---+---+-+++---+ | b2490dd2-b535-4b98-8647-cca428a63e01 | cirros | qcow2 | | 307962880 | queued | +---+---+-+++---+ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1268680/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1422699] Re: glance api doesn't abort start up on Store configuration errors
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1422699 Title: glance api doesn't abort start up on Store configuration errors Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Glance backend store-drivers library (glance_store): Fix Released Bug description: Glance api service does not abort start up when errors in glance-api.cfg file are encountered. It would make sense to abort service start up when a BadStoreConfiguration exception is encountered, instead of just sending the error to the logs and disabling adding images to that Store. For example if a Filesystem Storage Backend with multiple store is configured with a duplicate directory: filesystem_store_datadirs=/mnt/nfs1/images/:200 filesystem_store_datadirs=/mnt/nfs1/images/:100 Logs will have the error: ERROR glance_store._drivers.filesystem [-] Directory /mnt/nfs1/image specified multiple times in filesystem_store_datadirs option of filesystem configuration TRACE glance_store._drivers.filesystem None TRACE glance_store._drivers.filesystem WARNING glance_store.driver [-] Failed to configure store correctly: None Disabling add method. Service will start and when client tries to add an image he will receive a 410 Gone error saying: Error in store configuration. Adding images to store is disabled. This affects not only the filesystem storage backend but all glance- storage drivers that encounter an error in the configuration and raise a BadStoreConfiguration exception. How reproducible: Every time Steps to Reproduce: 1. Configure Glance to use Filesystem Storage Backend with multiple store and duplicate a filesystem_storage_datadirs. 2. Run glance api Expected behavior: Glance api service should not have started and should have reported that the directory was specified multiple times. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1422699/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1439061] Re: Plugin types are not exposed to the client
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1439061 Title: Plugin types are not exposed to the client Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: Fix Released Bug description: Glance Search clients currently don't have anyway to know what types are available. Search clients need to know the type to include in the search request for the particular resource. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1439061/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445827] Re: unit test failures: Glance insist on ordereddict
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1445827 Title: unit test failures: Glance insist on ordereddict Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: In Progress Status in Glance liberty series: Fix Released Status in Taskflow for task-oriented systems.: In Progress Bug description: There's no python-ordereddict package anymore in Debian, as this is normally included in Python 2.7. I have therefore patched requirements.txt to remove ordereddict. However, even after this, I get some bad unit test errors about it. This must be fixed upstream, because there's no way (modern) downstream distributions can fix it (as the ordereddict Python package will *not* come back). Below is the tracebacks for the 4 failed unit tests. FAIL: glance.tests.unit.test_opts.OptsTestCase.test_list_api_opts -- Traceback (most recent call last): _StringException: Traceback (most recent call last): File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 143, in test_list_api_opts expected_opt_groups, expected_opt_names) File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 45, in _test_entry_point list_fn = ep.load() File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2188, in load self.require(env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2202, in require items = working_set.resolve(reqs, env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 639, in resolve raise DistributionNotFound(req) DistributionNotFound: ordereddict == FAIL: glance.tests.unit.test_opts.OptsTestCase.test_list_cache_opts -- Traceback (most recent call last): _StringException: Traceback (most recent call last): File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 288, in test_list_cache_opts expected_opt_groups, expected_opt_names) File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 45, in _test_entry_point list_fn = ep.load() File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2188, in load self.require(env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2202, in require items = working_set.resolve(reqs, env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 639, in resolve raise DistributionNotFound(req) DistributionNotFound: ordereddict == FAIL: glance.tests.unit.test_opts.OptsTestCase.test_list_manage_opts -- Traceback (most recent call last): _StringException: Traceback (most recent call last): File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 301, in test_list_manage_opts expected_opt_groups, expected_opt_names) File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 45, in _test_entry_point list_fn = ep.load() File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2188, in load self.require(env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2202, in require items = working_set.resolve(reqs, env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 639, in resolve raise DistributionNotFound(req) DistributionNotFound: ordereddict == FAIL: glance.tests.unit.test_opts.OptsTestCase.test_list_registry_opts -- Traceback (most recent call last): _StringException: Traceback (most recent call last): File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 192, in test_list_registry_opts expected_opt_groups, expected_opt_names) File /��PKGBUILDDIR��/glance/tests/unit/test_opts.py, line 45, in _test_entry_point list_fn = ep.load() File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2188, in load self.require(env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2202, in require items = working_set.resolve(reqs, env, installer) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 639, in resolve raise DistributionNotFound(req) DistributionNotFound: ordereddict == FAIL:
[Yahoo-eng-team] [Bug 1452750] Re: dest_file in task convert is wrong
** 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/1452750 Title: dest_file in task convert is wrong Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: Fix Committed Bug description: https://github.com/openstack/glance/commit/1b144f4c12fd6da58d7c48348bf7bab5873388e9 #diff-f02c20aafcce326b4d31c938376f6c2aR78 - head - desk The dest_path is not formated correctly, which ends up in converting the image to a path that is completely ignored by other tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1452750/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1451850] Re: Glance v2 api returns 500 on NotAuthenticated in registry
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1451850 Title: Glance v2 api returns 500 on NotAuthenticated in registry Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: If any CRUD image operation fails due to keystone token expiration during a glance-registry operation, glance-api returns 500 InternalServerError as NotAuthenticated exception is not expected in any of the api methods. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1451850/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1453068] Re: task: Image's locations empty after importing to store
** 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/1453068 Title: task: Image's locations empty after importing to store Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: Fix Committed Bug description: The ImportToStore task is setting the image data correctly but not saving it after it's been imported. This causes the image's location to be lost and therefore the image is completely useless because there are no locations associated to it To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1453068/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1412798] Re: Typo in section header in config silently disables all config parsing
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1412798 Title: Typo in section header in config silently disables all config parsing Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: I know it sounds silly, but I just spend five hours trying to find why glance is not working with swift and printing random erros. At the end I had found it had ignored all debug/log settings, and later I had found the source of the problem - small typo in my config. If config contains '[[DEFAULT]' instead of '[DEFAULT]' glance ignores all setting in section (i think it is not only for 'default', but 'default' is the most devastating, because it disables logging and logging locations). Proposed solution: write down a warning to stdout if configuration file contains no '[DEFAULT]' section. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1412798/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1466851] Re: Move to graduated oslo.service
** Also affects: sahara Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1466851 Title: Move to graduated oslo.service Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Orchestration API (Heat): Fix Committed Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in OpenStack Data Processing (Sahara): In Progress Status in Openstack Database (Trove): In Progress Bug description: oslo.service library has graduated so all OpenStack projects should port to it instead of using oslo-incubator code. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1466851/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461776] Re: Error messages are encoded to HTML entity
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1461776
Title:
Error messages are encoded to HTML entity
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Status in Glance kilo series:
Fix Committed
Bug description:
If you pass min_disk or min_ram as -1 to the image create command,
then it shows following error message on the command prompt.
$ glance image-create --name test --container-format bare --disk-format raw
--file filename --min-disk -1
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Image min_disk
must be gt;= 0 ('-1' specified). (HTTP 400)
The above error message will be rendered correctly in the browser but
it is not readable on the command prompt.
This issue belongs to v1 API, in case of v2 api it returns proper error
message:
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Cannot be a
negative value (HTTP 400)
So we can make this error message consistent for both the APIs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1461776/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1443464] Re: glance/doc/source/architecture.rst has non-ascii characters”
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1443464 Title: glance/doc/source/architecture.rst has non-ascii characters” Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: Basic architecture section has non-ascii (utf-8) characters. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1443464/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467589] Re: Remove Cinder V1 supprt
** Also affects: tempest Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1467589 Title: Remove Cinder V1 supprt Status in Cinder: In Progress Status in OpenStack Compute (Nova): In Progress Status in Rally: In Progress Status in Tempest: New Bug description: Cinder created v2 support in the Grizzly release. This is to track progress in removing v1 support in other projects. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1467589/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467110] Re: glance.tests.functional.test_reload.TestReload.test_reload fails on FreeBSD
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1467110 Title: glance.tests.functional.test_reload.TestReload.test_reload fails on FreeBSD Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: The glance.tests.functional.test_reload.TestReload.test_reload test fails on FreeBSD because it uses 'strace' that's usually not present on FreeBSD. Traceback (most recent call last): File glance/tests/functional/test_reload.py, line 113, in test_reload self.start_servers(fork_socket=False, **vars(self)) File glance/tests/functional/__init__.py, line 768, in start_servers self.start_with_retry(self.api_server, 'api_port', 3, **kwargs) File glance/tests/functional/__init__.py, line 738, in start_with_retry launch_msg = self.wait_for_servers([server], expect_launch) File glance/tests/functional/__init__.py, line 829, in wait_for_servers execute(cmd, raise_error=False, expect_exit=False) File glance/tests/utils.py, line 307, in execute env=env) File /usr/local/lib/python2.7/subprocess.py, line 710, in __init__ errread, errwrite) File /usr/local/lib/python2.7/subprocess.py, line 1335, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory Ran 1 tests in 136.994s (+6.953s) FAILED (id=2, failures=1) error: testr failed (1) strace _could_ be installed from FreeBSD ports [1], however, it's available only for i386 and that's a huge limitation. 1: http://www.freshports.org/devel/strace/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1467110/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1434578] Re: Inefficient db call while doing a image_get with image_id.
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1434578 Title: Inefficient db call while doing a image_get with image_id. Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: I am running MySql as backend and I can see two queries being done when I try to get an image. In first query the tables images, image_locations and image_properties are joined and in another query tags related to that image are fetched from the db. These two can be combined to one query which will do a join of images, image_locations, image_properties and image_tags (join of these four tables happen when a call is made to get a list of all images). Reference: https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L69-74 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1434578/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1455314] Re: Typo in doc about configuation
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1455314 Title: Typo in doc about configuation Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: You can find the typo by searching configuation in http://docs.openstack.org/developer/glance/controllingservers.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1455314/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1434501] Re: Incorrect error message while listing members for a public image.
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1434501
Title:
Incorrect error message while listing members for a public image.
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
This happens with glance api version 2.
request:
for i in glance.image_members.list('dc782b57-2e28-4339-a9ec-c1967848c4ec'):
print i
response:
html
head
title403 Forbidden/title
/head
body
h1403 Forbidden/h1
Not allowed to list members for image
dc782b57-2e28-4339-a9ec-c1967848c4ec.br /br /
/body
/html (HTTP 403)
The response should be:
html
head
title403 Forbidden/title
/head
body
h1403 Forbidden/h1
Public images do not have members.br /br /
/body
/html (HTTP 403)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1434501/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1433785] Re: Tests error out when running tests with --debug after oslo.log graduation
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1433785 Title: Tests error out when running tests with --debug after oslo.log graduation Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Bug description: If you want to debug into the tests, you might do ./run_tests.sh --debug -V glance.tests.unit.v1.test_api.TestGlanceAPI This translated to python -m testtools.run glance.tests.unit.v1.test_api.TestGlanceAPI which errors out because we attempt to set CONF.debug but the debug option hasn't been registered. This is registered by oslo.log and when using testtools.run, it seems to not be registered (probably because of how testtools imports tests). This prevents tests from running properly and from debugging into them. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1433785/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1423973] Re: Use choices from oslo_config
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1423973 Title: Use choices from oslo_config Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Identity (Keystone) Middleware: In Progress Status in OpenStack Compute (Nova): Fix Committed Bug description: Support went into oslo_config recently that will allow us to use the choices keyword argument from argparse [1]. We should look at leveraging this in Keystone. [1] https://github.com/openstack/oslo.config/blame/578f9f4e60f58c210a9e1cb455925b9f310fe10e/oslo_config/cfg.py#L932 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1423973/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394316] Re: glance-manage does not display basic options if run without any arguments
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1394316
Title:
glance-manage does not display basic options if run without any
arguments
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Bug description:
glance-manage isn't very helpful if it is run without any arguments.
Compare against nova-manage and cinder-manage:
$ nova-manage
usage: nova-manage [-h] [--config-dir DIR] [--config-file PATH] [--debug]
[--log-config-append PATH] [--log-date-format DATE_FORMAT]
[--log-dir LOG_DIR] [--log-file PATH] [--log-format FORMAT]
[--nodebug] [--nouse-syslog] [--nouse-syslog-rfc-format]
[--noverbose] [--syslog-log-facility SYSLOG_LOG_FACILITY]
[--use-syslog] [--use-syslog-rfc-format] [--verbose]
[--version] [--remote_debug-host REMOTE_DEBUG_HOST]
[--remote_debug-port REMOTE_DEBUG_PORT]
{version,bash-completion,shell,logs,db,vm,agent,host,flavor,vpn,floating,project,account,network,service,cell,fixed}
...
nova-manage: error: too few arguments
$ cinder-manage
OpenStack Cinder version: 2014.2
/usr/local/bin/cinder-manage category action [args]
Available categories:
db
volume
host
shell
logs
service
config
version
backup
Glance-manage, on the other hand shows very little extra information:
$ glance-manage
usage: glance-manage [options] cmd
glance-manage: error: too few arguments
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1394316/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467982] [NEW] Profiler raises an error when it is enabled
Public bug reported:
Description:
When OSProfiler is enabled in Glance API and Registry, they raise the
following exception:
CRITICAL glance [-] AttributeError: 'module' object has no attribute 'messaging'
TRACE glance Traceback (most recent call last):
TRACE glance File /usr/bin/glance-api, line 10, in module
TRACE glance sys.exit(main())
TRACE glance File /usr/lib/python2.7/site-packages/glance/cmd/api.py, line
80, in main
TRACE glance notifier.messaging, {},
TRACE glance AttributeError: 'module' object has no attribute 'messaging'
TRACE glance
Steps to reproduce:
1. Enable profiler in glance-api.conf and glance-registry.conf
[profiler]
enabled = True
2. Restart API and Registry Services
Expected Behavior:
Start services with profiler enabled
** Affects: glance
Importance: Undecided
Assignee: Obed N Munoz (obed-n-munoz)
Status: New
** Changed in: glance
Assignee: (unassigned) = Obed N Munoz (obed-n-munoz)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1467982
Title:
Profiler raises an error when it is enabled
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Description:
When OSProfiler is enabled in Glance API and Registry, they raise the
following exception:
CRITICAL glance [-] AttributeError: 'module' object has no attribute
'messaging'
TRACE glance Traceback (most recent call last):
TRACE glance File /usr/bin/glance-api, line 10, in module
TRACE glance sys.exit(main())
TRACE glance File /usr/lib/python2.7/site-packages/glance/cmd/api.py,
line 80, in main
TRACE glance notifier.messaging, {},
TRACE glance AttributeError: 'module' object has no attribute 'messaging'
TRACE glance
Steps to reproduce:
1. Enable profiler in glance-api.conf and glance-registry.conf
[profiler]
enabled = True
2. Restart API and Registry Services
Expected Behavior:
Start services with profiler enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1467982/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1434370] Re: common/README still references openstack-common
** Changed in: cinder Status: Fix Committed = Fix Released ** Changed in: cinder Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1434370 Title: common/README still references openstack-common Status in Cinder: 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 Committed Status in Manila: Fix Released Status in Openstack Database (Trove): Fix Committed Bug description: The README under openstack/common references openstack-common, but the link (correctly) points to oslo-incubator. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1434370/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1436877] Re: metadef JSON files need updating for the Kilo release
** Changed in: glance Status: Fix Committed = Fix Released ** Changed in: glance Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1436877 Title: metadef JSON files need updating for the Kilo release Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Glance kilo series: Fix Released Bug description: Since Juno, some new hardware properties have been added to Nova that should be included in the Kilo versions of the metadef JSON files. This bug, would add in new properties or objects found in Nova and update properties or objects if the definitions have changed. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1436877/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467935] [NEW] widget attributes changed
Public bug reported: In Django 1.8, widget attribute data-date-picker=True will be rendered as 'data-date-picker'. To preserve current behavior, use the string 'True' instead of the boolean value. ** Affects: horizon Importance: Undecided Assignee: Matthias Runge (mrunge) Status: In Progress -- 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/1467935 Title: widget attributes changed Status in OpenStack Dashboard (Horizon): In Progress Bug description: In Django 1.8, widget attribute data-date-picker=True will be rendered as 'data-date-picker'. To preserve current behavior, use the string 'True' instead of the boolean value. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1467935/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461835] Re: devstack fails due to error:'lockfile' is not in global-requirements.txt 2014.2.3
Fetch the icehouse/juno branch of devstack instead of master. ** Changed in: devstack Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1461835 Title: devstack fails due to error:'lockfile' is not in global- requirements.txt 2014.2.3 Status in devstack - openstack dev environments: Invalid Status in OpenStack Identity (Keystone): Invalid Bug description: STacking of controller fails at keystone update with error 'lockfile' is not in global-requirements.txt.The system is built from 2014.2.3 tag Log: 2015-06-04 05:01:36.180 | + git checkout 2014.2.3 2015-06-04 05:01:36.272 | Note: checking out '2014.2.3'. 2015-06-04 05:01:36.272 | 2015-06-04 05:01:36.272 | You are in 'detached HEAD' state. You can look around, make experimental 2015-06-04 05:01:36.272 | changes and commit them, and you can discard any commits you make in this 2015-06-04 05:01:36.272 | state without impacting any branches by performing another checkout. 2015-06-04 05:01:36.272 | 2015-06-04 05:01:36.272 | If you want to create a new branch to retain commits you create, you may 2015-06-04 05:01:36.272 | do so (now or later) by using -b with the checkout command again. Example: 2015-06-04 05:01:36.272 | 2015-06-04 05:01:36.272 | git checkout -b new_branch_name 2015-06-04 05:01:36.272 | 2015-06-04 05:01:36.272 | HEAD is now at 91a3387... Merge Updated from global requirements into stable/juno 2015-06-04 05:01:36.274 | + cd /opt/stack/keystone 2015-06-04 05:01:36.274 | + git show --oneline 2015-06-04 05:01:36.275 | + head -1 2015-06-04 05:01:36.279 | 91a3387 Merge Updated from global requirements into stable/juno 2015-06-04 05:01:36.280 | + cd /opt/devstack 2015-06-04 05:01:36.280 | + setup_develop /opt/stack/keystone 2015-06-04 05:01:36.280 | + local project_dir=/opt/stack/keystone 2015-06-04 05:01:36.280 | + setup_package_with_req_sync /opt/stack/keystone -e 2015-06-04 05:01:36.280 | + local project_dir=/opt/stack/keystone 2015-06-04 05:01:36.281 | + local flags=-e 2015-06-04 05:01:36.281 | ++ cd /opt/stack/keystone 2015-06-04 05:01:36.281 | ++ git diff --exit-code 2015-06-04 05:01:36.309 | + local update_requirements= 2015-06-04 05:01:36.309 | + [[ '' != \c\h\a\n\g\e\d ]] 2015-06-04 05:01:36.310 | + [[ strict == \s\o\f\t ]] 2015-06-04 05:01:36.310 | + cd /opt/stack/requirements 2015-06-04 05:01:36.310 | + python update.py /opt/stack/keystone 2015-06-04 05:01:36.410 | Version change for: pbr, webob, eventlet, greenlet, netaddr, pastedeploy, paste, routes, six, sqlalchemy, sqlalchemy-migrate, passlib, iso8601, python-keystoneclient, keystonemiddleware, oslo.config, oslo.messaging, oslo.db, oslo.i18n, oslo.serialization, oslo.utils, babel, oauthlib, dogpile.cache, pycadf, posix-ipc 2015-06-04 05:01:36.410 | Updated /opt/stack/keystone/requirements.txt: 2015-06-04 05:01:36.410 | pbr=0.6,!=0.7,1.0- pbr=0.11,2.0 2015-06-04 05:01:36.410 | WebOb=1.2.3,=1.3.1 - WebOb=1.2.3 2015-06-04 05:01:36.411 | eventlet=0.15.1,=0.15.2 - eventlet=0.17.3 2015-06-04 05:01:36.411 | greenlet=0.3.2,=0.4.2- greenlet=0.3.2 2015-06-04 05:01:36.411 | netaddr=0.7.12,=0.7.13 - netaddr=0.7.12 2015-06-04 05:01:36.411 | PasteDeploy=1.5.0,=1.5.2 - PasteDeploy=1.5.0 2015-06-04 05:01:36.411 | Paste=1.7.5.1 - Paste 2015-06-04 05:01:36.411 | Routes=1.12.3,!=2.0,=2.1 - Routes=1.12.3,!=2.0 2015-06-04 05:01:36.411 | six=1.7.0,=1.9.0 - six=1.9.0 2015-06-04 05:01:36.411 | SQLAlchemy=0.8.4,=0.9.99,!=0 - SQLAlchemy=0.9.7,=0.9.99 2015-06-04 05:01:36.411 | sqlalchemy-migrate==0.9.1 - sqlalchemy-migrate=0.9.6 2015-06-04 05:01:36.411 | passlib=1.6.2 - passlib 2015-06-04 05:01:36.411 | iso8601=0.1.9,=0.1.10- iso8601=0.1.9 2015-06-04 05:01:36.411 | python-keystoneclient=0.10.0, - python-keystoneclient=1.3.0 2015-06-04 05:01:36.411 | keystonemiddleware=1.0.0,1.4 - keystonemiddleware=1.5.0 2015-06-04 05:01:36.411 | oslo.config=1.4.0,=1.6.0 # A - oslo.config=1.11.0 # Apache-2.0 2015-06-04 05:01:36.411 | oslo.messaging=1.4.0,1.5.0 - oslo.messaging=1.8.0 # Apache-2.0 2015-06-04 05:01:36.411 | oslo.db=1.0.0,1.1 # Apache- - oslo.db=1.10.0 # Apache-2.0 2015-06-04 05:01:36.411 | oslo.i18n=1.0.0,=1.3.1 # Apa - oslo.i18n=1.5.0 # Apache-2.0 2015-06-04 05:01:36.411 | oslo.serialization=1.0.0,=1. - oslo.serialization=1.4.0 # Apache-2.0 2015-06-04 05:01:36.411 | oslo.utils=1.0.0,=1.2.1 # Ap - oslo.utils=1.4.0 # Apache-2.0 2015-06-04 05:01:36.411 | Babel=1.3,=1.3 - Babel=1.3 2015-06-04 05:01:36.411 |
[Yahoo-eng-team] [Bug 1467927] [NEW] Odd number of vCPUs breaks 'prefer' threads policy
Public bug reported:
Using a CPU policy of dedicated ('hw:cpu_policy=dedicated') results in
vCPUs being pinned to pCPUs, per the original blueprint:
http://specs.openstack.org/openstack/nova-
specs/specs/kilo/implemented/virt-driver-cpu-pinning.html
When scheduling instance with this extra spec there appears to be an
implicit use of the 'prefer' threads policy, i.e. where possible vCPUs
are pinned to thread siblings first. This is implicit because the
threads policy aspect of this spec has not yet been implemented.
However, this implicit 'prefer' policy breaks when a VM with an odd
number of vCPUs is booted. This has been seen on a Hyper-Threading-
enabled host where sibling sets are two long, but it would presumably
happen on any host where the number of siblings (or any number between
this value and one) is not an factor of the number of vCPUs (i.e. vCPUs
% n != 0, for siblings = n 0).
It is reasonable to assume that a three vCPU VM, for example, should try
best effort and use siblings for at the first two vCPUs of the VM
(assuming you're on a host system with HyperThreading and sibling sets
are of length two). This would give us a true best effort
implementation.
---
# Testing Configuration
Testing was conducted on a single-node, Fedora 21-based
(3.17.8-300.fc21.x86_64) OpenStack instance (built with devstack). The
system is a dual-socket, 10 core, HT-enabled system (2 sockets * 10
cores * 2 threads = 40 pCPUs. 0-9,20-29 = node0, 10-19,30-39 = node1).
Two flavors were used:
openstack flavor create --ram 4096 --disk 20 --vcpus 3 demo.odd
nova flavor-key demo.odd set hw:cpu_policy=dedicated
openstack flavor create --ram 4096 --disk 20 --vcpus 4 demo.even
nova flavor-key demo.even set hw:cpu_policy=dedicated
# Results
Correct case (even number of vCPUs)
=
The output from 'virsh dumpxml [ID]' for the four vCPU VM is given
below. Similar results can be seen for varying even numbers of vCPUs
(2, 4, 10 tested):
cputune
shares4096/shares
vcpupin vcpu='0' cpuset='3'/
vcpupin vcpu='1' cpuset='23'/
vcpupin vcpu='2' cpuset='26'/
vcpupin vcpu='3' cpuset='6'/
emulatorpin cpuset='3,6,23,26'/
/cputune
Incorrect case (odd number of vCPUs)
==
The output from 'virsh dumpxml [ID]' for the three vCPU VM is given
below. Similar results can be seen for varying odd numbers of vCPUs
(3, 5 tested):
cputune
shares3072/shares
vcpupin vcpu='0' cpuset='1'/
vcpupin vcpu='1' cpuset='0'/
vcpupin vcpu='2' cpuset='25'/
emulatorpin cpuset='0-1,25'/
/cputune
This isn't correct. We would expect something closer to this:
cputune
shares3072/shares
vcpupin vcpu='0' cpuset='0'/
vcpupin vcpu='1' cpuset='20'/
vcpupin vcpu='2' cpuset='1'/
emulatorpin cpuset='0-1,20'/
/cputune
** Affects: nova
Importance: Undecided
Status: New
** Tags: libvirt
--
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/1467927
Title:
Odd number of vCPUs breaks 'prefer' threads policy
Status in OpenStack Compute (Nova):
New
Bug description:
Using a CPU policy of dedicated ('hw:cpu_policy=dedicated') results in
vCPUs being pinned to pCPUs, per the original blueprint:
http://specs.openstack.org/openstack/nova-
specs/specs/kilo/implemented/virt-driver-cpu-pinning.html
When scheduling instance with this extra spec there appears to be an
implicit use of the 'prefer' threads policy, i.e. where possible vCPUs
are pinned to thread siblings first. This is implicit because the
threads policy aspect of this spec has not yet been implemented.
However, this implicit 'prefer' policy breaks when a VM with an odd
number of vCPUs is booted. This has been seen on a Hyper-Threading-
enabled host where sibling sets are two long, but it would
presumably happen on any host where the number of siblings (or any
number between this value and one) is not an factor of the number of
vCPUs (i.e. vCPUs % n != 0, for siblings = n 0).
It is reasonable to assume that a three vCPU VM, for example, should
try best effort and use siblings for at the first two vCPUs of the VM
(assuming you're on a host system with HyperThreading and sibling sets
are of length two). This would give us a true best effort
implementation.
---
# Testing Configuration
Testing was conducted on a single-node, Fedora 21-based
(3.17.8-300.fc21.x86_64) OpenStack instance (built with devstack). The
system is a dual-socket, 10 core, HT-enabled system (2 sockets * 10
cores * 2 threads = 40 pCPUs. 0-9,20-29 = node0, 10-19,30-39 =
node1). Two flavors were used:
openstack flavor create --ram 4096 --disk 20 --vcpus 3 demo.odd
nova flavor-key demo.odd set
[Yahoo-eng-team] [Bug 1467950] [NEW] test_floatingip and test_keypair tests are failing
Public bug reported: The test above are failing with different reasons. Please note that they were working until yesterday (2015-06-22). test_floatingip: 2015-06-23 12:30:20.815 | 2015-06-23 12:30:20.797 | Traceback (most recent call last): 2015-06-23 12:30:20.817 | 2015-06-23 12:30:20.799 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_floatingip.py, line 25, in test_floatingip 2015-06-23 12:30:20.819 | 2015-06-23 12:30:20.801 | floating_ip = floatingip_page.allocate_floatingip() 2015-06-23 12:30:20.821 | 2015-06-23 12:30:20.803 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/access_and_security/floatingipspage.py, line 62, in allocate_floatingip 2015-06-23 12:30:20.822 | 2015-06-23 12:30:20.804 | self.floatingips_table.allocate_ip_to_project.click() 2015-06-23 12:30:20.824 | 2015-06-23 12:30:20.806 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/baseregion.py, line 59, in __getattr__ 2015-06-23 12:30:20.826 | 2015-06-23 12:30:20.808 | return self._dynamic_properties[name]() 2015-06-23 12:30:20.827 | 2015-06-23 12:30:20.810 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/baseregion.py, line 78, in __call__ 2015-06-23 12:30:20.829 | 2015-06-23 12:30:20.811 | return result if self.index is None else result[self.index] 2015-06-23 12:30:20.830 | 2015-06-23 12:30:20.813 | IndexError: list index out of range Most likely the page was changed. test_keypair: 2015-06-23 12:30:22.598 | 2015-06-23 12:30:22.581 | Traceback (most recent call last): 2015-06-23 12:30:22.600 | 2015-06-23 12:30:22.582 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_keypair.py, line 28, in test_keypair 2015-06-23 12:30:22.601 | 2015-06-23 12:30:22.583 | self.assertTrue(keypair_page.is_keypair_present(self.KEYPAIR_NAME)) 2015-06-23 12:30:22.603 | 2015-06-23 12:30:22.585 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/unittest2/case.py, line 678, in assertTrue 2015-06-23 12:30:22.604 | 2015-06-23 12:30:22.586 | raise self.failureException(msg) 2015-06-23 12:30:22.606 | 2015-06-23 12:30:22.588 | AssertionError: False is not true Either changed page, or an active polling of the ready state is needed. See for example http://logs.openstack.org/72/193072/1/gate/gate-horizon-dsvm-integration/dd294c6/console.html#_2015-06-23_12_30_20_817 The bug is to track the skip patch which will follow and the future investigations of the real issues, that needs to be fixed. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1467950 Title: test_floatingip and test_keypair tests are failing Status in OpenStack Dashboard (Horizon): New Bug description: The test above are failing with different reasons. Please note that they were working until yesterday (2015-06-22). test_floatingip: 2015-06-23 12:30:20.815 | 2015-06-23 12:30:20.797 | Traceback (most recent call last): 2015-06-23 12:30:20.817 | 2015-06-23 12:30:20.799 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_floatingip.py, line 25, in test_floatingip 2015-06-23 12:30:20.819 | 2015-06-23 12:30:20.801 | floating_ip = floatingip_page.allocate_floatingip() 2015-06-23 12:30:20.821 | 2015-06-23 12:30:20.803 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/access_and_security/floatingipspage.py, line 62, in allocate_floatingip 2015-06-23 12:30:20.822 | 2015-06-23 12:30:20.804 | self.floatingips_table.allocate_ip_to_project.click() 2015-06-23 12:30:20.824 | 2015-06-23 12:30:20.806 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/baseregion.py, line 59, in __getattr__ 2015-06-23 12:30:20.826 | 2015-06-23 12:30:20.808 | return self._dynamic_properties[name]() 2015-06-23 12:30:20.827 | 2015-06-23 12:30:20.810 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/baseregion.py, line 78, in __call__ 2015-06-23 12:30:20.829 | 2015-06-23 12:30:20.811 | return result if self.index is None else result[self.index] 2015-06-23 12:30:20.830 | 2015-06-23 12:30:20.813 | IndexError: list index out of range Most likely the page was changed. test_keypair: 2015-06-23 12:30:22.598 | 2015-06-23 12:30:22.581 | Traceback (most recent call last): 2015-06-23 12:30:22.600 | 2015-06-23 12:30:22.582 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_keypair.py, line 28, in test_keypair 2015-06-23 12:30:22.601 | 2015-06-23 12:30:22.583 |
[Yahoo-eng-team] [Bug 1434370] Re: common/README still references openstack-common
** Changed in: trove 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/1434370 Title: common/README still references openstack-common Status in Cinder: 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 Committed Status in Manila: Fix Released Status in Openstack Database (Trove): Fix Released Bug description: The README under openstack/common references openstack-common, but the link (correctly) points to oslo-incubator. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1434370/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 933498] Re: List Volumes should support filtering
** Changed in: tempest
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/933498
Title:
List Volumes should support filtering
Status in OpenStack Compute (Nova):
Confirmed
Status in Tempest:
Fix Released
Bug description:
List Volumes Filtered by Name is returning all volumes
The name parameter (with a text value) is passed to get the volumes of
that particular name.
But Instead it is returning all the volumes in the server
Nosetest Log:
FAIL: Positive: Should return the details of volume by the name
--
Traceback (most recent call last):
File
/home/unnimaya/MYTempest/VOLUMES/tempest/tempest/tests/test_volumes.py, line
159, in test_volume_list_filter_by_name
self.assertEqual(len(fetched_volumes), 1)
AssertionError: 5 != 1
==
Nova-Api Log
List of all the volumes
muralik@openstack27:~/source/csbu-qa/nova/tests$ ./apitool.py GET os-volumes
apitool
apitool
apitool
apitool
apitool
RESP:{'date': 'Fri, 17 Feb 2012 10:40:00 GMT', 'vary': 'X-Auth-Token',
'content-length': '1444', 'status': '200', 'content-type': 'application/json;
charset=UTF-8'} {access: {token: {expires: 2012-02-18T00:18:26,
tenants: [{id: 74da8012b13c4d9195f11c10605ec7d0, name: demo}], id:
8a65e999-4c36-4305-bbd6-e6b0a7c6342f, tenant: {id:
74da8012b13c4d9195f11c10605ec7d0, name: demo}}, serviceCatalog:
[{endpoints: [{id: 1, region: RegionOne, publicURL:
http://10.233.52.27:8774/v1.1/74da8012b13c4d9195f11c10605ec7d0;,
internalURL:
http://10.233.52.27:8774/v1.1/74da8012b13c4d9195f11c10605ec7d0;, tenantId:
74da8012b13c4d9195f11c10605ec7d0}], type: compute, name: nova},
{endpoints: [{id: 2, region: RegionOne, internalURL:
http://10.233.52.27:8773/services/Cloud;, publicURL:
http://10.233.52.27:8773/services/Cloud}], type: ec2, name: ec2},
{endpoints: [{id: 3, region: RegionOne, internalURL:
http://10.233.52.27:9292/v1;, publicURL: http://10.233.52.27:9292/v1}],
type: image, name: glance}, {endpoints: [{id: 4, region:
RegionOne, internalURL: http://10.233.52.27:5000/v2.0;, publicURL:
http://10.233.52.27:5000/v2.0}], type: identity, name: keystone}],
user: {id: 8837101af2434cdfbd346e101906ba0a, roles: [{name: Member,
id: 2, tenantId: 74da8012b13c4d9195f11c10605ec7d0}, {name:
sysadmin, id: 5, tenantId: 74da8012b13c4d9195f11c10605ec7d0},
{name: netadmin, id: 6, tenantId:
74da8012b13c4d9195f11c10605ec7d0}], name: demo}}}
REQ: curl -i
http://10.233.52.27:8774/v1.1/74da8012b13c4d9195f11c10605ec7d0/os-
volumes -X GET -H X-Auth-Project-Id: demo -H User-Agent: python-
novaclient -H Accept: application/json -H X-Auth-Token:
8a65e999-4c36-4305-bbd6-e6b0a7c6342f
RESP:{'status': '200', 'content-length': '485', 'content-location':
u'http://10.233.52.27:8774/v1.1/74da8012b13c4d9195f11c10605ec7d0/os-
volumes', 'x-compute-request-id': 'req-50ca9204-fb50-4eab-b97d-
1ff062e0690d', 'date': 'Fri, 17 Feb 2012 10:40:00 GMT', 'content-
type': 'application/json'} {volumes: [{status: available,
displayDescription: null, availabilityZone: nova, displayName:
null, attachments: [{}], volumeType: null, snapshotId: null,
size: 1, id: 6, createdAt: 2012-02-16 21:00:26, metadata:
{}}, {status: available, displayDescription: null,
availabilityZone: nova, displayName: test, attachments:
[{}], volumeType: null, snapshotId: null, size: 2, id: 7,
createdAt: 2012-02-17 10:03:23, metadata: {}}]}
--- START OF RESPONSE ---
{ u'volumes': [ { u'attachments': [{ }],
u'availabilityZone': u'nova',
u'createdAt': u'2012-02-16 21:00:26',
u'displayDescription': None,
u'displayName': None,
u'id': 6,
u'metadata': { },
u'size': 1,
u'snapshotId': None,
u'status': u'available',
u'volumeType': None},
{ u'attachments': [{ }],
u'availabilityZone': u'nova',
u'createdAt': u'2012-02-17 10:03:23',
u'displayDescription': None,
u'displayName': u'test',
u'id': 7,
u'metadata': { },
u'size': 2,
u'snapshotId': None,
u'status': u'available',
u'volumeType': None}]}
--- ENF OF RESPONSE ---
Now List of volumes filtered by Name should return the volume with the
specified name , but it is returning all the volumes.
[Yahoo-eng-team] [Bug 1350149] Re: mysqldb + eventlet = potential deadlocks
** Changed in: oslo.db Status: Fix Committed = Fix Released ** Changed in: oslo.db Milestone: None = 1.12.0 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1350149 Title: mysqldb + eventlet = potential deadlocks Status in OpenStack Neutron (virtual network service): Fix Committed Status in Oslo Database library: Fix Released Bug description: mysqldb is a C library, and thus can't be monkeypatched by eventlet. With eventlet, this series of events may lead to a deadlock: 1. greenlet A opens a mysql DB transaction, does some stuff 2. greenlet A yields, perhaps by making another unrelated blocking operation (eg: sending a network request) 3. greenlet B is scheduled and opens a mysql DB transaction that conflicts with A's 4. greenlet B enters mysqldb and the C call blocks, waiting until A completes Note that this is a deadlock on the client side, since A will never be scheduled again - and not a typical example of waiting for a transaction lock. The python process is now wedged until a mysqldb deadlock timer expires and B raises an exception. The mysql deadlock timer has a distinctive Lock wait timeout exceeded; try restarting transaction error message. There are bugs relating to specific instances of this, like bug 1298355 and bug 1313794. .. but fundamentally this issue is generic across any use of mysqldb + eventlet + any code that yields the greenlet while holding a lock inside the database server. This bug is to track the generic issue across all such instances of the above pattern. Note it is not specific to oslo.db. See also this blueprint for a proposed fix (switch to a different mysql driver): - https://blueprints.launchpad.net/oslo/+spec/switch-to-mysql-connector To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1350149/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1468012] [NEW] compute monitors should be loaded via stevedore
Public bug reported:
The monitor plugins in /nova/compute/monitors/ are currently loaded via
a nova.loadables.BaseLoader subclass called ResourceMonitorHandler. We
should be able to get rid of the nova.loadables Python module and just
use the stevedore library, which is purpose-built for extension loading
and managing like this.
This would have the side benefit of us being able to deprecate the
following CONF options:
compute_monitors_opts = [
cfg.MultiStrOpt('compute_available_monitors',
default=['nova.compute.monitors.all_monitors'],
help='Monitor classes available to the compute which may '
'be specified more than once.'),
cfg.ListOpt('compute_monitors',
default=[],
help='A list of monitors that can be used for getting '
'compute metrics.'),
]
Since stevedore's ExtensionManager loads extensions via standard Python
setuptools entry_points.
** Affects: nova
Importance: Wishlist
Assignee: Jay Pipes (jaypipes)
Status: Triaged
** Tags: low-hanging-fruit
--
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/1468012
Title:
compute monitors should be loaded via stevedore
Status in OpenStack Compute (Nova):
Triaged
Bug description:
The monitor plugins in /nova/compute/monitors/ are currently loaded
via a nova.loadables.BaseLoader subclass called
ResourceMonitorHandler. We should be able to get rid of the
nova.loadables Python module and just use the stevedore library, which
is purpose-built for extension loading and managing like this.
This would have the side benefit of us being able to deprecate the
following CONF options:
compute_monitors_opts = [
cfg.MultiStrOpt('compute_available_monitors',
default=['nova.compute.monitors.all_monitors'],
help='Monitor classes available to the compute which may '
'be specified more than once.'),
cfg.ListOpt('compute_monitors',
default=[],
help='A list of monitors that can be used for getting '
'compute metrics.'),
]
Since stevedore's ExtensionManager loads extensions via standard
Python setuptools entry_points.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1468012/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1277104] Re: wrong order of assertEquals args
** Changed in: trove 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/1277104 Title: wrong order of assertEquals args Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Triaged Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in Messaging API for OpenStack: Fix Released Status in Oslo Policy: Fix Released Status in Python client library for Ceilometer: In Progress Status in Python client library for Glance: Fix Released Status in Python client library for Ironic: Fix Released Status in Python client library for Nova: Fix Released Status in OpenStack Command Line Client: Fix Released Status in Python client library for Sahara (ex. Savanna): Fix Released Status in Python client library for Swift: In Progress Status in Trove client binding: Fix Released Status in Rally: Confirmed Status in Openstack Database (Trove): Fix Released Bug description: Args of assertEquals method in ceilometer.tests are arranged in wrong order. In result when test fails it shows incorrect information about observed and actual data. It's found more than 2000 times. Right order of arguments is expected, actual. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1277104/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467982] Re: Profiler raises an error when it is enabled
** Changed in: glance
Importance: Undecided = Low
** Tags added: kilo-backport-potential
** Also affects: glance/liberty
Importance: Low
Assignee: Obed N Munoz (obed-n-munoz)
Status: In Progress
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance/kilo
Status: New = Confirmed
** Changed in: glance/kilo
Importance: Undecided = Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1467982
Title:
Profiler raises an error when it is enabled
Status in OpenStack Image Registry and Delivery Service (Glance):
In Progress
Status in Glance kilo series:
Confirmed
Status in Glance liberty series:
In Progress
Bug description:
Description:
When OSProfiler is enabled in Glance API and Registry, they raise the
following exception:
CRITICAL glance [-] AttributeError: 'module' object has no attribute
'messaging'
TRACE glance Traceback (most recent call last):
TRACE glance File /usr/bin/glance-api, line 10, in module
TRACE glance sys.exit(main())
TRACE glance File /usr/lib/python2.7/site-packages/glance/cmd/api.py,
line 80, in main
TRACE glance notifier.messaging, {},
TRACE glance AttributeError: 'module' object has no attribute 'messaging'
TRACE glance
Steps to reproduce:
1. Enable profiler in glance-api.conf and glance-registry.conf
[profiler]
enabled = True
2. Restart API and Registry Services
Expected Behavior:
Start services with profiler enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1467982/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467589] Re: Remove Cinder V1 supprt
** Also affects: devstack Importance: Undecided Status: New ** Changed in: devstack Assignee: (unassigned) = Ivan Kolodyazhny (e0ne) ** Changed in: devstack Status: New = In Progress -- 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/1467589 Title: Remove Cinder V1 supprt Status in Cinder: In Progress Status in devstack - openstack dev environments: In Progress Status in OpenStack Compute (Nova): In Progress Status in Rally: In Progress Status in Tempest: New Bug description: Cinder created v2 support in the Grizzly release. This is to track progress in removing v1 support in other projects. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1467589/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1468009] [NEW] disabling arp spoofing for 0.0.0.0/0 doesn't work
Public bug reported: If 0.0.0.0/0 is in the allowed address pairs rules, the rule to allow that will fail to install because of the /0 prefix. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) = Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1468009 Title: disabling arp spoofing for 0.0.0.0/0 doesn't work Status in OpenStack Neutron (virtual network service): New Bug description: If 0.0.0.0/0 is in the allowed address pairs rules, the rule to allow that will fail to install because of the /0 prefix. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1468009/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1465687] Re: use fixed ip address cannot ping/ssh instance from controller node
** Changed in: neutron 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/1465687 Title: use fixed ip address cannot ping/ssh instance from controller node Status in OpenStack Neutron (virtual network service): Invalid Bug description: I found one question in openstack network. I configure nova.conf with multi_host = true in controller node and compute node. and set security group as below: nova secgroup-add-rule default tcp 22 22 0.0.0.0/0 nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0 and I create one neutron network, the type is gre, and subnet is 10.1.2.0/24. I can boot one instance successful and also the boot instance also can get one ip address from 10.1.2.0/24 subnet. from this instance, it can ping/ssh the controller node ip address, but from controller node , I can not ping/ssh the instance ip address. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1465687/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1421825] Re: Sample policy should allow user to validate and revoke own token
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1421825
Title:
Sample policy should allow user to validate and revoke own token
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
The sample policy doesn't allow a non-admin user to validate or revoke
their own token.
Steps to recreate:
0) Start with devstack
1) Get a token for a non-admin user
$ curl -i -H Content-Type: application/json -d '
{ auth: {
identity: {
methods: [password],
password: {
user: {
name: demo,
domain: { id: default },
password: demopwd
}
}
},
scope: {
project: {
name: demo,
domain: { id: default }
}
}
}
}' http://localhost:35357/v3/auth/tokens ; echo
$ TOKEN=e91bab6a52e44e39ba7ca63b04bb717b
2) Try to get the token using the token using v3:
$ curl -H X-Auth-Token: $TOKEN -H X-Subject-Token: $TOKEN
http://localhost:35357/v3/auth/tokens
{error: {message: You are not authorized to perform the requested
action: identity:validate_token (Disable debug mode to suppress these
details.), code: 403, title: Forbidden}}
3) Try to validate the token using the token using v3:
$ curl -I -H X-Auth-Token: $TOKEN -H X-Subject-Token: $TOKEN
http://localhost:35357/v3/auth/tokens
HTTP/1.1 403 Forbidden
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 185
Date: Fri, 13 Feb 2015 20:00:21 GMT
4) Try to get the token using the token using v2:
$ curl -H X-Auth-Token: $TOKEN http://localhost:35357/v2.0/tokens/$TOKEN
{error: {message: You are not authorized to perform the requested
action: identity:validate_token (Disable debug mode to suppress these
details.), code: 403, title: Forbidden}}
5) Try to validate the token using the token using v2:
$ curl -I -H X-Auth-Token: $TOKEN http://localhost:35357/v2.0/tokens/$TOKEN
HTTP/1.1 403 Forbidden
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 193
Date: Fri, 13 Feb 2015 20:11:49 GMT
6) Try to revoke the token using the token using v3:
$ curl -X DELETE -H X-Auth-Token: $TOKEN -H X-Subject-Token: $TOKEN
http://localhost:35357/v3/auth/tokens
{error: {message: You are not authorized to perform the requested
action: identity:revoke_token (Disable debug mode to suppress these details.),
code: 403, title: Forbidden}
7) Try to revoke the token using the token using v2:
$ curl -X DELETE -H X-Auth-Token: $TOKEN
http://localhost:35357/v2.0/tokens/$TOKEN
{error: {message: You are not authorized to perform the requested
action: admin_required (Disable debug mode to suppress these details.),
code: 403, title: Forbidden}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1421825/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1434370] Re: common/README still references openstack-common
** 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/1434370 Title: common/README still references openstack-common Status in Cinder: 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 Manila: Fix Released Status in Openstack Database (Trove): Fix Released Bug description: The README under openstack/common references openstack-common, but the link (correctly) points to oslo-incubator. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1434370/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1386773] Re: Project details request with long ID causes 500 error with DB2
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1386773
Title:
Project details request with long ID causes 500 error with DB2
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When using DB2 as the database, if you get project details with a really long
ID (even if it doesn't exist), the you get a 500 error instead of 404 Not Found:
$ curl -s -H X-Auth-Token: $TOKEN
http://localhost:35357/v3/projects/915eb1fb90d34430b1dafbc712889924asldkjsalkfdjlaksdjflkdsajflkdsajfdsasad
| python -m json.tool
{
error: {
code: 500,
message: An unexpected error prevented the server from fulfilling
your request: (DataError) ibm_db_dbi::DataError: Statement Execute Failed:
[IBM][CLI Driver] CLI0109E String data right truncation. SQLSTATE=22001
SQLCODE=-9 'SELECT project.id AS project_id, project.name AS project_name,
project.domain_id AS project_domain_id, project.description AS
project_description, project.enabled AS project_enabled, project.extra AS
project_extra \\nFROM project \\nWHERE project.id = ?'
('915eb1fb90d34430b1dafbc712889924asldkjsalkfdjlaksdjflkdsajflkdsajfdsasad',)
(Disable debug mode to suppress these details.),
title: Internal Server Error
}
}
I guess DB2 doesn't like getting a parameter that's longer than the
column.
This probably applies to other resources, too.
Seems like the right thing to do here is either check the length in
the SQL backend or catch this particular exception and reraise it as
NotFound. Seems safer and more efficient to check the length in the
SQL backend, although it's going to be a lot of changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1386773/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1379952] Re: API accepts tenant name for TenantId, fails, and provides not helpful message
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1379952 Title: API accepts tenant name for TenantId, fails, and provides not helpful message Status in OpenStack Identity (Keystone): Fix Released Bug description: When authenticating with Keystone's REST API, if I happen to provide my tenant name in the TenantId field, the resulting error tells me that I am not authorized for that tenant, even though all the information (user, pass, tenant) are correct. It *should* tell me that I just passed invalid data into a field that expects a UUID, which, as a user, would tell me exactly what was wrong. For what it's worth, in debugging my auth problem, I ended up tcpdump'ing keystone which led to this gem of a demonstration of the problem: http://paste.openstack.org/show/4v5JtwbGNu6QhQ3K5oQ1/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1379952/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1428124] Re: Missing tests to list projects by the parent_id
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1428124 Title: Missing tests to list projects by the parent_id Status in OpenStack Identity (Keystone): Fix Released Bug description: Although it is possible to perform GET /projects?parent_id=project_id [1], it is not tested. [1] https://github.com/openstack/keystone/blob/master/keystone/resource/controllers.py#L167 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1428124/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1425113] Re: list_projects_in_subtree() and list_project_parents() accepts invalid values
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1425113 Title: list_projects_in_subtree() and list_project_parents() accepts invalid values Status in OpenStack Identity (Keystone): Fix Released Bug description: The list_projects_in_subtree() and list_project_parents() method accepts invalid values of project_id (such as None and non-existent project_ids). To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1425113/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1426496] Re: Create project with invalid domain_id
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1426496
Title:
Create project with invalid domain_id
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Right now it is possible to create a project with an invalid domain_id
(we do not check if the domain_id exists in the create_project method)
if we are using engines that not support foreign keys, such as
sqllite:
https://github.com/openstack/keystone/blob/master/keystone/resource/core.py#L87-L116
If we are using engines that support foreign keys, the error returned
is not really helpfull:
{
error: {
code: 500,
message: An unexpected error occurred when trying to store project
(Disable debug mode to suppress these details.),
title: Internal Server Error
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1426496/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1421968] Re: List Endpoint Groups Associated with project not routed
** 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/1421968
Title:
List Endpoint Groups Associated with project not routed
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
I was looking through the sample policy.json file and noticed that the
identity:list_endpoint_groups_for_project target doesn't have a corresponding
mapping in the routers[1]. Looks like there's supposed to be a router mapping
/v3/OS-EP-FILTER/endpoint_groups/projects/{project_id}[2] to
list_endpoint_groups_for_project. Since there's no mapping for the path, the
keystone server is just going to 404.
[1] This would be in
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/contrib/endpoint_filter/routers.py
[2]
http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-ep-filter-ext.html#list-endpoint-groups-associated-with-project
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1421968/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1441300] Re: keystone-manage man page updates
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1441300 Title: keystone-manage man page updates Status in OpenStack Identity (Keystone): Fix Released Status in Keystone kilo series: Fix Released Bug description: The keystone-manage man page doesn't show any of the new fernet commands, so it's out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1441300/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1444748] Re: Remove unused policy rule for trust
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1444748 Title: Remove unused policy rule for trust Status in OpenStack Identity (Keystone): Fix Released Bug description: There are couple of policy rule that are unused for trust, even if the user updates the rule it won't impact the policy check. we should clean this up to avoid confusion. This is step #1 as for fixing the policy rule for trust. See : https://bugs.launchpad.net/keystone/+bug/1280084 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1444748/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440958] Re: loosen validation on matching trusted dashboard
** 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/1440958
Title:
loosen validation on matching trusted dashboard
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
In the current implementation for verifying where the SSO request came
from, the host is grabbed from the 'origin' query parameter, and
compared to the list of 'trusted_dashboards' in the config file.
origin = context['query_string'].get('origin')
host = urllib.parse.unquote_plus(origin)
if host in CONF.federation.trusted_dashboard:
...
https://github.com/openstack/keystone/blob/master/keystone/contrib/federation/controllers.py#L278-L287
This works, but unless the entry is marked perfectly in the config
file, it won't match. We should loosen the validation that is
performed, and maybe even use the HTTP Referer instead (and no longer
require the 'origin' parameter from horizon).
We should be able to decompose the Refer to figure out the scheme +
hostname + path, and use that hostname to check against the trusted
dashboards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1440958/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1467791] Re: Specific ipv4 subnet to create port and return port contains ipv4 and ipv6 address
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-
ipv6-prefixes.html#proposed-change is where this behavior is documented.
** Changed in: neutron
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/1467791
Title:
Specific ipv4 subnet to create port and return port contains ipv4 and
ipv6 address
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
neutron --version
2.6.0
When a network named 'A' contains a ipv4 subnet and a ipv6 subnet with
ipv6_address_mode and ipv6_ra_mode are 'slaac'/'dhcpv6-stateless'. I
specify the ipv4 subnet without ipv4 addr to create a port based on
this network 'A'. The returned port contains 2 addresses (both ipv4
and ipv6).
It just like:
| fixed_ips | {subnet_id:
990f3f53-ee5b-4a6f-b362-34fc339ab6e5, ip_address: 10.0.0.5}
| | {subnet_id:
59464306-6781-4d33-b10c-214f4ba30e6c, ip_address: fd00:dd95:d03f:0:f81
But the result which expected is just :
| fixed_ips | {subnet_id:
990f3f53-ee5b-4a6f-b362-34fc339ab6e5, ip_address: 10.0.0.5}
repo:
1.create a network
2.create a ipv4 subnet and a ipv6 subnet into this network.And specify
ipv6_address_mode and ipv6_ra_mode are 'slaac'/'dhcpv6-stateless'.
3.run the command
neutron port-create --fixed-ip subnet_id=$[ipv4_subnet_id]
$[network_id/name]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1467791/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1468059] [NEW] Extend default setenv instead of replacing it in tox.ini
Public bug reported: Some tox jobs[1] define their own setenv without extending/referencing default setenv, it disallows to define environment variables shared by all jobs. [1] (dsvm-)functional/fullstack ** Affects: neutron Importance: Undecided Status: New ** Description changed: Some tox jobs[1] define their own setenv without extending/referencing default setenv, it disallows to define environment variables shared by all jobs. + + [1] (dsvm-)functional/fullstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1468059 Title: Extend default setenv instead of replacing it in tox.ini Status in OpenStack Neutron (virtual network service): New Bug description: Some tox jobs[1] define their own setenv without extending/referencing default setenv, it disallows to define environment variables shared by all jobs. [1] (dsvm-)functional/fullstack To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1468059/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1462355] Re: wrong title in v3 OS-INHERIT Extension spec
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1462355
Title:
wrong title in v3 OS-INHERIT Extension spec
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
The title of API [1] is wrong:
Revoke an inherited project role from group on domain
DELETE
/OS-INHERIT/projects/{project_id)/groups/{group_id}/roles/{role_id}/inherited_to_projects
It should be Revoke an inherited project role from group on project.
[1]: http://specs.openstack.org/openstack/keystone-specs/api/v3
/identity-api-v3-os-inherit-ext.html#revoke-an-inherited-project-role-
from-group-on-domain
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1462355/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1466957] Re: keystone configuration docs missing some keystone-manage commands
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1466957 Title: keystone configuration docs missing some keystone-manage commands Status in OpenStack Identity (Keystone): Fix Released Bug description: The keystone configuration docs are missing info on all of the keystone-manage commands. See http://docs.openstack.org/developer/keystone/configuration.html #initializing-keystone Missing are: domain_config_upload fernet_rotate fernet_setup However, the man page for keystone-manage does contain info. ? domain_config_upload: Upload domain configuration file. ? fernet_rotate: Rotate keys in the Fernet key repository. ? fernet_setup: Setup a Fernet key repository. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1466957/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1459816] Re: update sample_data script to use openstack commands
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1459816 Title: update sample_data script to use openstack commands Status in OpenStack Identity (Keystone): Fix Released Bug description: The sample data script is genterating warnings since the keystone commands are depricated. The script needs to be updated to use the new openstack commands. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1459816/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1459279] Re: Wrong assertion examples in doc
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1459279 Title: Wrong assertion examples in doc Status in OpenStack Identity (Keystone): Fix Released Bug description: The pure SAML assertion example in [1] is not a valid assertion generated by keystone and the ECP wrapped one is missing the two new attributes openstack_user_domain and openstack_project_domain. [1] https://github.com/openstack/keystone-specs/blob/master/api/v3 /identity-api-v3-os-federation-ext.rst#generating-assertions To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1459279/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1459683] Re: Config federation docs still references SP as regions
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1459683 Title: Config federation docs still references SP as regions Status in OpenStack Identity (Keystone): Fix Released Bug description: In the session [1], SPs are still referenced as regions. [1] https://github.com/openstack/keystone/blob/master/doc/source/configure_federation.rst #testing-it-all-out To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1459683/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461251] Re: Stop using deprecated oslo_utils.timeutils.isotime
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1461251 Title: Stop using deprecated oslo_utils.timeutils.isotime Status in OpenStack Identity (Keystone): Fix Released Status in Oslo utility library: New Status in Python client library for Keystone: In Progress Bug description: oslo_utils.timeutils.isotime() is deprecated as of 1.6 so we need to stop using it. This breaks unit tests in keystone since we've got a check for calling deprecated functions. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1461251/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1464366] Re: unit tests fail based on wall clock time
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1464366 Title: unit tests fail based on wall clock time Status in OpenStack Identity (Keystone): Fix Released Bug description: We've got a lot of tests that depend on how long the test takes to run. Tests can take a long time just because you have a slow or overloaded system, or maybe you're trying to step through it with the debugger. The tests that fail generally don't care about the time and aren't attempting to verify performance, but still require that the test run quickly enough. Tests shouldn't depend on the wall clock time, just like they shouldn't depend on any external factors. Here's an example of a failing test: keystone.tests.unit.test_auth.AuthWithRemoteUser.test_scoped_remote_authn - Captured traceback: ~~~ Traceback (most recent call last): File keystone/tests/unit/test_auth.py, line 741, in test_scoped_remote_authn enforce_audit_ids=False) File keystone/tests/unit/test_auth.py, line 104, in assertEqualTokens timeutils.parse_isotime(b['access']['token']['expires'])) File keystone/tests/unit/core.py, line 521, in assertCloseEnoughForGovernmentWork self.assertTrue(abs(a - b).seconds = delta, msg) File /home/jenkins/workspace/keystone/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py, line 678, in assertTrue raise self.failureException(msg) AssertionError: False is not true : 2015-06-11 13:34:46+00:00 != 2015-06-11 13:34:50+00:00 within 3 delta It took 4 seconds rather than 3. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1464366/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461031] Re: Federation docs say domain is identified by name not id
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1461031 Title: Federation docs say domain is identified by name not id Status in OpenStack Identity (Keystone): Fix Released Bug description: In [0] in the token example we can see that service domain is identified by 'name', whereas [1] sets 'id' field. Docs should reflect code. [0] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-federation-ext.html#authenticating [1] https://github.com/openstack/keystone/blob/master/keystone/contrib/federation/utils.py#L529-L533 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1461031/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1465444] Re: Fernet key rotation removing keys early
** 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/1465444 Title: Fernet key rotation removing keys early Status in OpenStack Identity (Keystone): Fix Released Bug description: When setting up Fernet key rotation with a maximum number of active of keys set to 25, it turned out that 'keystone-manage fernet_rotate' started deleting two keys once there reached 13 existing keys. It would waver between 12 and 13 keys every time it was rotated. It looks like this might be related to the range of keys to remove being negative : excess_keys = ( keys[:len(key_files) - CONF.fernet_tokens.max_active_keys + 1]) .. ends up being excess_keys = ( keys[:-11] ) .. which seems to be dipping back into the range of keys that should still be good and removing those. Adding something like: if len(key_files) - CONF.fernet_tokens.max_active_keys + 1 = 0 for the purge excess keys section seemed to allow us to generate all 25 keys, then rotate as normal. Once we hit the full 25 keys, this additional line was no longer needed. Attaching some log information showing the available keys going from 12, 13, 12, 13. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1465444/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1460839] Re: bandit: blacklist_functions not a valid plugin
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1460839
Title:
bandit: blacklist_functions not a valid plugin
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
Keystone currently has the keystone_conservative profile in
bandit.yaml defined as follows:
keystone_conservative:
include:
- blacklist_functions
- blacklist_imports
- request_with_no_cert_validation
- exec_used
- set_bad_file_permissions
- subprocess_popen_with_shell_equals_true
- linux_commands_wildcard_injection
- ssl_with_bad_version
The keystone_conservative profile is the default profile run when
using bandit in the keystone project. The problem is that
blacklist_functions is not actually a bandit plugin. There is a
plugin called blacklist_calls, but not blacklist_functions.
To recreate:
- Edit bandit.yaml, comment out - '/tests/' in the exclude_dirs
- Run 'tox -e bandit'
- Notice you get no errors
- Edit bandit.yaml again, search/replace blacklist_functions to
blacklist_calls
- Rerun 'tox -e bandit'
- Notice you get an error now:
Issue: Use of possibly insecure function - consider using safer
ast.literal_eval.
Severity: Medium Confidence: High
Location: keystone/tests/unit/test_wsgi.py:104
103 resp = req.get_response(app)
104 self.assertIn('X-Foo', eval(resp.body))
105
So basically, the blacklist_calls are never checked.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1460839/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1459532] Re: api_curl_examples.rst is out of date
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1459532 Title: api_curl_examples.rst is out of date Status in OpenStack Identity (Keystone): Fix Released Bug description: Two example in the `api_curl_examples.rst` is not accurate anymore, we need to update the docs. 1. Default scope - Get an token with default scope (may be unscoped) Since this example is trying to get an unscoped token, so there will be no catalog associated with the token, so the response is not correct. 2. Getting a token from a token The example here is also trying to get a unscoped token from a existing token, so there will no catalog associated with the token, so the response is not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1459532/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1456441] Re: keystone wsgi does not read files in /etc/keystone/*
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1456441 Title: keystone wsgi does not read files in /etc/keystone/* Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): Invalid Bug description: Keystone launched through wsgi was not picking up the connection string in /etc/keystone/keystone.conf. Manual run of keystone-all identified that there was a collision with /usr/share/keystone /keystone-dist.conf which contains an entry for connection in [database]. Commented out the line in keystone-dist.conf and restarted apache. Correct connection string was then picked up from /etc/keystone/keystone.conf. CentOS 7 minimal install Followed install guide for Kilo. Encountered error Access denied keystone@localhost at step of creating openstack service identity because the wrong credentials from the .conf conflict were being passed to mariadb. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1456441/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461299] Re: Failure on list users when using ldap domain configuration from database
** Project changed: keystone = oslo.config -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1461299 Title: Failure on list users when using ldap domain configuration from database Status in Oslo configuration management library: New Bug description: When having a setup with domain_specific_drivers_enabled set to true, and a domain configured with ldap backend and configurations stored in the database : the keystone user list API fails with the following error: openstack user list --domain domainX ERROR: openstack An unexpected error prevented the server from fulfilling your request: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. (Disable debug mode to suppress these details.) (HTTP 500) To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.config/+bug/1461299/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1456755] Re: Could not retrieve gateway port for subnet
*** This bug is a duplicate of bug 1404823 ***
https://bugs.launchpad.net/bugs/1404823
** This bug is no longer a duplicate of bug 1456756
Could not retrieve gateway port for subnet
** This bug has been marked a duplicate of bug 1404823
router-interface-add port succeed but does not add corresponding flows
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1456755
Title:
Could not retrieve gateway port for subnet
Status in OpenStack Neutron (virtual network service):
New
Bug description:
There is this trace at error level in the server logs when DVR is
enabled by default:
[req-179a109e-456a-4743-8395-58b2f322afe2 None None] Could not
retrieve gateway port for subnet {'ipv6_ra_mode': None,
'allocation_pools': [{'start': u'10.100.0.2', 'end': u'10.100.0.14'}],
'host_routes': [], 'ipv6_address_mode': None, 'cidr':
u'10.100.0.0/28', 'id': u'8a47789b-452d-4ac7-a85b-9e57838456f0',
'subnetpool_id': None, 'name': u'', 'enable_dhcp': True, 'network_id':
u'85389a7f-8f50-405c-a19c-c4ad7b35e9ff', 'tenant_id':
u'ec2ad8998456415ea6e8f9a217b5c1d8', 'dns_nameservers': [],
'gateway_ip': u'10.100.0.1', 'ip_version': 4L, 'shared': False}
This is the logstash query:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQ291bGQgbm90IHJldHJpZXZlIGdhdGV3YXkgcG9ydCBmb3Igc3VibmV0XCIgQU5EIGJ1aWxkX25hbWU6XCJjaGVjay10ZW1wZXN0LWRzdm0tbmV1dHJvbi1kdnJcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQzMjA2MDU2NzU0MSwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1456755/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1468087] [NEW] py27 job failing on test_save_objectfield_missing_instance_row
Public bug reported: http://logs.openstack.org/28/145528/22/check/gate-nova- python27/a818283/console.html 2015-06-23 14:13:01.268 | == 2015-06-23 14:13:01.268 | Failed 1 tests - output below: 2015-06-23 14:13:01.268 | == 2015-06-23 14:13:01.269 | 2015-06-23 14:13:01.269 | nova.tests.unit.objects.test_instance.TestRemoteInstanceObject.test_save_objectfield_missing_instance_row 2015-06-23 14:13:01.269 | - 2015-06-23 14:13:01.269 | 2015-06-23 14:13:01.269 | Captured traceback: 2015-06-23 14:13:01.269 | ~~~ 2015-06-23 14:13:01.269 | Traceback (most recent call last): 2015-06-23 14:13:01.269 | File nova/tests/unit/objects/test_instance.py, line 499, in test_save_objectfield_missing_instance_row 2015-06-23 14:13:01.269 | _test() 2015-06-23 14:13:01.269 | File /home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/mock.py, line 1201, in patched 2015-06-23 14:13:01.270 | return func(*args, **keywargs) 2015-06-23 14:13:01.270 | File nova/tests/unit/objects/test_instance.py, line 498, in _test 2015-06-23 14:13:01.270 | instance.save) 2015-06-23 14:13:01.270 | File /home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py, line 422, in assertRaises 2015-06-23 14:13:01.270 | self.assertThat(our_callable, matcher) 2015-06-23 14:13:01.270 | File /home/jenkins/workspace/gate-nova-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py, line 435, in assertThat 2015-06-23 14:13:01.270 | raise mismatch_error 2015-06-23 14:13:01.270 | testtools.matchers._impl.MismatchError: bound method Instance.save of Instance(access_ip_v4=None,access_ip_v6=None,architecture=None,auto_disk_config=False,availability_zone=None,cell_name=None,cleaned=False,config_drive=None,created_at=1955-11-05T00:00:00Z,default_ephemeral_device=None,default_swap_device=None,deleted=False,deleted_at=None,disable_terminate=False,display_description=None,display_name=None,ec2_ids=?,ephemeral_gb=0,ephemeral_key_uuid=None,fault=?,flavor=Flavor(1),host='fake-host',hostname=None,id=1,image_ref=None,info_cache=?,instance_type_id=None,kernel_id=None,key_data=None,key_name=None,launch_index=None,launched_at=None,launched_on=None,locked=False,locked_by=None,memory_mb=None,metadata=?,new_flavor=None,node=None,numa_topology=?,old_flavor=None,os_type=None,pci_devices=?,pci_requests=?,power_state=None,progress=None,project_id='fake-project',ramdisk_id=None,reservation_id=None,root_device_name=None,root_gb=0,scheduled _at=None,security_groups=?,shutdown_terminate=False,system_metadata=?,tags=?,task_state=None,terminated_at=None,updated_at=None,user_data=None,user_id='fake-user',uuid=b0d1668f-f941-4124-8c22-b60c42b54655,vcpu_model=?,vcpus=None,vm_mode=None,vm_state=None) returned None 2015-06-23 14:13:01.270 | Seen repetitively over the last 24 hours : http://logstash.openstack.org/#eyJzZWFyY2giOiJidWlsZF9uYW1lOlwiZ2F0ZS1ub3ZhLXB5dGhvbjI3XCIgQU5EIG1lc3NhZ2U6XCJ0ZXN0dG9vbHMubWF0Y2hlcnMuX2ltcGwuTWlzbWF0Y2hFcnJvcjogJmx0O2JvdW5kIG1ldGhvZCBJbnN0YW5jZS5zYXZlIG9mIEluc3RhbmNlXCIgQU5EIG1lc3NhZ2U6XCJyZXR1cm5lZCBOb25lXCIgQU5EIHRhZ3M6XCJjb25zb2xlXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzUwODg0NTk1NzUsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= ** Affects: nova Importance: High Status: Confirmed ** Tags: testing -- 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/1468087 Title: py27 job failing on test_save_objectfield_missing_instance_row Status in OpenStack Compute (Nova): Confirmed Bug description: http://logs.openstack.org/28/145528/22/check/gate-nova- python27/a818283/console.html 2015-06-23 14:13:01.268 | == 2015-06-23 14:13:01.268 | Failed 1 tests - output below: 2015-06-23 14:13:01.268 | == 2015-06-23 14:13:01.269 | 2015-06-23 14:13:01.269 | nova.tests.unit.objects.test_instance.TestRemoteInstanceObject.test_save_objectfield_missing_instance_row 2015-06-23 14:13:01.269 | - 2015-06-23 14:13:01.269 | 2015-06-23 14:13:01.269 | Captured traceback: 2015-06-23 14:13:01.269 | ~~~ 2015-06-23 14:13:01.269 | Traceback (most recent call last): 2015-06-23 14:13:01.269 | File nova/tests/unit/objects/test_instance.py, line 499, in test_save_objectfield_missing_instance_row 2015-06-23 14:13:01.269 | _test() 2015-06-23 14:13:01.269 | File
[Yahoo-eng-team] [Bug 1442787] Re: Mapping openstack_user attribute in k2k assertions with different domains
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1442787 Title: Mapping openstack_user attribute in k2k assertions with different domains Status in OpenStack Identity (Keystone): Fix Released Bug description: We can have two users with the same username in different domains. So if we have a User A in Domain X and a User A in Domain Y, there is no way to differ what User A is being used in a SAML assertion generated by this IdP (we have only the openstack_user attribute in the SAML assertion). To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1442787/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1443721] Re: Make checking of Trust existence more DRY
** 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/1443721 Title: Make checking of Trust existence more DRY Status in OpenStack Identity (Keystone): Fix Released Bug description: The code for checking if Trust exists is duplicated all over the controller: if not trust: raise exception.TrustNotFound(trust_id=trust_id) https://github.com/openstack/keystone/blob/master/keystone/trust/controllers.py#L77-L78 to make it more DRY, remove the check in controller and move it the driver To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1443721/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445183] Re: Expose domain_name in the context for policy.json
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1445183 Title: Expose domain_name in the context for policy.json Status in OpenStack Identity (Keystone): Fix Released Bug description: The setup for cloud_admin in the policy file required knowing the uuid of the cloud admin domain ahead of time. This would required additional handling for deployers, and adding complexity for deploment. Exposing the domain_name in the context would make it easier for the deployer to setup the cloud admin policy. Instead of defining the policy for cloud admin as: cloud_admin: rule:admin_required and domain_id:admin_domain_id, The deployer have the flexibility to define the policy as: cloud_admin: rule:admin_required and domain_name:admin_domain_name, To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1445183/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1423973] Re: Use choices from oslo_config
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1423973 Title: Use choices from oslo_config Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Identity (Keystone) Middleware: In Progress Status in OpenStack Compute (Nova): Fix Committed Bug description: Support went into oslo_config recently that will allow us to use the choices keyword argument from argparse [1]. We should look at leveraging this in Keystone. [1] https://github.com/openstack/oslo.config/blame/578f9f4e60f58c210a9e1cb455925b9f310fe10e/oslo_config/cfg.py#L932 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1423973/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1387605] Re: Implement validation on Identity V3 API
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1387605 Title: Implement validation on Identity V3 API Status in OpenStack Identity (Keystone): Fix Released Bug description: Now, all of the keystone objects except for user and group use jsonschema to check parameters when creating or updating. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1387605/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1455344] Re: the deprecated compute_port option need to be removed
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1455344 Title: the deprecated compute_port option need to be removed Status in OpenStack Identity (Keystone): Fix Released Bug description: the compute_port option has been marked deprecated and should be remove in Liberty. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1455344/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1454968] Re: hard to understand the uri printed in the log
** 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/1454968
Title:
hard to understand the uri printed in the log
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
In keystone's log file, we can easily find some uri printed like this:
http://127.0.0.1:35357/v3/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens/auth/tokens
seems there is something wrong when we are trying to log the uri in the log
file.
LOG.info('%(req_method)s %(uri)s', {
'req_method': req.environ['REQUEST_METHOD'].upper(),
'uri': wsgiref.util.request_uri(req.environ),
})
code is here:
https://github.com/openstack/keystone/blob/0debc2fbf448b44574da6f3fef7d457037c59072/keystone/common/wsgi.py#L232
but seems it has already been wrong when the req is passed in.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1454968/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1454309] Re: Keystone v3 user/tenant lookup by name via OpenStack CLI client fails
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1454309
Title:
Keystone v3 user/tenant lookup by name via OpenStack CLI client fails
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When using the openstack CLI client to look up users/tenants by name
(e.g., openstack user show admin or openstack openstack project show
AdminTenant), it fails with a 500 and the following traceback:
2015-05-12 09:27:22.483530 2015-05-12 09:27:22.483 31012 DEBUG
keystone.common.ldap.core [-] LDAP search: base=ou=People,dc=local,dc=lan
scope=2 filterstr=((None(sn=admin))(objectClass=inetOrgPerson)) attrs=['cn',
'userPassword', 'enabled', 'sn', 'mail'] attrsonly=0 search_s
/usr/lib/python2.7/dist-packages/keystone/common/ldap/core.py:931
2015-05-12 09:27:22.483677 2015-05-12 09:27:22.483 31012 DEBUG
keystone.common.ldap.core [-] LDAP unbind unbind_s
/usr/lib/python2.7/dist-packages/keystone/common/ldap/core.py:904
2015-05-12 09:27:22.485831 2015-05-12 09:27:22.483 31012 ERROR
keystone.common.wsgi [-] {'desc': 'Bad search filter'}
2015-05-12 09:27:22.485874 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi Traceback (most recent call last):
2015-05-12 09:27:22.485881 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py, line 239, in
__call__
2015-05-12 09:27:22.485885 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi result = method(context, **params)
2015-05-12 09:27:22.485897 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/common/controller.py, line 202, in
wrapper
2015-05-12 09:27:22.485901 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi return f(self, context, filters, **kwargs)
2015-05-12 09:27:22.485904 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py, line 223,
in list_users
2015-05-12 09:27:22.485908 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi hints=hints)
2015-05-12 09:27:22.485911 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/common/manager.py, line 52, in
wrapper
2015-05-12 09:27:22.485915 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi return f(self, *args, **kwargs)
2015-05-12 09:27:22.485919 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/identity/core.py, line 342, in
wrapper
2015-05-12 09:27:22.485922 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi return f(self, *args, **kwargs)
2015-05-12 09:27:22.485926 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/identity/core.py, line 353, in
wrapper
2015-05-12 09:27:22.485930 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi return f(self, *args, **kwargs)
2015-05-12 09:27:22.485933 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/identity/core.py, line 791, in
list_users
2015-05-12 09:27:22.485937 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi ref_list = driver.list_users(hints)
2015-05-12 09:27:22.485941 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap.py, line 82,
in list_users
2015-05-12 09:27:22.485944 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi return self.user.get_all_filtered(hints)
2015-05-12 09:27:22.485948 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/identity/backends/ldap.py, line
269, in get_all_filtered
2015-05-12 09:27:22.485951 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi return [self.filter_attributes(user) for user in
self.get_all(query)]
2015-05-12 09:27:22.485964 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/common/ldap/core.py, line 1863, in
get_all
2015-05-12 09:27:22.485968 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi for x in self._ldap_get_all(ldap_filter)
2015-05-12 09:27:22.485972 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/common/ldap/core.py, line 1467, in
_ldap_get_all
2015-05-12 09:27:22.485975 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi attrs)
2015-05-12 09:27:22.485979 2015-05-12 09:27:22.483 31012 TRACE
keystone.common.wsgi File
/usr/lib/python2.7/dist-packages/keystone/common/ldap/core.py, line 944, in
[Yahoo-eng-team] [Bug 1448991] Re: Introduction to target.token.* is needed in the RBAC part of configuration.rst
** Changed in: keystone Status: Fix Committed = Fix Released ** Changed in: keystone Milestone: None = liberty-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1448991 Title: Introduction to target.token.* is needed in the RBAC part of configuration.rst Status in OpenStack Identity (Keystone): Fix Released Bug description: When limiting access to token-related operations, we may need references like %(target.token.user.domain.id)s. However possible values of target.token.* is missing while target.user.*, target.role.* and so on are listed in configuration.rst: http://docs.openstack.org/developer/keystone/configuration.html #keystone-api-protection-with-role-based-access-control-rbac I think this work will supplement keystone's current documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1448991/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448286] Re: unicode query string raises UnicodeEncodeError
** 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/1448286 Title: unicode query string raises UnicodeEncodeError Status in OpenStack Identity (Keystone): Fix Released Bug description: The logging in keystone.common.wsgi is unable to handle unicode query strings. The simplest example would be: $ curl http://localhost:35357/?Ϡ This will fail with a backtrace similar to: 2015-04-24 19:57:45.860 22255 TRACE keystone.common.wsgi File .../keystone/keystone/common/wsgi.py, line 234, in __call__ 2015-04-24 19:57:45.860 22255 TRACE keystone.common.wsgi 'params': urllib.urlencode(req.params)}) 2015-04-24 19:57:45.860 22255 TRACE keystone.common.wsgi File /usr/lib/python2.7/urllib.py, line 1311, in urlencode 2015-04-24 19:57:45.860 22255 TRACE keystone.common.wsgi k = quote_plus(str(k)) 2015-04-24 19:57:45.860 22255 TRACE keystone.common.wsgi UnicodeEncodeError: 'ascii' codec can't encode character u'\u03e0' in position 0: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1448286/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
