[Yahoo-eng-team] [Bug 1638178] [NEW] MagicSearch does not filter by localized options
Public bug reported: How to reproduce: 1. Set a different language than English (Tested with Spanish) 2. Go to Project->Compute->Images 3. Open filters and select a facet with options, e.g. "Status". 4. A menu opens with a set options (note: translated options). Type "activo" (spanish word for active). 5. See that no matches are found since "activo" is not a valid filter option in the API. 6. Try using "active" and now it works Showing the localized options might confuse the user as they may think is a valid option but it's not. However, I believe we should keep the options localized. ** Affects: horizon Importance: Undecided Status: New ** Tags: filter images magicsearch ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1638178/+attachment/4770408/+files/magicsearchoptions.png -- 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/1638178 Title: MagicSearch does not filter by localized options Status in OpenStack Dashboard (Horizon): New Bug description: How to reproduce: 1. Set a different language than English (Tested with Spanish) 2. Go to Project->Compute->Images 3. Open filters and select a facet with options, e.g. "Status". 4. A menu opens with a set options (note: translated options). Type "activo" (spanish word for active). 5. See that no matches are found since "activo" is not a valid filter option in the API. 6. Try using "active" and now it works Showing the localized options might confuse the user as they may think is a valid option but it's not. However, I believe we should keep the options localized. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1638178/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** No longer affects: heat -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in anvil: New Status in bifrost: Fix Released Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in dox: New Status in DragonFlow: New Status in Freezer: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-brocade: New Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in octavia: Fix Released Status in ooi: Fix Released Status in os-brick: Fix Released Status in os-client-config: Fix Released Status in oslo.messaging: Fix Released Status in python-barbicanclient: Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Released Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Quark: Money Reinvented: New Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Stackalytics: Fix Released Status in OpenStack Object Storage (swift): Invalid Status in taskflow: Fix Released Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in tuskar: Fix Released Status in watcher: Fix Released Status in zaqar: Fix Released Status in Zun: New Status in designate package in Ubuntu: Fix Released Status in python-tuskarclient package in Ubuntu: Fix Committed Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1638152] [NEW] vpn should support different auth algorithm for different driver
Public bug reported: Currently, vpnaas plugin limits the ipsec and ike auth algorithm to "sha1" and "sha256", if user add a new driver (for example, hardware vpn gateway), and the new driver supports more auth algorithm, such as "sha2-384", "sha2-512", it can not integrated with current vpnaas plugin. It is necessary to support different auth algorithm for different drivers. ** 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/1638152 Title: vpn should support different auth algorithm for different driver Status in neutron: New Bug description: Currently, vpnaas plugin limits the ipsec and ike auth algorithm to "sha1" and "sha256", if user add a new driver (for example, hardware vpn gateway), and the new driver supports more auth algorithm, such as "sha2-384", "sha2-512", it can not integrated with current vpnaas plugin. It is necessary to support different auth algorithm for different drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1638152/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: zun Importance: Undecided Status: New ** Changed in: zun Assignee: (unassigned) => HengHa (2001xxj) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in anvil: New Status in bifrost: Fix Released Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in dox: New Status in DragonFlow: New Status in Freezer: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-brocade: New Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in octavia: Fix Released Status in ooi: Fix Released Status in os-brick: Fix Released Status in os-client-config: Fix Released Status in oslo.messaging: Fix Released Status in python-barbicanclient: Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Released Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Quark: Money Reinvented: New Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Stackalytics: Fix Released Status in OpenStack Object Storage (swift): Invalid Status in taskflow: Fix Released Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in tuskar: Fix Released Status in watcher: Fix Released Status in zaqar: Fix Released Status in Zun: New Status in designate package in Ubuntu: Fix Released Status in python-tuskarclient package in Ubuntu: Fix Committed Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1633668] Re: Pecan: Tempest API test fails QosBandwidthLimitRuleTestJSON
Reviewed: https://review.openstack.org/387723 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c1b28a8d7377380464e7fc7ce36ab1406f12eaf1 Submitter: Jenkins Branch:master commit c1b28a8d7377380464e7fc7ce36ab1406f12eaf1 Author: Brandon LoganDate: Mon Oct 17 18:33:35 2016 -0500 Pecan: Fix internal server error on QoS rule PUT A patch [1] was made to the legacy wsgi code but was not also done for the pecan code. This patch does the same check. [1] Ia82ad84a3a07df4df8eaeaed6c47d31be9493cbd Closes-Bug: #1633668 Change-Id: I829a9fee79109e42a366d349afef3868265e9d94 ** Changed in: neutron Status: In Progress => 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/1633668 Title: Pecan: Tempest API test fails QosBandwidthLimitRuleTestJSON Status in neutron: Fix Released Bug description: neutron.tests.tempest.api.test_qos.QosBandwidthLimitRuleTestJSON.test_rule_update_forbidden_for_regular_tenants_own_policy Traceback (most recent call last): File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_qos.py", line 476, in test_rule_update_forbidden_for_regular_tenants_own_policy policy['id'], rule['id'], max_kbps=2, max_burst_kbps=4) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 485, in assertRaises self.assertThat(our_callable, matcher) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 496, in assertThat mismatch_error = self._matchHelper(matchee, matcher, message, verbose) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 547, in _matchHelper mismatch = matcher.match(matchee) File "/usr/local/lib/python2.7/dist-packages/testtools/matchers/_exception.py", line 108, in match mismatch = self.exception_matcher.match(exc_info) File "/usr/local/lib/python2.7/dist-packages/testtools/matchers/_higherorder.py", line 62, in match mismatch = matcher.match(matchee) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 475, in match reraise(*matchee) File "/usr/local/lib/python2.7/dist-packages/testtools/matchers/_exception.py", line 101, in match result = matchee() File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 1049, in __call__ return self._callable_object(*self._args, **self._kwargs) File "/opt/stack/new/neutron/neutron/tests/tempest/services/network/json/network_client.py", line 599, in update_bandwidth_limit_rule resp, body = self.put(uri, jsonutils.dumps(post_data)) File "tempest/lib/common/rest_client.py", line 340, in put return self.request('PUT', url, extra_headers, headers, body, chunked) File "tempest/lib/common/rest_client.py", line 665, in request resp, resp_body) File "tempest/lib/common/rest_client.py", line 829, in _error_checker message=message) tempest.lib.exceptions.ServerFault: Got server fault Details: Request Failed: internal server error while processing your request. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1633668/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1633664] Re: Pecan: Auto allocate topology tempestapi tests fail
Reviewed: https://review.openstack.org/387708 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9006726acbd6255263de7acae6bf6110a5aeed8e Submitter: Jenkins Branch:master commit 9006726acbd6255263de7acae6bf6110a5aeed8e Author: Brandon LoganDate: Mon Oct 17 18:03:00 2016 -0500 Pecan: Don't prefetch resource fields on DELETE The legacy wsgi does not prefetch resources and specify fields on DELETE. It does do this on PUTs though. However, the pecan wsgi policy hook was doing it for both PUT and DELETE. This also fixes a failure with the auto-allocated-topology tests. Change-Id: I9933c141f7d0481caade5a9484022fe090cf47f0 Closes-Bug: #1633664 ** Changed in: neutron Status: In Progress => 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/1633664 Title: Pecan: Auto allocate topology tempestapi tests fail Status in neutron: Fix Released Bug description: These tests currently fail: neutron.tests.tempest.api.test_auto_allocated_topology.TestAutoAllocatedTopology.test_delete_allocated_net_topology_as_tenant Traceback (most recent call last): File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_auto_allocated_topology.py", line 115, in test_delete_allocated_net_topology_as_tenant self.client.delete_auto_allocated_topology() File "/opt/stack/new/neutron/neutron/tests/tempest/services/network/json/network_client.py", line 794, in delete_auto_allocated_topology resp, body = self.delete(uri) File "tempest/lib/common/rest_client.py", line 307, in delete return self.request('DELETE', url, extra_headers, headers, body) File "tempest/lib/common/rest_client.py", line 665, in request resp, resp_body) File "tempest/lib/common/rest_client.py", line 768, in _error_checker raise exceptions.BadRequest(resp_body, resp=resp) tempest.lib.exceptions.BadRequest: Bad request Details: {u'type': u'BadRequest', u'detail': u'', u'message': u'Bad auto_allocate request: Unrecognized field.'} neutron.tests.tempest.api.test_auto_allocated_topology.TestAutoAllocatedTopology.test_get_allocated_net_topology_as_tenant Traceback (most recent call last): File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_auto_allocated_topology.py", line 85, in test_get_allocated_net_topology_as_tenant self.assertEqual((0, 0, 0), resources_before) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: (0, 0, 0) != (1, 2, 1) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1633664/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1604971] Re: RFE: keystone doctor should check for domain specific backends
Reviewed: https://review.openstack.org/361435 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fd6445ee0555cd26afd2f18adffda3c3c0379a42 Submitter: Jenkins Branch:master commit fd6445ee0555cd26afd2f18adffda3c3c0379a42 Author: GageDate: Fri Aug 26 14:26:14 2016 -0500 Doctor check for LDAP domain specific configs Added multiple checks for domain specific LDAP configurations using file-based configurations: - Set enabled & valid directory - Filenames are in the correct format - Parse values in each file Change-Id: I47375088635d7b6634e2c8683772dc4f2ad11a93 Closes-Bug: #1604971 ** Changed in: keystone Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1604971 Title: RFE: keystone doctor should check for domain specific backends Status in OpenStack Identity (keystone): Fix Released Bug description: keystone-manage doctor checks only the [ldap] values for the general keystone.conf, we should check for domain specific LDAP configs. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1604971/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1638130] [NEW] SLaaC or DHCPv6 stateless doesn't work on isolated Neutron networks
Public bug reported: On an isolated IPv6 network no router advertisements are sent, so the instances are unable to discover what prefix to use. To enabled instances to discover which prefixes are on-link router advertisements with a router lifetime of zero should be sent (from the DHCP namespace) https://tools.ietf.org/html/rfc4861#page-43. Dnsmasq seems to support this via --ra-param option: --ra-param=,[high|low],[[],] Set non-default values for router advertisements sent via an interface. The priority field for the router may be altered from the default of medium with eg --ra-param=eth0,high. The interval between router advertisements may be set (in seconds) with --ra-param=eth0,60. The lifetime of the route may be changed or set to zero, which allows a router to advertise prefixes but not a route via itself. --ra-parm=eth0,0,0 (A value of zero for the interval means the default value.) All three parameters may be set at once. --ra-param=low,60,1200 The interface field may include a wildcard. Alternatively radvd could be used within the DHCP namespace. Steps to reproduce: $ openstack network create isolated-ipv6 +---+--+ | Field | Value| +---+--+ | admin_state_up| UP | | availability_zone_hints | | | availability_zones| | | created_at| 2016-10-31T20:14:13Z | | description | | | headers | | | id| 7044aa9b-937f-4f7d-9073-00512f88a066 | | ipv4_address_scope| None | | ipv6_address_scope| None | | mtu | 1450 | | name | isolated-ipv6| | port_security_enabled | True | | project_id| 6d80770322b64b8ba57038788004e93e | | project_id| 6d80770322b64b8ba57038788004e93e | | provider:network_type | vxlan| | provider:physical_network | None | | provider:segmentation_id | 11 | | revision_number | 3| | router:external | Internal | | shared| False| | status| ACTIVE | | subnets | | | tags | [] | | updated_at| 2016-10-31T20:14:13Z | +---+--+ $ openstack subnet create --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac --network 7044aa9b-937f-4f7d-9073-00512f88a066 --subnet-range fddd:fd72:8298::/64 isolated-ipv6-subnet +---++ | Field | Value | +---++ | allocation_pools | fddd:fd72:8298::2-fddd:fd72:8298:0:::: | | cidr | fddd:fd72:8298::/64| | created_at| 2016-10-31T20:17:44Z | | description || | dns_nameservers || | enable_dhcp | True | | gateway_ip| fddd:fd72:8298::1 | | headers || | host_routes || | id| 96bf9b9f-736b-46c3-86f0-029c6d5f6e92 | | ip_version| 6 | | ipv6_address_mode | slaac | | ipv6_ra_mode | slaac | | name | isolated-ipv6-subnet | | network_id| 7044aa9b-937f-4f7d-9073-00512f88a066 | | project_id| 6d80770322b64b8ba57038788004e93e | | project_id| 6d80770322b64b8ba57038788004e93e | | revision_number | 2 | | service_types |
[Yahoo-eng-team] [Bug 1633254] Re: [RFE]Add tag extension to Neutron-Lbaas Resources
This was discussed at the summit, and the impetus for tags was to pass meta from the api layer to the drivers, which is explicitly against its listed use cases, because it leaks implementation details to end users. The alternative discussed was finishing the flavors framework, which has a notion of passing metadata to drivers, in an end user agnostic manner (very much vendor not agnostic for the operator, but they can configure their cloud however they want.) Closing after that discussion, please re-open if you have another use case in mind. ** Changed in: neutron Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1633254 Title: [RFE]Add tag extension to Neutron-Lbaas Resources Status in neutron: Won't Fix Bug description: [Use-cases] - Supporting tag functionality as part of LBaaSv2 Implement tag extension support for LBaaSv2 objects such as Listener, Pool and PoolMember objects. [Limitations] In the Mitaka release Neutron was introduced with the tag extension but unfortunately tags are limited to Neutron project. From the documentation and and comments in the implementation code it is clear that the intent is to extend tags to other Neutron modeled objects. [Enhancement] - Add tag support to LBaaSv2 Objects Extend the tag supported resources of Neutron to LBaaSv2 objects such as Listener, Pool and PoolMember. - Extend existing API Add the support for tags to the Neutron-Lbaas objects API. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1633254/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp