[Yahoo-eng-team] [Bug 1275654] [NEW] neutron.unit.services code duplication
Public bug reported: code duplication between neutron.unit.services.loadbalancer.test_loadbalancer_plugin and neutron.unit.services.vpn.test_vpnaas_extension ** 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/1275654 Title: neutron.unit.services code duplication Status in OpenStack Neutron (virtual network service): New Bug description: code duplication between neutron.unit.services.loadbalancer.test_loadbalancer_plugin and neutron.unit.services.vpn.test_vpnaas_extension To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1275654/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1026301] Re: image-list should be able to filter on deleted attribute
** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) = Richard Zsarnoczai (richard-zsarnoczai) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1026301 Title: image-list should be able to filter on deleted attribute Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Python client library for Glance: In Progress Bug description: In order to see deleted images, the glance client should be able to do: glance image-list --deleted=True|False|None To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1026301/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275675] [NEW] Version change in ObjectField does not work with back-levelling
Public bug reported: When a NovaObject primitive is deserialized the object version is checked and an IncompatibleObjectVersion exception is raised is the serialized primitive has is labelled with a version that is not known locally. The exception indicates what version is known locallay, and the deserialization attempts backport the primitive to the local version. If an object A has an ObjectField b containing object B and it is B that has the incompatible version, the version number in the exception will be the the locally supported version for B. The desrialization will then attempt to backport the primitive of object A to the locally supported version number for object B. ** 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/1275675 Title: Version change in ObjectField does not work with back-levelling Status in OpenStack Compute (Nova): New Bug description: When a NovaObject primitive is deserialized the object version is checked and an IncompatibleObjectVersion exception is raised is the serialized primitive has is labelled with a version that is not known locally. The exception indicates what version is known locallay, and the deserialization attempts backport the primitive to the local version. If an object A has an ObjectField b containing object B and it is B that has the incompatible version, the version number in the exception will be the the locally supported version for B. The desrialization will then attempt to backport the primitive of object A to the locally supported version number for object B. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275675/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275686] [NEW] Non-ascii characters does not handled correctly.
Public bug reported: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. ** Affects: keystone Importance: Undecided Assignee: Ilya Pekelny (i159) Status: In Progress ** Changed in: keystone Assignee: (unassigned) = Ilya Pekelny (i159) ** Changed in: keystone Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1275686 Title: Non-ascii characters does not handled correctly. Status in OpenStack Identity (Keystone): In Progress Bug description: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275693] [NEW] Wrong oauth1_extension used instead of oauth_extension in documentation
Public bug reported: The documentation in doc/source/extensions/oauth1-configuration.rst states that oauth1_extension should be used. However, in the paste configuration file and in the tests, oauth_extension is be used. ** 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/1275693 Title: Wrong oauth1_extension used instead of oauth_extension in documentation Status in OpenStack Identity (Keystone): New Bug description: The documentation in doc/source/extensions/oauth1-configuration.rst states that oauth1_extension should be used. However, in the paste configuration file and in the tests, oauth_extension is be used. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275693/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275695] [NEW] Enabling Federation extension causes Unregistered dependency: federation_api
Public bug reported: Enabling the Federation extension, according with doc/source/extensions /federation-configuration.rst makes Keystone crash with the following exception: Traceback (most recent call last): File /usr/lib/cgi-bin/keystone/main, line 60, in module dependency.resolve_future_dependencies() File /opt/stack/keystone/keystone/common/dependency.py, line 251, in resolve_future_dependencies raise UnresolvableDependencyException(dependency) UnresolvableDependencyException: Unregistered dependency: federation_api Since the dependency is never registered. ** 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/1275695 Title: Enabling Federation extension causes Unregistered dependency: federation_api Status in OpenStack Identity (Keystone): New Bug description: Enabling the Federation extension, according with doc/source/extensions/federation-configuration.rst makes Keystone crash with the following exception: Traceback (most recent call last): File /usr/lib/cgi-bin/keystone/main, line 60, in module dependency.resolve_future_dependencies() File /opt/stack/keystone/keystone/common/dependency.py, line 251, in resolve_future_dependencies raise UnresolvableDependencyException(dependency) UnresolvableDependencyException: Unregistered dependency: federation_api Since the dependency is never registered. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275695/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275716] [NEW] psutil = 1.1.0 is actually on PyPI
Public bug reported: Downloading/unpacking psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) Could not find a version that satisfies the requirement psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) Some externally hosted files were ignored (use --allow-external to allow). ** Affects: glance Importance: High Assignee: Fei Long Wang (flwang) Status: Triaged ** Description changed: - Downloading/unpacking psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_rebase/glance/test-requirements.txt (line 19)) - Could not find a version that satisfies the requirement psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_rebase/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) - Some externally hosted files were ignored (use --allow-external to allow). + Downloading/unpacking psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) + Could not find a version that satisfies the requirement psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_rebase/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) + Some externally hosted files were ignored (use --allow-external to allow). ** Description changed: Downloading/unpacking psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) - Could not find a version that satisfies the requirement psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_rebase/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) + Could not find a version that satisfies the requirement psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) Some externally hosted files were ignored (use --allow-external to allow). ** Changed in: glance Assignee: (unassigned) = Fei Long Wang (flwang) ** Changed in: glance Importance: Undecided = High ** Changed in: glance Status: New = Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1275716 Title: psutil = 1.1.0 is actually on PyPI Status in OpenStack Image Registry and Delivery Service (Glance): Triaged Bug description: Downloading/unpacking psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) Could not find a version that satisfies the requirement psutil=0.6.1,1.0 (from -r /home/flwang/MyWorkSpace/workspace_community/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) Some externally hosted files were ignored (use --allow-external to allow). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1275716/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275741] [NEW] attach and detach interface should check lock
Public bug reported: attach_interface and detach_interface will modify the instance, so it should check the lock state first ** Affects: nova Importance: Undecided Assignee: jichencom (jichenjc) Status: New ** Changed in: nova Assignee: (unassigned) = jichencom (jichenjc) -- 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/1275741 Title: attach and detach interface should check lock Status in OpenStack Compute (Nova): New Bug description: attach_interface and detach_interface will modify the instance, so it should check the lock state first To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275741/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275744] [NEW] v3/projects /{project_id}/users/{user_id}/roles will not work for inherited roles
Public bug reported:
When using inherites roles and the roles list call is made for the
user in the project, with v3, inherited roles are not shown. If we use
v2.0 (v2.0/tenants/{tenant_id}/users/{user_id}/roles) works correctly
and shown the inherited roles.
** Affects: keystone
Importance: Undecided
Status: New
** Description changed:
When using inherites roles and the roles list call is made for the
user in the project, with v3, inherited roles are not shown. If we use
- v2.0 (v2.0/tenants / tenant_id {} / users / {user_id} / roles) works
- correctly and shown the inherited roles.
+ v2.0 (v2.0/tenants/{tenant_id}/users/{user_id}/roles) works correctly
+ and shown the inherited roles.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1275744
Title:
v3/projects /{project_id}/users/{user_id}/roles will not work for
inherited roles
Status in OpenStack Identity (Keystone):
New
Bug description:
When using inherites roles and the roles list call is made for the
user in the project, with v3, inherited roles are not shown. If we use
v2.0 (v2.0/tenants/{tenant_id}/users/{user_id}/roles) works correctly
and shown the inherited roles.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1275744/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275755] [NEW] v2 volume api should return volumenotfound
Public bug reported: currently, NotFound exception was raised when no volume found in v2 api this will not be helpful to user especially there is no 'ec2 error code' returned ** Affects: nova Importance: Undecided Assignee: jichencom (jichenjc) Status: New ** Changed in: nova Assignee: (unassigned) = jichencom (jichenjc) -- 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/1275755 Title: v2 volume api should return volumenotfound Status in OpenStack Compute (Nova): New Bug description: currently, NotFound exception was raised when no volume found in v2 api this will not be helpful to user especially there is no 'ec2 error code' returned To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275755/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1266960] Re: InstanceIsLocked Exception didn't raise
let me know your opinion and suggestion, thanks ** Changed in: nova Status: Opinion = New ** Changed in: nova Assignee: jichencom (jichenjc) = (unassigned) -- 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/1266960 Title: InstanceIsLocked Exception didn't raise Status in OpenStack Compute (Nova): New Bug description: When VM is locked by nova, VM API should not execute. There are so many api that cannot be executed when vm is locked. But When API is tried, nova raise inappropriate InstanceInvalidSate exception instead of InstanceIsLocked exception. example) $ nova reboot 9b4a0687-d1f5-4dac-a49e-f5c6d1f3e316 ERROR: Instance is in an invalid state for 'reboot' (HTTP 409) (Request-ID: req-8407d42d-9f0e-4c91-995b-35025251f209) $ nova delete 9b4a0687-d1f5-4dac-a49e-f5c6d1f3e316 Instance is in an invalid state for 'delete' (HTTP 409) (Request-ID: req-f1b144b6-958e-4b19-84c7-fa641344d4d5) This case is occured from so many compute api. delete reboot rebuild resize shelve pause unpause suspend resume rescue unrescue attach_volume detach_volume update_instance_metadata InstanceInvalidState is used at many api to check state is appropriate, but InstanceIsLocked inherited InstanceInvalidState, when vm is locked, api request return InstanceInvalidState instead of InstanceIsLocked. So I suggest modify InstanceIsLocked inherit Invalid instead of InstanceInvalidState. InstanceIsLocked(InstanceInvalidState) - InstanceIsLocked(Invalid) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1266960/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275773] [NEW] VMware session not logged out on VMwareAPISession garbage collection
Public bug reported: A bug in VMwareAPISession.__del__() prevents the session being logged out when the session object is garbage collected. ** Affects: nova Importance: Medium Status: New ** Tags: havana-backport-potential vmware -- 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/1275773 Title: VMware session not logged out on VMwareAPISession garbage collection Status in OpenStack Compute (Nova): New Bug description: A bug in VMwareAPISession.__del__() prevents the session being logged out when the session object is garbage collected. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275773/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275686] Re: Non-ascii characters not handled correctly
** Also affects: oslo Importance: Undecided Status: New ** Changed in: oslo Assignee: (unassigned) = Ilya Pekelny (i159) ** Changed in: oslo Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1275686 Title: Non-ascii characters not handled correctly Status in OpenStack Identity (Keystone): In Progress Status in Oslo - a Library of Common OpenStack Code: In Progress Bug description: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275772] [NEW] Missing raise statement in the Hyper-V driver when checking the config driver format
Public bug reported: There's a missing raise statement when checking the ConfigDrive format: https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L283 ** Affects: nova Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: hyper-v ** Tags added: havana-backport-potential -- 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/1275772 Title: Missing raise statement in the Hyper-V driver when checking the config driver format Status in OpenStack Compute (Nova): New Bug description: There's a missing raise statement when checking the ConfigDrive format: https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L283 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275772/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275789] [NEW] KeyError 'svc_type' in unit tests
Public bug reported:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162ERROR
[neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
neutron/tests/unit/test_provider_configuration.py, line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 108, in match
2014-02-03 08:44:47.768 | mismatch = self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py,
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File neutron/services/provider_configuration.py,
line 74, in parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File neutron/openstack/common/gettextutils.py,
line 199, in __mod__
2014-02-03 08:44:47.775 | params=self._sanitize_mod_params(other),
2014-02-03 08:44:47.776 | File neutron/openstack/common/gettextutils.py,
line 215, in _sanitize_mod_params
2014-02-03 08:44:47.776 | params = self._trim_dictionary_parameters(other)
2014-02-03 08:44:47.776 | File neutron/openstack/common/gettextutils.py,
line 239, in _trim_dictionary_parameters
2014-02-03 08:44:47.777 | params[key] = self._copy_param(dict_param[key])
2014-02-03 08:44:47.777 | KeyError: 'svc_type'
** Affects: neutron
Importance: Undecided
Assignee: Henry Gessau (gessau)
Status: New
** Changed in: neutron
Assignee: (unassigned) = Henry Gessau (gessau)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275789
Title:
KeyError 'svc_type' in unit tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
[Yahoo-eng-team] [Bug 1275802] [NEW] Wrong variable name in debug statement in the Hyper-V driver
Public bug reported: Here's a minor issue in the naming of a variable in a debug statement formatting: https://github.com/openstack/nova/blob/8f28ddd13a91eb25f0f2f3a312068223500ded97/nova/virt/hyperv/snapshotops.py#L107 ** Affects: nova Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: havana-backport-potential hyper-v -- 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/1275802 Title: Wrong variable name in debug statement in the Hyper-V driver Status in OpenStack Compute (Nova): New Bug description: Here's a minor issue in the naming of a variable in a debug statement formatting: https://github.com/openstack/nova/blob/8f28ddd13a91eb25f0f2f3a312068223500ded97/nova/virt/hyperv/snapshotops.py#L107 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275802/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275789] Re: KeyError 'svc_type' in unit tests
*** This bug is a duplicate of bug 1270212 ***
https://bugs.launchpad.net/bugs/1270212
Marked as duplicate to bug #1270212 (which is the sourced duplicate of
bug #1270182).
** This bug has been marked a duplicate of bug 1270212
regression: multiple calls to Message.__mod__ trigger exceptions
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275789
Title:
KeyError 'svc_type' in unit tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
neutron/tests/unit/test_provider_configuration.py, line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 108, in match
2014-02-03 08:44:47.768 | mismatch =
self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py,
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File
neutron/services/provider_configuration.py, line 74, in
parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File neutron/openstack/common/gettextutils.py,
line 199, in __mod__
2014-02-03 08:44:47.775 | params=self._sanitize_mod_params(other),
2014-02-03 08:44:47.776 | File neutron/openstack/common/gettextutils.py,
line 215, in _sanitize_mod_params
2014-02-03 08:44:47.776 | params = self._trim_dictionary_parameters(other)
2014-02-03 08:44:47.776 | File neutron/openstack/common/gettextutils.py,
line 239, in _trim_dictionary_parameters
2014-02-03 08:44:47.777
[Yahoo-eng-team] [Bug 1275805] [NEW] Wrong variable used in log statement in the HYper-V driver
Public bug reported: This patch includes some improved logging during resizes in the Hyper-V driver: https://review.openstack.org/#/c/51129/ There's a small issue in the variable used: root_vhd should be replaced with root_vhd_internal_size ** Affects: nova Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: havana-backport-potential hyper-v -- 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/1275805 Title: Wrong variable used in log statement in the HYper-V driver Status in OpenStack Compute (Nova): New Bug description: This patch includes some improved logging during resizes in the Hyper-V driver: https://review.openstack.org/#/c/51129/ There's a small issue in the variable used: root_vhd should be replaced with root_vhd_internal_size To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275805/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275771] Re: Notifications do not work: AttributeError: 'RequestContext' object has no attribute 'iteritems'
** Also affects: oslo.messaging
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/1275771
Title:
Notifications do not work: AttributeError: 'RequestContext' object has
no attribute 'iteritems'
Status in OpenStack Compute (Nova):
New
Status in Messaging API for OpenStack:
New
Bug description:
When enabling notification with notification_driver = messaging, I get
the following:
2014-02-03 14:20:41.152 ERROR oslo.messaging.notify._impl_messaging [-] Could
not send notification to notifications. Payload={'priority': 'INFO',
'_unique_id': 'da748b32fd144c25adc45ba5b393339d', 'event_type':
'compute.instance.create.end', 'timestamp': '2014-02-03 14:20:41.151419',
'publisher_id': 'compute.devstack', 'payload': {'node': u'devstack',
'state_description': '', 'ramdisk_id': u'37ad58df-c587-4bed-9062-9428ca14eaf0',
'created_at': '2014-02-03 14:20:33+00:00', 'access_ip_v6': None, 'disk_gb': 0,
'availability_zone': u'nova', 'terminated_at': '', 'ephemeral_gb': 0,
'instance_type_id': 6, 'instance_flavor_id': '42', 'image_name':
u'cirros-0.3.1-x86_64-uec', 'host': u'devstack', 'fixed_ips':
[FixedIP({'version': 4, 'floating_ips': [], 'label': u'private', 'meta': {},
'address': u'10.0.0.2', 'type': u'fixed'})], 'user_id':
u'6bcbc8f54d65473c9a0c4a55f64fb580', 'message': u'Success', 'deleted_at': '',
'reservation_id': u'r-jycyyveh', 'image_ref_url': u'http://162.209.87.220:9
292/images/7b8d712a-fb31-43b8-8a05-a74d70fd8a11', 'memory_mb': 64, 'root_gb':
0, 'display_name': u'dwq', 'instance_type': 'm1.nano', 'tenant_id':
u'cda1741ff4ef47f48fb3d9d76e302add', 'access_ip_v4': None, 'hostname': u'dwq',
'vcpus': 1, 'instance_id': '272c2ec6-bb98-4e84-9377-84c63c7a9ce9', 'kernel_id':
u'5d1a6130-0e6a-4155-9c05-0174a654da68', 'state': u'active', 'image_meta':
{u'kernel_id': u'5d1a6130-0e6a-4155-9c05-0174a654da68', u'container_format':
u'ami', u'min_ram': u'0', u'ramdisk_id':
u'37ad58df-c587-4bed-9062-9428ca14eaf0', u'disk_format': u'ami', u'min_disk':
u'0', u'base_image_ref': u'7b8d712a-fb31-43b8-8a05-a74d70fd8a11'},
'architecture': None, 'os_type': None, 'launched_at':
'2014-02-03T14:20:41.070490', 'metadata': {}}, 'message_id':
'03b2985a-6bcd-44ff-8303-29618d3c2b01'}
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging Traceback
(most recent call last):
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging File
/opt/stack/oslo.messaging/oslo/messaging/notify/_impl_messaging.py, line 47,
in notify
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
version=self.version)
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging File
/opt/stack/oslo.messaging/oslo/messaging/transport.py, line 93, in
_send_notification
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
self._driver.send_notification(target, ctxt, message, version)
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging File
/opt/stack/oslo.messaging/oslo/messaging/_drivers/amqpdriver.py, line 393, in
send_notification
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
return self._send(target, ctxt, message, envelope=(version == 2.0))
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging File
/opt/stack/oslo.messaging/oslo/messaging/_drivers/amqpdriver.py, line 362, in
_send
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
rpc_amqp.pack_context(msg, context)
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging File
/opt/stack/oslo.messaging/oslo/messaging/_drivers/amqp.py, line 299, in
pack_context
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
context_d = six.iteritems(context.to_dict())
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging File
/usr/local/lib/python2.7/dist-packages/six.py, line 484, in iteritems
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
return iter(getattr(d, _iteritems)(**kw))
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
AttributeError: 'RequestContext' object has no attribute 'iteritems'
2014-02-03 14:20:41.152 TRACE oslo.messaging.notify._impl_messaging
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275771/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275822] [NEW] VMware: redundant VC call after VM creation
Public bug reported: We have the following code in the spawn() method in vmops.py: def spawn(...): ... def _execute_create_vm(): vm_create_task = self._session._call_method(...) self._session._wait_for_task(instance['uuid'], vm_create_task) _execute_create_vm() vm_ref = vm_util.get_vm_ref_from_name(self._session, instance_name) ... get_vm_ref_from_name() is making remote call which is redundant because we can obtain a reference to the created VM from the CreateVM task itself. From the the vSphere documentation: This method returns a Task object with which to monitor the operation. The info.result property in the Task contains the newly created VirtualMachine upon success. We should fix _execute_create_vm() to get the VM from the task and return it. ** Affects: nova Importance: Undecided Status: New ** Tags: vmware -- 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/1275822 Title: VMware: redundant VC call after VM creation Status in OpenStack Compute (Nova): New Bug description: We have the following code in the spawn() method in vmops.py: def spawn(...): ... def _execute_create_vm(): vm_create_task = self._session._call_method(...) self._session._wait_for_task(instance['uuid'], vm_create_task) _execute_create_vm() vm_ref = vm_util.get_vm_ref_from_name(self._session, instance_name) ... get_vm_ref_from_name() is making remote call which is redundant because we can obtain a reference to the created VM from the CreateVM task itself. From the the vSphere documentation: This method returns a Task object with which to monitor the operation. The info.result property in the Task contains the newly created VirtualMachine upon success. We should fix _execute_create_vm() to get the VM from the task and return it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275822/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275823] [NEW] RFE: default keystone.conf file should point to correct paths for cert files
Public bug reported: To enable ssl in keystone, you have to uncomment the following lines in kestone.conf: #enable = True #certfile = /etc/keystone/pki/certs/ssl_cert.pem #keyfile = /etc/keystone/pki/private/ssl_key.pem #ca_certs = /etc/keystone/pki/certs/cacert.pem #ca_key = /etc/keystone/pki/private/cakey.pem The above file paths are invalid in the default keystone setup. The correct paths are: certfile = /etc/keystone/ssl/certs/ca.pem keyfile = /etc/keystone/ssl/certs/cakey.pem ca_certs = /etc/keystone/ssl/certs/signing_cert.pem ca_key = /etc/keystone/ssl/private/signing_key.pem The default keystone.conf file should already have the correct paths in it, even if they are commented out. ** 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/1275823 Title: RFE: default keystone.conf file should point to correct paths for cert files Status in OpenStack Identity (Keystone): New Bug description: To enable ssl in keystone, you have to uncomment the following lines in kestone.conf: #enable = True #certfile = /etc/keystone/pki/certs/ssl_cert.pem #keyfile = /etc/keystone/pki/private/ssl_key.pem #ca_certs = /etc/keystone/pki/certs/cacert.pem #ca_key = /etc/keystone/pki/private/cakey.pem The above file paths are invalid in the default keystone setup. The correct paths are: certfile = /etc/keystone/ssl/certs/ca.pem keyfile = /etc/keystone/ssl/certs/cakey.pem ca_certs = /etc/keystone/ssl/certs/signing_cert.pem ca_key = /etc/keystone/ssl/private/signing_key.pem The default keystone.conf file should already have the correct paths in it, even if they are commented out. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275823/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275789] Re: KeyError 'svc_type' in unit tests
OK I agree the KeyError part is a duplicate of bug #1270212.
But I really meant to file this bug against:
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']
** Summary changed:
- KeyError 'svc_type' in unit tests
+ ERROR [neutron.services.provider_configuration] Service type 'svc_type' is
not allowed in unit tests
** This bug is no longer a duplicate of bug 1270212
regression: multiple calls to Message.__mod__ trigger exceptions
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275789
Title:
ERROR [neutron.services.provider_configuration] Service type
'svc_type' is not allowed in unit tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
neutron/tests/unit/test_provider_configuration.py, line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 108, in match
2014-02-03 08:44:47.768 | mismatch =
self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py,
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File
neutron/services/provider_configuration.py, line 74, in
parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File neutron/openstack/common/gettextutils.py,
line 199, in __mod__
2014-02-03 08:44:47.775 |
[Yahoo-eng-team] [Bug 1275789] Re: ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not allowed in unit tests
*** This bug is a duplicate of bug 1270212 ***
https://bugs.launchpad.net/bugs/1270212
Nope. You are right Amir. It seems that ERROR is a fallout of Bug
#1270212.
** This bug has been marked a duplicate of bug 1270212
regression: multiple calls to Message.__mod__ trigger exceptions
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275789
Title:
ERROR [neutron.services.provider_configuration] Service type
'svc_type' is not allowed in unit tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
neutron/tests/unit/test_provider_configuration.py, line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 108, in match
2014-02-03 08:44:47.768 | mismatch =
self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py,
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py,
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py,
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File
neutron/services/provider_configuration.py, line 74, in
parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File neutron/common/exceptions.py, line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File neutron/openstack/common/gettextutils.py,
line 199, in __mod__
2014-02-03 08:44:47.775 | params=self._sanitize_mod_params(other),
2014-02-03 08:44:47.776 | File neutron/openstack/common/gettextutils.py,
line 215, in _sanitize_mod_params
2014-02-03 08:44:47.776 | params = self._trim_dictionary_parameters(other)
2014-02-03 08:44:47.776 | File neutron/openstack/common/gettextutils.py,
line
[Yahoo-eng-team] [Bug 1267191] Re: openstack-nova-compute service fails with - libvirtError: internal error: CPU feature `avx' specified more than once
Hmm, just wondering. . .
Ideally, these kind of bugs under the hood technologies that affect
OpenStack could be closed as reason -- CLOSED, UPSTREAM
But, closing it as Fix Committed is a misleading -- as there's no
actual fix committed in openstack-nova.
So, closing it as Invalid, Not a bug (technically, this is right -- as
it's not a Nova bug; but a bug in libvirt that _affected_ Nova).
** Changed in: nova
Status: Fix Committed = 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/1267191
Title:
openstack-nova-compute service fails with - libvirtError: internal
error: CPU feature `avx' specified more than once
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Description of problem
---
Restarting openstack-nova-compute serivce fails with:
libvirtError: internal error: CPU feature `avx' specified more than
once
Version
-
$ rpm -q openstack-nova libvirt qemu-system-x86
openstack-nova-2014.1-0.4.b1.fc21.noarch
libvirt-1.1.3.2-1.fc20.x86_64
qemu-system-x86-1.6.1-3.fc20.x86_64
Test env
--
A two node OpenStack RDO set-up configured manually on two Fedora 20
VMs:
- Controller node: Nova, Keystone, Cinder, Glance, Neutron (using Open
vSwitch plugin and GRE tunneling).
- Compute node: Nova (nova-compute), Neutron (openvswitch-agent)
How reproducible: Consistently.
Steps to Reproduce
--
$ systemctl restart openstack-nova-compute
Observe /var/log/nova/compute.log
Actual results
--
$ tail -f /var/log/nova/compute.log
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup File
/usr/lib/python2.7/site-packages/eventlet/tpool.py, line 187, in doit
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup
result = proxy_call(self._autowrap, f, *args, **kwargs)
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup File
/usr/lib/python2.7/site-packages/eventlet/tpool.py, line 147, in proxy_call
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup rv =
execute(f,*args,**kwargs)
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup File
/usr/lib/python2.7/site-packages/eventlet/tpool.py, line 76, in tworker
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup rv =
meth(*args,**kwargs)
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup File
/usr/lib64/python2.7/site-packages/libvirt.py, line 3622, in baselineCPU
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup if
ret is None: raise libvirtError ('virConnectBaselineCPU() failed', conn=self)
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup
libvirtError: internal error: CPU feature `avx' specified more than once
2014-01-08 07:00:07.200 1529 TRACE nova.openstack.common.threadgroup
Expected results
Compute service should start successfully.
Additional info
---
Status of openstack-nova-compute service
$ systemctl status openstack-nova-compute
openstack-nova-compute.service - OpenStack Nova Compute Server
Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service;
enabled)
Active: inactive (dead) since Tue 2014-01-08 07:00:07 EST; 13min ago
Process: 1529 ExecStart=/usr/bin/nova-compute --logfile
/var/log/nova/compute.log (code=exited, status=0/SUCCESS)
Main PID: 1529 (code=exited, status=0/SUCCESS)
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup File /usr/lib/pyth...in doit
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup result = proxy_ca...kwargs)
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup File /usr/lib/pyth...xy_call
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup rv = execute(f,*a...kwargs)
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup File /usr/lib/pyth...tworker
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup rv = meth(*args,**kwargs)
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup File /usr/lib64/py...lineCPU
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup if ret is None: r...n=self)
Jan 07 07:00:07 node2-compute nova-compute[1529]: 2014-01-08
[Yahoo-eng-team] [Bug 1275857] [NEW] FAIL: nova.tests.compute.test_compute.ComputeAPIAggrTestCase.test_update_aggregate_metadata
Public bug reported:
Just started seeing this in the gate jobs gate-nova-python27 and gate-
nova-python26
Logstash query:
message:FAIL:
nova.tests.compute.test_compute.ComputeAPIAggrTestCase.test_update_aggregate_metadata
AND filename:console.html
Stack trace:
2014-02-03 17:45:15.744 |
==
2014-02-03 17:45:15.745 | FAIL:
nova.tests.compute.test_compute.ComputeAPIAggrTestCase.test_update_aggregate_metadata
2014-02-03 17:45:15.745 | tags: worker-3
2014-02-03 17:45:15.745 |
--
2014-02-03 17:45:15.745 | Empty attachments:
2014-02-03 17:45:15.745 | stderr
2014-02-03 17:45:15.745 | stdout
2014-02-03 17:45:15.745 |
2014-02-03 17:45:15.746 | pythonlogging:'': {{{
2014-02-03 17:45:15.746 | INFO [nova.virt.driver] Loading compute driver
'nova.virt.fake.FakeDriver'
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Auditing
locally available compute resources
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Free ram (MB):
7680
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Free disk (GB):
1028
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Free VCPUS: 1
2014-02-03 17:45:15.746 | INFO [nova.compute.resource_tracker] Compute_service
record created for fake-mini:fakenode1
2014-02-03 17:45:15.747 | AUDIT [nova.compute.manager] Deleting orphan compute
node 2
2014-02-03 17:45:15.747 | }}}
2014-02-03 17:45:15.747 |
2014-02-03 17:45:15.747 | Traceback (most recent call last):
2014-02-03 17:45:15.747 | File nova/tests/compute/test_compute.py, line
8797, in test_update_aggregate_metadata
2014-02-03 17:45:15.747 | self.assertEqual(expected_payload_meta_data,
msg.payload['meta_data'])
2014-02-03 17:45:15.747 | File
/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/testtools/testcase.py,
line 321, in assertEqual
2014-02-03 17:45:15.748 | self.assertThat(observed, matcher, message)
2014-02-03 17:45:15.748 | File
/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/testtools/testcase.py,
line 406, in assertThat
2014-02-03 17:45:15.748 | raise mismatch_error
2014-02-03 17:45:15.748 | MismatchError: !=:
2014-02-03 17:45:15.748 | reference = {'foo_key1': None, 'foo_key2':
'foo_value2'}
2014-02-03 17:45:15.748 | actual= {'availability_zone': 'fake_zone',
'foo_key1': None, 'foo_key2': 'foo_value2'}
** Affects: nova
Importance: Undecided
Status: New
** Tags: gate-failure
** Tags added: gate-fail
** Tags removed: gate-fail
** Tags added: gate-failure
--
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/1275857
Title:
FAIL:
nova.tests.compute.test_compute.ComputeAPIAggrTestCase.test_update_aggregate_metadata
Status in OpenStack Compute (Nova):
New
Bug description:
Just started seeing this in the gate jobs gate-nova-python27 and gate-
nova-python26
Logstash query:
message:FAIL:
nova.tests.compute.test_compute.ComputeAPIAggrTestCase.test_update_aggregate_metadata
AND filename:console.html
Stack trace:
2014-02-03 17:45:15.744 |
==
2014-02-03 17:45:15.745 | FAIL:
nova.tests.compute.test_compute.ComputeAPIAggrTestCase.test_update_aggregate_metadata
2014-02-03 17:45:15.745 | tags: worker-3
2014-02-03 17:45:15.745 |
--
2014-02-03 17:45:15.745 | Empty attachments:
2014-02-03 17:45:15.745 | stderr
2014-02-03 17:45:15.745 | stdout
2014-02-03 17:45:15.745 |
2014-02-03 17:45:15.746 | pythonlogging:'': {{{
2014-02-03 17:45:15.746 | INFO [nova.virt.driver] Loading compute driver
'nova.virt.fake.FakeDriver'
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Auditing
locally available compute resources
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Free ram
(MB): 7680
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Free disk
(GB): 1028
2014-02-03 17:45:15.746 | AUDIT [nova.compute.resource_tracker] Free VCPUS: 1
2014-02-03 17:45:15.746 | INFO [nova.compute.resource_tracker]
Compute_service record created for fake-mini:fakenode1
2014-02-03 17:45:15.747 | AUDIT [nova.compute.manager] Deleting orphan
compute node 2
2014-02-03 17:45:15.747 | }}}
2014-02-03 17:45:15.747 |
2014-02-03 17:45:15.747 | Traceback (most recent call last):
2014-02-03 17:45:15.747 | File nova/tests/compute/test_compute.py, line
8797, in test_update_aggregate_metadata
2014-02-03 17:45:15.747 | self.assertEqual(expected_payload_meta_data,
msg.payload['meta_data'])
2014-02-03 17:45:15.747 | File
[Yahoo-eng-team] [Bug 1266906] Re: Volume type defaults remain in Defaults tab even after volume type is removed
** No longer affects: horizon -- 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/1266906 Title: Volume type defaults remain in Defaults tab even after volume type is removed Status in Cinder: In Progress Bug description: After creating a volume type 'abc' a number of default quotas are added to the Default tab's quota table: - Volumes Abc - Snapshots Abc - Gigabytes Abc I expected these defaults to be removed from the table once I remove the volume type. However, after removing the volume type they are still there. I verified that volume type was removed from the Volumes tab, and also marked deleted in Cinder database. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1266906/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275875] [NEW] Virt drivers should use standard image properties
Public bug reported:
Several virt drivers are using non-standard driver-specific image
metadata properties. This creates an API contract between the external
user and the driver implementation. These non-standard ones should be
marked as deprecated in some way, enforced in v3, etc. We need a global
whitelist of keys and values that are allowed so that we can make sure
others don't leak in.
Examples:
nova/virt/vmwareapi/vmops.py:os_type =
image_properties.get(vmware_ostype, otherGuest)
nova/virt/vmwareapi/vmops.py:adapter_type =
image_properties.get(vmware_adaptertype,
nova/virt/vmwareapi/vmops.py:disk_type =
image_properties.get(vmware_disktype,
nova/virt/vmwareapi/vmops.py:vif_model =
image_properties.get(hw_vif_model, VirtualE1000)
nova/virt/xenapi/vm_utils.py:device_id =
image_properties.get('xenapi_device_id')
I think it's important to try to get this fixed (or as close as
possible) before the icehouse release.
** Affects: nova
Importance: Medium
Status: Confirmed
--
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/1275875
Title:
Virt drivers should use standard image properties
Status in OpenStack Compute (Nova):
Confirmed
Bug description:
Several virt drivers are using non-standard driver-specific image
metadata properties. This creates an API contract between the external
user and the driver implementation. These non-standard ones should be
marked as deprecated in some way, enforced in v3, etc. We need a
global whitelist of keys and values that are allowed so that we can
make sure others don't leak in.
Examples:
nova/virt/vmwareapi/vmops.py:os_type =
image_properties.get(vmware_ostype, otherGuest)
nova/virt/vmwareapi/vmops.py:adapter_type =
image_properties.get(vmware_adaptertype,
nova/virt/vmwareapi/vmops.py:disk_type =
image_properties.get(vmware_disktype,
nova/virt/vmwareapi/vmops.py:vif_model =
image_properties.get(hw_vif_model, VirtualE1000)
nova/virt/xenapi/vm_utils.py:device_id =
image_properties.get('xenapi_device_id')
I think it's important to try to get this fixed (or as close as
possible) before the icehouse release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275875/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275907] [NEW] user_enabled and user_enabled_emulation_dn not documented
Public bug reported: The keystone configuration page lacks any documentation on these settings (http://docs.openstack.org/developer/keystone/configuration.html). I've spoken with Yorik (Yuriy) and given his bug and code comments I think I can get this documented. ** Affects: keystone Importance: Undecided Assignee: Matt Fischer (mfisch) Status: In Progress ** Changed in: keystone Assignee: (unassigned) = Matt Fischer (mfisch) ** Changed in: keystone Status: New = Incomplete ** Changed in: keystone Status: Incomplete = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1275907 Title: user_enabled and user_enabled_emulation_dn not documented Status in OpenStack Identity (Keystone): In Progress Bug description: The keystone configuration page lacks any documentation on these settings (http://docs.openstack.org/developer/keystone/configuration.html). I've spoken with Yorik (Yuriy) and given his bug and code comments I think I can get this documented. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275907/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275906] [NEW] Remove str() from message formating block
Public bug reported: Remove str() from message formatting code, example: Error %s % str(x), because %s conversion converts any Python object using str() ** 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/1275906 Title: Remove str() from message formating block Status in OpenStack Compute (Nova): New Bug description: Remove str() from message formatting code, example: Error %s % str(x), because %s conversion converts any Python object using str() To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275906/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
** Changed in: python-keystoneclient Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in Cinder: Opinion Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic (Bare Metal Provisioning): Fix Released Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): Invalid Status in OpenStack Compute (Nova): In Progress Status in Python client library for Ceilometer: Fix Committed Status in Python client library for Cinder: In Progress Status in Python client library for Keystone: Fix Released Status in Python client library for Nova: Fix Committed Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275911] [NEW] More dropdown menu cutoff for last item in Projects table
Public bug reported: Login as admin and navigate to Admin Projects. Clicking on the More button next to any but the last item on the Projects page opens a dropdown menu which has 4 items: Edit Project, View Usage, Modify Quotas, and Delete Project. Clicking More next to the last item in the table only shows the first 2 items: Edit Project and View Usage. The other two are cutoff. See attached screenshot. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Screenshot of cutoff issue https://bugs.launchpad.net/bugs/1275911/+attachment/3968033/+files/MenuCutoff.PNG ** Description changed: Login as admin and navigate to Admin Projects. Clicking on the More button next to any but the last item on the Projects page opens a dropdown menu which has 4 items: Edit Project, - View Usage, Modify Quotas and Delete Project. Clciking More next to the - last item in the table only shows the first 2 items: Edit Project and - View Usage. The other two are cutoff. + View Usage, Modify Quotas, and Delete Project. Clicking More next to + the last item in the table only shows the first 2 items: Edit Project + and View Usage. The other two are cutoff. See attached screenshot. -- 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/1275911 Title: More dropdown menu cutoff for last item in Projects table Status in OpenStack Dashboard (Horizon): New Bug description: Login as admin and navigate to Admin Projects. Clicking on the More button next to any but the last item on the Projects page opens a dropdown menu which has 4 items: Edit Project, View Usage, Modify Quotas, and Delete Project. Clicking More next to the last item in the table only shows the first 2 items: Edit Project and View Usage. The other two are cutoff. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1275911/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275934] [NEW] Disallow duplicate instance names within the same project
Public bug reported: Currently it is possible to pick duplicate names for instances in the same project. Ideally, with the score of a project, users should not be able to create instances with existing names, or update instance names to a name that already exists. When Instance Count is greater than 1 in Launch Instance screen the instance id is appended to the entered name to guarantee uniqueness. This uniqueness should apply to manual creation too. ** Affects: horizon Importance: Undecided Assignee: Vahid Hashemian (vahidhashemian) Status: New ** Tags: duplicate instance name ** Changed in: horizon Assignee: (unassigned) = Vahid Hashemian (vahidhashemian) -- 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/1275934 Title: Disallow duplicate instance names within the same project Status in OpenStack Dashboard (Horizon): New Bug description: Currently it is possible to pick duplicate names for instances in the same project. Ideally, with the score of a project, users should not be able to create instances with existing names, or update instance names to a name that already exists. When Instance Count is greater than 1 in Launch Instance screen the instance id is appended to the entered name to guarantee uniqueness. This uniqueness should apply to manual creation too. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1275934/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275935] [NEW] update Volume Snapshot description
Public bug reported: On the 'Create Snapshot' popup for Project Volume table, the Description portion on the right hand side should be updated to reflect the action. Right now, it is the same as 'Create Volume' description. ** 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/1275935 Title: update Volume Snapshot description Status in OpenStack Dashboard (Horizon): New Bug description: On the 'Create Snapshot' popup for Project Volume table, the Description portion on the right hand side should be updated to reflect the action. Right now, it is the same as 'Create Volume' description. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1275935/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275937] [NEW] More buttons don't work in IE9
Public bug reported: More buttons don't work in IE9. Nothing happens when I click on one. I've tried those on the Flavors, Projects and Users pages. This issue does not occur with Chrome or with Firefox. ** 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/1275937 Title: More buttons don't work in IE9 Status in OpenStack Dashboard (Horizon): New Bug description: More buttons don't work in IE9. Nothing happens when I click on one. I've tried those on the Flavors, Projects and Users pages. This issue does not occur with Chrome or with Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1275937/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275950] [NEW] Missing Cancel button on some Create/Edit screens
Public bug reported: The Cancel button is missing on these dialog boxes: - Project - Instances - +Launch Instance / Edit Instance / Edit Security Group / Resize Instance - Admin - Instances - Edit Instance - Admin - Flavors - +Create Flavor / Edit Flavor / Modify Access - Admin - Defaults - Update Defaults - Admin - Projects - +Create Project / Modify Users / Edit Project / Modify Quota Adding it on these forms would improve usability and consistency with other screens that already have the Cancel button. ** Affects: horizon Importance: Undecided Assignee: Vahid Hashemian (vahidhashemian) Status: New ** Tags: box button cancel dialog ** Changed in: horizon Assignee: (unassigned) = Vahid Hashemian (vahidhashemian) -- 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/1275950 Title: Missing Cancel button on some Create/Edit screens Status in OpenStack Dashboard (Horizon): New Bug description: The Cancel button is missing on these dialog boxes: - Project - Instances - +Launch Instance / Edit Instance / Edit Security Group / Resize Instance - Admin - Instances - Edit Instance - Admin - Flavors - +Create Flavor / Edit Flavor / Modify Access - Admin - Defaults - Update Defaults - Admin - Projects - +Create Project / Modify Users / Edit Project / Modify Quota Adding it on these forms would improve usability and consistency with other screens that already have the Cancel button. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1275950/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1226120] Re: bootstrap dropdown buttons do not work without javascript
We've made the decision moving forward that Horizon will require JavaScript to be fully functional. The functionality should still be accessible via screen readers. If this is not the case, please update this bug. ** Changed in: horizon Status: Confirmed = Won't Fix ** Changed in: horizon Importance: Medium = Wishlist -- 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/1226120 Title: bootstrap dropdown buttons do not work without javascript Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: When using a browser with javascript deactivated (or a javascript uncapable browser), the bootstrap dropdown buttons do not work. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1226120/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275967] [NEW] duplicate rpc_backend registration
Public bug reported: nova was recently ported to oslo.incubator. This results in devstack raising an exception about duplicate rpc_backend options being registered. The problem is that openstack/common/service.py was not updated as part of that work. ** Affects: nova Importance: Undecided Assignee: Steve Loranz (steveloranz) Status: New ** Changed in: nova Assignee: (unassigned) = Steve Loranz (steveloranz) -- 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/1275967 Title: duplicate rpc_backend registration Status in OpenStack Compute (Nova): New Bug description: nova was recently ported to oslo.incubator. This results in devstack raising an exception about duplicate rpc_backend options being registered. The problem is that openstack/common/service.py was not updated as part of that work. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275967/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275686] Re: Non-ascii characters not handled correctly
*** This bug is a duplicate of bug 1273301 *** https://bugs.launchpad.net/bugs/1273301 ** This bug has been marked a duplicate of bug 1273301 Unit test failure: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. ** Also 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/1275686 Title: Non-ascii characters not handled correctly Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): New Status in Oslo - a Library of Common OpenStack Code: In Progress Bug description: We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error: UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1275686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1209345] Re: Migration tests fail with sqlalchemy 0.8
Marking this as invalid since it must be working, we're now supporting sqlalchemy 0.8. ** Changed in: nova Status: Incomplete = 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/1209345 Title: Migration tests fail with sqlalchemy 0.8 Status in OpenStack Compute (Nova): Invalid Bug description: File /��BUILDDIR��/nova-2013.2+git201308071233~saucy/nova/db/sqlalchemy/migrate_repo/versions/206_add_instance_cleaned.py, line 47, in downgrade instances.columns.cleaned.drop() File /usr/lib/python2.7/dist-packages/migrate/changeset/schema.py, line 549, in drop engine._run_visitor(visitorcallable, self, connection, **kwargs) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1479, in _run_visitor conn._run_visitor(visitorcallable, element, **kwargs) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1122, in _run_visitor **kwargs).traverse_single(element) File /usr/lib/python2.7/dist-packages/migrate/changeset/ansisql.py, line 53, in traverse_single ret = super(AlterTableVisitor, self).traverse_single(elem) File /usr/lib/python2.7/dist-packages/sqlalchemy/sql/visitors.py, line 111, in traverse_single return meth(obj, **kw) File /usr/lib/python2.7/dist-packages/migrate/changeset/databases/sqlite.py, line 90, in visit_column super(SQLiteColumnDropper,self).visit_column(column) File /usr/lib/python2.7/dist-packages/migrate/changeset/databases/sqlite.py, line 53, in visit_column self.recreate_table(table,column,delta) File /usr/lib/python2.7/dist-packages/migrate/changeset/databases/sqlite.py, line 40, in recreate_table table.create(bind=self.connection) File /usr/lib/python2.7/dist-packages/sqlalchemy/schema.py, line 614, in create checkfirst=checkfirst) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1122, in _run_visitor **kwargs).traverse_single(element) File /usr/lib/python2.7/dist-packages/sqlalchemy/sql/visitors.py, line 111, in traverse_single return meth(obj, **kw) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/ddl.py, line 93, in visit_table self.traverse_single(index) File /usr/lib/python2.7/dist-packages/sqlalchemy/sql/visitors.py, line 111, in traverse_single return meth(obj, **kw) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/ddl.py, line 105, in visit_index self.connection.execute(schema.CreateIndex(index)) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 662, in execute params) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 720, in _execute_ddl compiled File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 874, in _execute_context context) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1024, in _handle_dbapi_exception exc_info File /usr/lib/python2.7/dist-packages/sqlalchemy/util/compat.py, line 195, in raise_from_cause reraise(type(exception), exception, tb=exc_tb) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 867, in _execute_context context) File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py, line 324, in do_execute cursor.execute(statement, parameters) OperationalError: (OperationalError) table instances has no column named cleaned u'CREATE INDEX instances_host_deleted_cleaned_idx ON instances (host, deleted, cleaned)' () == FAIL: process-returncode tags: worker-0 -- To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1209345/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1264748] Re: nova command fails, when enable squid client in /etc/profile
** Changed in: nova
Status: Incomplete = 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/1264748
Title:
nova command fails, when enable squid client in /etc/profile
Status in OpenStack Compute (Nova):
Invalid
Bug description:
When testing OpenStack in my local environment, downloading package or
yum install takes a lot of time.
Thus, I enable squid in all nodes, by pointing http_proxy to a local squid
server.
,---
| echo export http_proxy='http://denny:@192.168.209.1:3128/' /etc/profile
`---
squid client works well, but nova cli fail.
,---
| [root@control ~(keystone_admin)]# nova --debug hypervisor-show 1
| nova --debug hypervisor-show 1
|
| REQ: curl -i http://192.168.209.131:35357/v2.0/tokens -X POST -H
Content-Type: application/json -H Accept: application/json -H User-Agent:
python-novaclient -d '{auth: {tenantName: admin, passwordCredentials:
{username: admin, password: 9d278a0b5fcc4f4e}}}'
|
| INFO (connectionpool:203) Starting new HTTP connection (1): 192.168.209.1
| DEBUG (connectionpool:295) POST http://192.168.209.131:35357/v2.0/tokens
HTTP/1.1 504 1113
| RESP: [504] {'content-length': '1113', 'via': '1.0
macs-mac-mini.att.net:3128 (squid/2.7.STABLE9)', 'x-cache': 'MISS from
macs-mac-mini.att.net', 'x-squid-error': 'ERR_CONNECT_FAIL 61', 'server':
'squid/2.7.STABLE9', 'connection': 'close', 'date': 'Sat, 28 Dec 2013 21:08:08
GMT', 'content-type': 'text/html'}
| RESP BODY: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
| HTMLHEADMETA HTTP-EQUIV=Content-Type CONTENT=text/html;
charset=iso-8859-1
| TITLEERROR: The requested URL could not be retrieved/TITLE
| STYLE
type=text/css!--BODY{background-color:#ff;font-family:verdana,sans-serif}PRE{font-family:sans-serif}--/STYLE
| /HEADBODY
| H1ERROR/H1
| H2The requested URL could not be retrieved/H2
| HR noshade size=1px
| P
| While trying to retrieve the URL:
| A
HREF=http://192.168.209.131:35357/v2.0/tokens;http://192.168.209.131:35357/v2.0/tokens/A
| P
| The following error was encountered:
| UL
| LI
| STRONG
| Connection to 192.168.209.131 Failed
| /STRONG
| /UL
|
| P
| The system returned:
| PREI(61) Connection refused/I/PRE
|
| P
| The remote host or network may be down. Please try the request again.
| PYour cache administrator is A HREF=mailto:webmaster;webmaster/A.
|
| BR clear=all
| HR noshade size=1px
| ADDRESS
| Generated Sat, 28 Dec 2013 21:08:08 GMT by macs-mac-mini.att.net
(squid/2.7.STABLE9)
| /ADDRESS
| /BODY/HTML
|
|
| DEBUG (shell:740) attribute 'message' of 'exceptions.BaseException'
objects (HTTP 504)
| Traceback (most recent call last):
| File /usr/lib/python2.6/site-packages/novaclient/shell.py, line 737, in
main
| OpenStackComputeShell().main(map(strutils.safe_decode, sys.argv[1:]))
| File /usr/lib/python2.6/site-packages/novaclient/shell.py, line 667, in
main
| self.cs.authenticate()
| File /usr/lib/python2.6/site-packages/novaclient/v1_1/client.py, line
171, in authenticate
| self.client.authenticate()
| File /usr/lib/python2.6/site-packages/novaclient/client.py, line 329,
in authenticate
| auth_url = self._v2_auth(auth_url)
| File /usr/lib/python2.6/site-packages/novaclient/client.py, line 411,
in _v2_auth
| return self._authenticate(url, body)
| File /usr/lib/python2.6/site-packages/novaclient/client.py, line 423,
in _authenticate
| **kwargs)
| File /usr/lib/python2.6/site-packages/novaclient/client.py, line 195,
in _time_request
| resp, body = self.request(url, method, **kwargs)
| File /usr/lib/python2.6/site-packages/novaclient/client.py, line 189,
in request
| raise exceptions.from_response(resp, body, url, method)
| ClientException: attribute 'message' of 'exceptions.BaseException'
objects (HTTP 504)
| ERROR: attribute 'message' of 'exceptions.BaseException' objects (HTTP
504)
`---
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1264748/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1276011] [NEW] Duplicate type defination in v2 images schema
Public bug reported: For example, see https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L664 and https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L666 ** Affects: glance Importance: Low Assignee: Fei Long Wang (flwang) Status: Triaged ** Changed in: glance Status: New = Triaged ** Changed in: glance Importance: Undecided = Low ** Changed in: glance Assignee: (unassigned) = Fei Long Wang (flwang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1276011 Title: Duplicate type defination in v2 images schema Status in OpenStack Image Registry and Delivery Service (Glance): Triaged Bug description: For example, see https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L664 and https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1276011/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1276017] [NEW] move default rule to policy section in keystone.conf
Public bug reported: The following is currently in the keystone.conf file: # Rule to check if no matching policy definition is found # FIXME(dolph): This should really be defined as [policy] default_rule # policy_default_rule = admin_required As the comment suggest, we should move the config option to the policy section. This will also impact oslo and we should ensure the old option is still supported for backwards compatibility. ** Affects: keystone Importance: Undecided Assignee: Steve Martinelli (stevemar) Status: New ** Affects: oslo Importance: Undecided Status: New ** Changed in: keystone Assignee: (unassigned) = Steve Martinelli (stevemar) ** Also affects: oslo 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/1276017 Title: move default rule to policy section in keystone.conf Status in OpenStack Identity (Keystone): New Status in Oslo - a Library of Common OpenStack Code: New Bug description: The following is currently in the keystone.conf file: # Rule to check if no matching policy definition is found # FIXME(dolph): This should really be defined as [policy] default_rule # policy_default_rule = admin_required As the comment suggest, we should move the config option to the policy section. This will also impact oslo and we should ensure the old option is still supported for backwards compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1276017/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1276033] [NEW] Now we're depending on python-swiftclient=1.6
Public bug reported: Based on the patch https://github.com/openstack/glance/commit/ae568d7858edeee4d60e52778243dc406651d46d , now we're depending on python-swiftclient=1.6 since the parameter 'headers' was introduced in python-swiftclient 1.6 get_object(container, obj, resp_chunk_size=None, query_string=None, response_dict=None, headers=None) See the new change in Glance: https://github.com/openstack/glance/blob/master/glance/store/swift.py#L325 And the change in Swift client: https://github.com/openstack/python- swiftclient/commit/d34f12614820416aebe5e91eab9726b556d1f973 But now we're depending on version 1.5 ** Affects: glance Importance: High Assignee: Fei Long Wang (flwang) Status: Triaged ** Changed in: glance Status: New = Triaged ** Changed in: glance Importance: Undecided = High ** Changed in: glance Assignee: (unassigned) = Fei Long Wang (flwang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1276033 Title: Now we're depending on python-swiftclient=1.6 Status in OpenStack Image Registry and Delivery Service (Glance): Triaged Bug description: Based on the patch https://github.com/openstack/glance/commit/ae568d7858edeee4d60e52778243dc406651d46d , now we're depending on python-swiftclient=1.6 since the parameter 'headers' was introduced in python-swiftclient 1.6 get_object(container, obj, resp_chunk_size=None, query_string=None, response_dict=None, headers=None) See the new change in Glance: https://github.com/openstack/glance/blob/master/glance/store/swift.py#L325 And the change in Swift client: https://github.com/openstack/python- swiftclient/commit/d34f12614820416aebe5e91eab9726b556d1f973 But now we're depending on version 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1276033/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
