[Yahoo-eng-team] [Bug 1727950] Re: [vpnaas] UTs failed
** Changed in: neutron 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/1727950 Title: [vpnaas] UTs failed Status in neutron: Fix Released Bug description: Here is the link to gate failed: http://logs.openstack.org/99/502699/105/check/openstack-tox- py27/5bf6b9c/testr_results.html.gz Detail as below: ft1.1: neutron_vpnaas.tests.unit.extensions.test_vpn_endpoint_groups.VpnEndpointGroupsTestCase.test_create_vlan_endpoint_group_create_StringException: Traceback (most recent call last): File "neutron_vpnaas/tests/unit/extensions/test_vpn_endpoint_groups.py", line 53, in setUp use_quota=True) TypeError: _setUpExtension() got multiple values for keyword argument 'plural_mappings' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1727950/+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 1728495] [NEW] When the remote security group and the remote IP are configured at the same time, the remote IP rule is ignored.
Public bug reported: ①Only configure the remote IP flow table as follows: table=82, priority=70,ct_state=+est-rel-rpl,ip,reg5=0x38 actions=output:56 table=82, priority=70,ct_state=+new-est,ip,reg5=0x38 actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:56 ②Configure the remote security group and the remote IP flow table as follows: table=82, priority=70,ct_state=+new-est,ip,reg6=0xd,nw_src=10.10.10.13 actions=conjunction(7,1/2),conjunction(11,1/2) table=82, priority=70,ct_state=+est-rel-rpl,ip,reg6=0xd,nw_src=10.10.10.13 actions=conjunction(6,1/2),conjunction(10,1/2) table=82, priority=70,ct_state=+est-rel-rpl,ip,reg5=0x38 actions=conjunction(10,2/2) table=82, priority=70,ct_state=+new-est,ip,reg5=0x38 actions=conjunction(11,2/2) table=82, priority=70,conj_id=10,ct_state=+est-rel-rpl,ip,reg5=0x38 actions=output:56 table=82, priority=70,conj_id=11,ct_state=+new-est,ip,reg5=0x38 actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:56 The rules for remote IP are ignored! ** 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/1728495 Title: When the remote security group and the remote IP are configured at the same time, the remote IP rule is ignored. Status in neutron: New Bug description: ①Only configure the remote IP flow table as follows: table=82, priority=70,ct_state=+est-rel-rpl,ip,reg5=0x38 actions=output:56 table=82, priority=70,ct_state=+new-est,ip,reg5=0x38 actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:56 ②Configure the remote security group and the remote IP flow table as follows: table=82, priority=70,ct_state=+new-est,ip,reg6=0xd,nw_src=10.10.10.13 actions=conjunction(7,1/2),conjunction(11,1/2) table=82, priority=70,ct_state=+est-rel-rpl,ip,reg6=0xd,nw_src=10.10.10.13 actions=conjunction(6,1/2),conjunction(10,1/2) table=82, priority=70,ct_state=+est-rel-rpl,ip,reg5=0x38 actions=conjunction(10,2/2) table=82, priority=70,ct_state=+new-est,ip,reg5=0x38 actions=conjunction(11,2/2) table=82, priority=70,conj_id=10,ct_state=+est-rel-rpl,ip,reg5=0x38 actions=output:56 table=82, priority=70,conj_id=11,ct_state=+new-est,ip,reg5=0x38 actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:56 The rules for remote IP are ignored! To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1728495/+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 1713541] Re: Admin should be able to see if tenant was deleted
[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.] ** Changed in: horizon Status: Incomplete => Expired -- 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/1713541 Title: Admin should be able to see if tenant was deleted Status in OpenStack Dashboard (Horizon): Expired Bug description: Is somebody deletes tenant where instance or other resource was created, this tenant should be marked as deleted on admin pages To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1713541/+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 1728479] [NEW] some security-group rules will be covered.
Public bug reported: 1. create security-group anquanzu01, anquanzu02 2. create vm1 with anquanzu01, anquanzu02, create vm2 with anquanzu02. 3. vm1 can ping vm2 well, but vm2 can not ping vm1. anquanzu01, anquanzu02 are as follows: [root@172e18e211e96 ~]# neutron security-group-show anquanzu01 neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--++ | Field| Value | +--++ | created_at | 2017-10-19T04:14:01Z | | description | | | id | b089348a-f939-43f8-bdd2-d7b54376f640 | | name | anquanzu01 | | project_id | 2acab64182334292a9bf5f3cdd5b3428 | | revision_number | 6 | | security_group_rules | { | | | "remote_group_id": null, | | | "direction": "ingress", | | | "protocol": "icmp", | | | "description": "", | | | "tags": [], | | | "ethertype": "IPv4", | | | "remote_ip_prefix": "0.0.0.0/0", | | | "port_range_max": null, | | | "updated_at": "2017-10-19T04:26:01Z", | | | "security_group_id": "b089348a-f939-43f8-bdd2-d7b54376f640", | | | "port_range_min": null, | | | "revision_number": 0, | | | "tenant_id": "2acab64182334292a9bf5f3cdd5b3428", | | | "created_at": "2017-10-19T04:26:01Z", | | | "project_id": "2acab64182334292a9bf5f3cdd5b3428", | | | "id": "1b7a4a06-e762-487a-9776-0d9d781f537c" | | | } | | | { | | | "remote_group_id": null, | | | "direction": "egress", | | | "protocol": null, | | | "description": null, | | | "tags": [], | | | "ethertype": "IPv6", | | | "remote_ip_prefix": null, | | | "port_range_max": null, | | | "updated_at": "2017-10-19T04:14:01Z", | | | "security_group_id": "b089348a-f939-43f8-bdd2-d7b54376f640", | | | "port_range_min": null, | | | "revision_number": 0, | | | "tenant_id": "2acab64182334292a9bf5f3cdd5b3428", | | | "created_at": "2017-10-19T04:14:01Z", | | | "project_id": "2acab64182334292a9bf5f3cdd5b3428", | | | "id": "2e605e9b-9be1-4dd3-a86b-af7b95c476fb" | | | } | | | { | | | "remote_group_id": "b089348a-f939-43f8-bdd2-d7b54376f640",| | | "direction": "ingress", | | | "protocol": null,
[Yahoo-eng-team] [Bug 1728368] Re: oslo.serialization 2.21.2 breaks glance
** Also affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1728368 Title: oslo.serialization 2.21.2 breaks glance Status in Glance: New Status in oslo.serialization: New Bug description: glance unittests break with 2.21.2, work fine with 2.21.1: == FAIL: glance.tests.unit.v1.test_registry_api.TestRegistryAPI.test_update_all_image_members -- Traceback (most recent call last): File "glance/tests/unit/v1/test_registry_api.py", line 1629, in test_update_all_image_members content_type='json') File "glance/tests/utils.py", line 564, in get_api_response_ext self.assertEqual(res.status_int, http_resp) File "/data/dmueller/src/Cloud/glance/.tox/venv/lib/python2.7/site-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/data/dmueller/src/Cloud/glance/.tox/venv/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 200 != 204 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1728368/+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 1728430] [NEW] make NTP tests work in gentoo
Public bug reported: Sample error when running tox in gentoo: == ERROR: Ntp schema validation allows for an empty ntp: configuration. -- Traceback (most recent call last): File "/home/ckonstanski/jobs/talligent/projects/cloud-init/tests/unittests/test_handler/test_handler_ntp .py", line 305, in test_ntp_handler_schema_validation_allows_empty_ntp_config with open(ntp_conf) as stream: IOError: [Errno 2] No such file or directory: '/tmp/ci-TestNtp.RXKT5o/ntp.conf' There are several errors but they all look similar. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1728430 Title: make NTP tests work in gentoo Status in cloud-init: New Bug description: Sample error when running tox in gentoo: == ERROR: Ntp schema validation allows for an empty ntp: configuration. -- Traceback (most recent call last): File "/home/ckonstanski/jobs/talligent/projects/cloud-init/tests/unittests/test_handler/test_handler_ntp .py", line 305, in test_ntp_handler_schema_validation_allows_empty_ntp_config with open(ntp_conf) as stream: IOError: [Errno 2] No such file or directory: '/tmp/ci-TestNtp.RXKT5o/ntp.conf' There are several errors but they all look similar. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1728430/+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 1728358] [NEW] Radware LBaaS v2 driver - support easy duplication
Public bug reported: This is actually an enhancement of the driver. Since no flavoring mechanism exists in neutron-lbaas and there is a need to use a driver with different configurations for different LBs, Radware LBaaS v2 driver should support easy driver duplication. The aim is to give user a possibility to inherit the original driver with a minimal code amount, so the new driver may be used with its own configuration which is different from the configuration of original driver. ** Affects: neutron Importance: Undecided Assignee: Evgeny Fedoruk (evgenyf) Status: New ** Tags: lbaas ** Changed in: neutron Assignee: (unassigned) => Evgeny Fedoruk (evgenyf) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1728358 Title: Radware LBaaS v2 driver - support easy duplication Status in neutron: New Bug description: This is actually an enhancement of the driver. Since no flavoring mechanism exists in neutron-lbaas and there is a need to use a driver with different configurations for different LBs, Radware LBaaS v2 driver should support easy driver duplication. The aim is to give user a possibility to inherit the original driver with a minimal code amount, so the new driver may be used with its own configuration which is different from the configuration of original driver. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1728358/+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