[Yahoo-eng-team] [Bug 1730756] [NEW] Creating a VM with a non-ASCII name fails with an Unicode error
Public bug reported: Creating a VM with a non-ASCII name in nova with the libvirt driver fails with an UnicodeEncodeError error. Instance failed to spawn: UnicodeEncodeError: 'ascii' codec can't encode character u'\u266b' in position 294: ord Traceback (most recent call last): File "/opt/stack/nova/nova/compute/manager.py", line 2208, in _build_resources yield resources File "/opt/stack/nova/nova/compute/manager.py", line 2001, in _build_and_run_instance block_device_info=block_device_info) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2821, in spawn destroy_disks_on_failure=True) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5289, in _create_domain_and_network destroy_disks_on_failure) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ self.force_reraise() File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise six.reraise(self.type_, self.value, self.tb) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5259, in _create_domain_and_network post_xml_callback=post_xml_callback) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5170, in _create_domain guest = libvirt_guest.Guest.create(xml, self._host) File "/opt/stack/nova/nova/virt/libvirt/guest.py", line 129, in create encodeutils.safe_decode(xml)) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ self.force_reraise() File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise six.reraise(self.type_, self.value, self.tb) File "/opt/stack/nova/nova/virt/libvirt/guest.py", line 125, in create guest = host.write_instance_config(xml) File "/opt/stack/nova/nova/virt/libvirt/host.py", line 826, in write_instance_config domain = self.get_connection().defineXML(xml) File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 186, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 144, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 125, in execute six.reraise(c, e, tb) File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3817, in defineXML ret = libvirtmod.virDomainDefineXML(self._o, xml) UnicodeEncodeError: 'ascii' codec can't encode character u'\u266b' in position 294: ordinal not in range(128) ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1730756 Title: Creating a VM with a non-ASCII name fails with an Unicode error Status in OpenStack Compute (nova): New Bug description: Creating a VM with a non-ASCII name in nova with the libvirt driver fails with an UnicodeEncodeError error. Instance failed to spawn: UnicodeEncodeError: 'ascii' codec can't encode character u'\u266b' in position 294: ord Traceback (most recent call last): File "/opt/stack/nova/nova/compute/manager.py", line 2208, in _build_resources yield resources File "/opt/stack/nova/nova/compute/manager.py", line 2001, in _build_and_run_instance block_device_info=block_device_info) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2821, in spawn destroy_disks_on_failure=True) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5289, in _create_domain_and_network destroy_disks_on_failure) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ self.force_reraise() File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise six.reraise(self.type_, self.value, self.tb) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5259, in _create_domain_and_network post_xml_callback=post_xml_callback) File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 5170, in _create_domain guest = libvirt_guest.Guest.create(xml, self._host) File "/opt/stack/nova/nova/virt/libvirt/guest.py", line 129, in create encodeutils.safe_decode(xml)) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ self.force_reraise() File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise six.reraise(self.type_, self.value, self.tb) File "/opt/stack/nova/nova/virt/libvirt/guest.py", line 125, in create guest = host.write_instance_config(xml) File "/opt/stack/nova/nova/virt/libvirt/host.py", line 826, in write_instance_config domain = self.get_connection().defineXML(xml) File "/usr/lib/python2.7/site-packages/eventl
[Yahoo-eng-team] [Bug 1572592] [NEW] gate-neutron-lbaasv1-dsvm-api gate broken on Neutron LBaaS: fail to find a quota
Public bug reported:
The gate-neutron-lbaasv1-dsvm-api gate job of Neutron LBaaS looks to
always fail on test_quotas. Example of a failure.
For example, the gate failed on the approve "Updated from global
requirements" change: https://review.openstack.org/#/c/307761/
Console logs: http://logs.openstack.org/61/307761/1/check/gate-neutron-
lbaasv1-dsvm-api/69872dd/console.html
neutron_lbaas.tests.tempest.v1.api.admin.test_quotas.QuotasTest.test_lbaas_quotas[gate]
---
Traceback (most recent call last):
File
"neutron_lbaas/tests/tempest/lib/services/network/json/network_client.py", line
330, in reset_quotas
resp, body = self.delete(uri)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 290, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 642, in request
resp, resp_body)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 695, in _error_checker
raise exceptions.NotFound(resp_body, resp=resp)
tempest.lib.exceptions.NotFound: Object not found
Details: {u'message': u'Quota for tenant ce7b2ca707c6479f88b67e312d3764f2 could
not be found.', u'detail': u'', u'type': u'TenantQuotaNotFound'}
neutron_lbaas.tests.tempest.v1.api.admin.test_quotas.QuotasTest.test_quotas[gate]
-
Traceback (most recent call last):
File
"neutron_lbaas/tests/tempest/lib/services/network/json/network_client.py", line
330, in reset_quotas
resp, body = self.delete(uri)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 290, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 642, in request
resp, resp_body)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 695, in _error_checker
raise exceptions.NotFound(resp_body, resp=resp)
tempest.lib.exceptions.NotFound: Object not found
Details: {u'message': u'Quota for tenant 89128f4ca5aa415db790b0ed30d8b24e could
not be found.', u'detail': u'', u'type': u'TenantQuotaNotFound'}
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1572592
Title:
gate-neutron-lbaasv1-dsvm-api gate broken on Neutron LBaaS: fail to
find a quota
Status in neutron:
New
Bug description:
The gate-neutron-lbaasv1-dsvm-api gate job of Neutron LBaaS looks to
always fail on test_quotas. Example of a failure.
For example, the gate failed on the approve "Updated from global
requirements" change: https://review.openstack.org/#/c/307761/
Console logs: http://logs.openstack.org/61/307761/1/check/gate-
neutron-lbaasv1-dsvm-api/69872dd/console.html
neutron_lbaas.tests.tempest.v1.api.admin.test_quotas.QuotasTest.test_lbaas_quotas[gate]
---
Traceback (most recent call last):
File
"neutron_lbaas/tests/tempest/lib/services/network/json/network_client.py", line
330, in reset_quotas
resp, body = self.delete(uri)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 290, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 642, in request
resp, resp_body)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 695, in _error_checker
raise exceptions.NotFound(resp_body, resp=resp)
tempest.lib.exceptions.NotFound: Object not found
Details: {u'message': u'Quota for tenant ce7b2ca707c6479f88b67e312d3764f2
could not be found.', u'detail': u'', u'type': u'TenantQuotaNotFound'}
neutron_lbaas.tests.tempest.v1.api.admin.test_quotas.QuotasTest.test_quotas[gate]
-
Traceback (most recent call last):
File
"neutron_lbaas/tests/tempest/lib/services/network/json/network_client.py", line
330, in reset_quotas
resp, body = self.delete(uri)
File
"/opt/stack/new/neutron-lbaas/.tox/apiv1/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
line 290,
[Yahoo-eng-team] [Bug 1543073] [NEW] keystoneclient API misused in MappingsViewTests
Public bug reported: The test openstack_dashboard.dashboards.identity.mappings.tests.MappingsViewTests.test_index() uses a keystoneclient.v3.contrib.federation.mappings.Mapping object created by the data() function of openstack_dashboard/test/test_data/keystone_data.py. Problem: data() pass the keystoneclient.v3.contrib.federation.mappings.MappingManager *class* to Mapping constructor, whereas it should pass an instance. keystoneclient.v3.contrib.federation.mappings.MappingManager constructor (keystoneclient.base.Manager constructor) has a client parameter but I don't know how to create such client: "instance of BaseClient descendant for HTTP requests". The bug is hidden on Python 2 in horizon.tables.base.DataTable.get_object_display() by hasattr(datum, 'name'), because hasattr() ignores *all* exceptions. I found this bug when running the test on Python 3, since hasattr() now only catchs AttributeError. I proposed https://review.openstack.org/#/c/275265/ to mimick hasattr() Python 2 beheaviour on Python 3 in horizon.tables.base.DataTable.get_object_display(). ** 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/1543073 Title: keystoneclient API misused in MappingsViewTests Status in OpenStack Dashboard (Horizon): New Bug description: The test openstack_dashboard.dashboards.identity.mappings.tests.MappingsViewTests.test_index() uses a keystoneclient.v3.contrib.federation.mappings.Mapping object created by the data() function of openstack_dashboard/test/test_data/keystone_data.py. Problem: data() pass the keystoneclient.v3.contrib.federation.mappings.MappingManager *class* to Mapping constructor, whereas it should pass an instance. keystoneclient.v3.contrib.federation.mappings.MappingManager constructor (keystoneclient.base.Manager constructor) has a client parameter but I don't know how to create such client: "instance of BaseClient descendant for HTTP requests". The bug is hidden on Python 2 in horizon.tables.base.DataTable.get_object_display() by hasattr(datum, 'name'), because hasattr() ignores *all* exceptions. I found this bug when running the test on Python 3, since hasattr() now only catchs AttributeError. I proposed https://review.openstack.org/#/c/275265/ to mimick hasattr() Python 2 beheaviour on Python 3 in horizon.tables.base.DataTable.get_object_display(). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1543073/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1541487] [NEW] glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api hangs when run with testtools
Public bug reported: When glance.tests.integration.v2.test_tasks_api is run directly with testtools, the test fails: "python -u -m testtools.run glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api" For an unknown reason, the test pass when run with testr: "testr run glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api" It looks like the _wait_on_task_execution() method of glance/tests/integration/v2/test_tasks_api.py is not reliable. The method uses time.sleep() to give time to the "server" to execute a task run in background. Problem: in practice, the "server" is in the same process than the client, eventlet is used to scheduled tasks of the server. time.sleep() really blocks the whole process, including the server which is supposed to run the task. Sorry, I'm unable to explain why the test pass with testr, eventlet, taskflow, etc. are too magic for my little brain :-) IMHO we must enable monkey-patch to run Glance unit and integration tests. Or at least, _wait_on_task_execution() must call eventlet.sleep(), not time.sleep(). Note: time.sleep() is not monkey-patched when the test is run with testtools or testr, the test runner doesn't change that. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1541487 Title: glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api hangs when run with testtools Status in Glance: New Bug description: When glance.tests.integration.v2.test_tasks_api is run directly with testtools, the test fails: "python -u -m testtools.run glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api" For an unknown reason, the test pass when run with testr: "testr run glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api" It looks like the _wait_on_task_execution() method of glance/tests/integration/v2/test_tasks_api.py is not reliable. The method uses time.sleep() to give time to the "server" to execute a task run in background. Problem: in practice, the "server" is in the same process than the client, eventlet is used to scheduled tasks of the server. time.sleep() really blocks the whole process, including the server which is supposed to run the task. Sorry, I'm unable to explain why the test pass with testr, eventlet, taskflow, etc. are too magic for my little brain :-) IMHO we must enable monkey-patch to run Glance unit and integration tests. Or at least, _wait_on_task_execution() must call eventlet.sleep(), not time.sleep(). Note: time.sleep() is not monkey-patched when the test is run with testtools or testr, the test runner doesn't change that. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1541487/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1473369] Re: new mock release broke a bunch of unit tests
** Also affects: swift Importance: Undecided Status: New ** Changed in: swift Assignee: (unassigned) => Victor Stinner (victor-stinner) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1473369 Title: new mock release broke a bunch of unit tests Status in Glance: In Progress Status in murano: Fix Committed Status in murano kilo series: Fix Committed Status in neutron: Fix Committed Status in python-muranoclient: In Progress Status in python-muranoclient kilo series: New Status in OpenStack Object Storage (swift): In Progress Bug description: http://lists.openstack.org/pipermail/openstack- dev/2015-July/069156.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1473369/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1471243] [NEW] Test on the xattr image cache fails because of noatime
Public bug reported: The check job gate-glance-python27 failed on my patch https://review.openstack.org/#/c/197916/ I added debug traces and it looks like the OpenStack infra uses a ext4 partition mounted with noatime, whereas the xattr image cache driver explicitly requires atime. Debug trace: http://logs.openstack.org/16/197916/6/check/gate-glance- python27/16760bf/testr_results.html.gz glance.tests.unit.test_image_cache.TestImageCacheXattr.test_caching_iterator_falloffend Traceback (most recent call last): File "glance/tests/unit/test_image_cache.py", line 411, in test_caching_iterator_falloffend self.assertFalse(os.path.exists(incomplete_file_path), debug_info) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py", line 696, in assertFalse raise self.failureException(msg) AssertionError: True is not false : /tmp/tmp.NOhmw2VXFN/tmpjnooYj Content of the image cache: /tmp/tmp.NOhmw2VXFN/tmpjnooYj/queue /tmp/tmp.NOhmw2VXFN/tmpjnooYj/incomplete /tmp/tmp.NOhmw2VXFN/tmpjnooYj/incomplete/1 /tmp/tmp.NOhmw2VXFN/tmpjnooYj/invalid Filesystem of the image cache (/tmp): Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvda1 41147472 11923388 27320644 31% / Filesystem mounted with: /dev/xvda1 on / type ext4 (rw,noatime,errors=remount-ro,barrier=0) Notice "noatime" in the mount options of /dev/xvda1. The test glance.tests.unit.test_image_cache.TestImageCacheXattr.test_caching_iterator_falloffend pass on my Fedora 22. On Fedora 22, the image cache is created on /tmp which mounted as tmpfs. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1471243 Title: Test on the xattr image cache fails because of noatime Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The check job gate-glance-python27 failed on my patch https://review.openstack.org/#/c/197916/ I added debug traces and it looks like the OpenStack infra uses a ext4 partition mounted with noatime, whereas the xattr image cache driver explicitly requires atime. Debug trace: http://logs.openstack.org/16/197916/6/check/gate-glance- python27/16760bf/testr_results.html.gz glance.tests.unit.test_image_cache.TestImageCacheXattr.test_caching_iterator_falloffend Traceback (most recent call last): File "glance/tests/unit/test_image_cache.py", line 411, in test_caching_iterator_falloffend self.assertFalse(os.path.exists(incomplete_file_path), debug_info) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py", line 696, in assertFalse raise self.failureException(msg) AssertionError: True is not false : /tmp/tmp.NOhmw2VXFN/tmpjnooYj Content of the image cache: /tmp/tmp.NOhmw2VXFN/tmpjnooYj/queue /tmp/tmp.NOhmw2VXFN/tmpjnooYj/incomplete /tmp/tmp.NOhmw2VXFN/tmpjnooYj/incomplete/1 /tmp/tmp.NOhmw2VXFN/tmpjnooYj/invalid Filesystem of the image cache (/tmp): Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvda1 41147472 11923388 27320644 31% / Filesystem mounted with: /dev/xvda1 on / type ext4 (rw,noatime,errors=remount-ro,barrier=0) Notice "noatime" in the mount options of /dev/xvda1. The test glance.tests.unit.test_image_cache.TestImageCacheXattr.test_caching_iterator_falloffend pass on my Fedora 22. On Fedora 22, the image cache is created on /tmp which mounted as tmpfs. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1471243/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1464298] [NEW] default hash function and hash format changed in OpenSSH 6.8 (ssh-keygen)
Public bug reported: The following tests fail on Fedora 22 because ssh-keygen output changed in OpenSSH 6.8: * nova.tests.unit.api.ec2.test_cloud.CloudTestCase.test_import_key_pair * nova.tests.unit.compute.test_keypairs.ImportKeypairTestCase.test_success_ssh Before OpenSSH used MD5 and hex with colons to display a fingerprint. It now uses SHA256 encoded to base64: """ * Add FingerprintHash option to ssh(1) and sshd(8), and equivalent command-line flags to the other tools to control algorithm used for key fingerprints. The default changes from MD5 to SHA256 and format from hex to base64. """ http://www.openssh.com/txt/release-6.8 ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1464298 Title: default hash function and hash format changed in OpenSSH 6.8 (ssh- keygen) Status in OpenStack Compute (Nova): New Bug description: The following tests fail on Fedora 22 because ssh-keygen output changed in OpenSSH 6.8: * nova.tests.unit.api.ec2.test_cloud.CloudTestCase.test_import_key_pair * nova.tests.unit.compute.test_keypairs.ImportKeypairTestCase.test_success_ssh Before OpenSSH used MD5 and hex with colons to display a fingerprint. It now uses SHA256 encoded to base64: """ * Add FingerprintHash option to ssh(1) and sshd(8), and equivalent command-line flags to the other tools to control algorithm used for key fingerprints. The default changes from MD5 to SHA256 and format from hex to base64. """ http://www.openssh.com/txt/release-6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1464298/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : 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] [NEW] issue with pbr 1.0 release
Public bug reported:
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.
** Affects: glance
Importance: Undecided
Status: New
--
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):
New
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 1456362] [NEW] flake8 requires pbr < 1.0 but nova installs pbr 1.0
Public bug reported:
The pep8 nova check was broken by the release of pbr 1.0:
http://lists.openstack.org/pipermail/openstack-dev/2015-May/064355.html
The check fails because nova requires "pbr>=0.11,<2.0", whereas flake8
requires "pbr!=0.7,<1.0,>=0.6".
flake8 should be updated to support pbr 1.0. Until that, I propose to
install pbr < 1.0 in nova to fix the pep8 check.
** Affects: nova
Importance: Undecided
Assignee: Victor Stinner (victor-stinner)
Status: 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/1456362
Title:
flake8 requires pbr < 1.0 but nova installs pbr 1.0
Status in OpenStack Compute (Nova):
In Progress
Bug description:
The pep8 nova check was broken by the release of pbr 1.0:
http://lists.openstack.org/pipermail/openstack-dev/2015-May/064355.html
The check fails because nova requires "pbr>=0.11,<2.0", whereas flake8
requires "pbr!=0.7,<1.0,>=0.6".
flake8 should be updated to support pbr 1.0. Until that, I propose to
install pbr < 1.0 in nova to fix the pep8 check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1456362/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1441083] [NEW] pkg_resources.DistributionNotFound: The 'argparse' distribution was not found and is required by oslo.config, python-keystoneclient, pysaml2
Public bug reported:
Hi,
When trying to install a fresh DevStack, I got issues with pip 6.1. First issue:
https://bugs.launchpad.net/tempest/+bug/1440984
I worked around the first issue, but then I got this issue:
2015-04-07 10:08:34.084 | + /usr/bin/keystone-manage db_sync
2015-04-07 10:08:34.239 | Traceback (most recent call last):
2015-04-07 10:08:34.239 | File "/usr/bin/keystone-manage", line 4, in
2015-04-07 10:08:34.239 |
__import__('pkg_resources').require('keystone==2015.1.dev143')
2015-04-07 10:08:34.239 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3057, in
2015-04-07 10:08:34.239 | working_set = WorkingSet._build_master()
2015-04-07 10:08:34.240 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 639, in
_build_master
2015-04-07 10:08:34.240 | ws.require(__requires__)
2015-04-07 10:08:34.240 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 940, in
require
2015-04-07 10:08:34.240 | needed =
self.resolve(parse_requirements(requirements))
2015-04-07 10:08:34.240 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 827, in
resolve
2015-04-07 10:08:34.240 | raise DistributionNotFound(req, requirers)
2015-04-07 10:08:34.241 | pkg_resources.DistributionNotFound: The 'argparse'
distribution was not found and is required by oslo.config,
python-keystoneclient, pysaml2
The problem is that newly released pip 6.1 doesn't want to install
argparse because argparse is part of the Python standard library:
fedora@myhost$ pip install argparse
Skipping requirement: argparse because argparse is a stdlib package
You must give at least one requirement to install (see "pip help install")
Workaround: downgrade pip to 6.0.8 and install argparse using pip (pip
install argparse).
A better fix is maybe to make argparse optional in keystone
requirements? It's now possible to add environment markers to
dependencies. Example:
futures; python_version < '2.7'
See https://github.com/pypa/pip/pull/1472
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1441083
Title:
pkg_resources.DistributionNotFound: The 'argparse' distribution was
not found and is required by oslo.config, python-keystoneclient,
pysaml2
Status in OpenStack Identity (Keystone):
New
Bug description:
Hi,
When trying to install a fresh DevStack, I got issues with pip 6.1. First
issue:
https://bugs.launchpad.net/tempest/+bug/1440984
I worked around the first issue, but then I got this issue:
2015-04-07 10:08:34.084 | + /usr/bin/keystone-manage db_sync
2015-04-07 10:08:34.239 | Traceback (most recent call last):
2015-04-07 10:08:34.239 | File "/usr/bin/keystone-manage", line 4, in
2015-04-07 10:08:34.239 |
__import__('pkg_resources').require('keystone==2015.1.dev143')
2015-04-07 10:08:34.239 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3057, in
2015-04-07 10:08:34.239 | working_set = WorkingSet._build_master()
2015-04-07 10:08:34.240 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 639, in
_build_master
2015-04-07 10:08:34.240 | ws.require(__requires__)
2015-04-07 10:08:34.240 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 940, in
require
2015-04-07 10:08:34.240 | needed =
self.resolve(parse_requirements(requirements))
2015-04-07 10:08:34.240 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 827, in
resolve
2015-04-07 10:08:34.240 | raise DistributionNotFound(req, requirers)
2015-04-07 10:08:34.241 | pkg_resources.DistributionNotFound: The 'argparse'
distribution was not found and is required by oslo.config,
python-keystoneclient, pysaml2
The problem is that newly released pip 6.1 doesn't want to install
argparse because argparse is part of the Python standard library:
fedora@myhost$ pip install argparse
Skipping requirement: argparse because argparse is a stdlib package
You must give at least one requirement to install (see "pip help install")
Workaround: downgrade pip to 6.0.8 and install argparse using pip (pip
install argparse).
A better fix is maybe to make argparse optional in keystone
requirements? It's now possible to add environment markers to
dependencies. Example:
futures; python_version < '2.7'
See https://github.com/pypa/pip/pull/1472
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1441083/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
