[Yahoo-eng-team] [Bug 1782001] Re: Install and configure for Ubuntu in Neutron
seems like brian and I commented at same time :) thanks brian for confirmation. ** Changed in: neutron Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1782001 Title: Install and configure for Ubuntu in Neutron Status in neutron: Invalid Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: __ this document have fault in nova.conf, neutron.conf auth_url = http://controller:35357 <--- is wrong. because all the keystone endpoints are http://controller:5000. (admin, public, internal) queen version install guide instructs that. but other version install guide instructs, internal = http://controller:35357 others = http://controller:5000 and OS_AUTH_URL=http://controller:35357/v3 I don't know what those do. but I know they are wrong I had an error when I made instance "Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures" but now that is solved by converting 35357 to 5000 in .conf files please make documents consistently --- Release: 12.0.4.dev37 on 2018-07-13 03:07 SHA: f58fa5c0217fa30e927456b95b9153b33fdd00c5 Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/install-ubuntu.rst URL: https://docs.openstack.org/neutron/queens/install/install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1782001/+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 1797663] [NEW] refactor def _get_dvr_sync_data from neutron/db/l3_dvr_db.py
Public bug reported: The function def _get_dvr_sync_data in neutron/db/l3_dvr_db.py is fetching and processing routers data and since its called upon for each dvr ha router type on update, its becomes very hard to pin point issues in such a massive method, so I propose breaking it into two methods. def _get_dvr_sync_data and _process_dvr_sync_data. will make debugging in future easy. ** 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/1797663 Title: refactor def _get_dvr_sync_data from neutron/db/l3_dvr_db.py Status in neutron: New Bug description: The function def _get_dvr_sync_data in neutron/db/l3_dvr_db.py is fetching and processing routers data and since its called upon for each dvr ha router type on update, its becomes very hard to pin point issues in such a massive method, so I propose breaking it into two methods. def _get_dvr_sync_data and _process_dvr_sync_data. will make debugging in future easy. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1797663/+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 1817238] Re: Failed to replace security group tags
curl -g -i -X PUT
$url/v2.0/security-groups/0c77e37f-3297-44a1-b90a-42d1ea763a6a/tags -H
"Content-Type: application/json" -H "User-Agent: openstacksdk/0.24.0
keystoneauth1/3.11.2 python-requests/2.21.0 CPython/2.7.12" -H "X-Auth-Token:
$TOKEN" -d '{"tags": ["blue", "red"]}'
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 25
X-Openstack-Request-Id: req-e69fa7e4-bf68-4442-a296-f49ab45ae205
Date: Mon, 25 Feb 2019 23:51:53 GMT
{"tags": ["blue", "reopenstack security group list
+--+-++--+---+
| ID | Name| Description|
Project | Tags |
+--+-++--+---+
| 0c77e37f-3297-44a1-b90a-42d1ea763a6a | default | Default security group |
426d8edd2b6c4c88861294716c35630a | [u'blue', u'red'] |
| 82be6fff-2401-4f4d-b316-3eb38c8d238c | default | Default security group |
| []|
| 9bad5f75-b639-46dd-a4ca-64640cfe7530 | default | Default security group |
1441b3d81ceb488cac04938da591fc59 | []|
+--+-++--+---+
works of me please check your data passed or request,
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1817238
Title:
Failed to replace security group tags
Status in neutron:
Invalid
Bug description:
Branch: master
Environment: devstack
Error log: http://paste.openstack.org/show/745672/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1817238/+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 1818383] Re: neutron not allowing access to external network
I think you're missing an iptable masquerade rule ?
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1818383
Title:
neutron not allowing access to external network
Status in neutron:
Invalid
Bug description:
We did a 4 node bare metal OpenStack Queens install. After setting up
networking and adding eth0 to br-ex and restarting network service we
cannot ping from qrouter to external floating IP network. Below layout
of the 4 node setup and our ovs db info.
This was a fresh install using PackStack script modify to prep all
nodes except the storage node.
CentOS 7
OpenStack Queens release
static hostname: controller01
Icon name: computer
Machine ID: 0f62242dd7f04961b2fa64208526
Boot ID: 1bf746fe751f4e58902431573696f31e
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-957.5.1.el7.x86_64
Architecture: x86-64
node 1 controller/network
node 2 compute01
node 3 compute02
node 4 cinder storage
[root@controller01 neutron(keystone_admin)]# neutron-server --version
neutron-server 12.0.5
root@controller01 neutron(keystone_admin)]# ovs-vsctl show
96de914b-630f-4014-b738-e149ee385b15
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge "br-eth1"
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port "br-eth1"
Interface "br-eth1"
type: internal
Port "eth1"
Interface "eth1"
Port "phy-br-eth1"
Interface "phy-br-eth1"
type: patch
options: {peer="int-br-eth1"}
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port "int-br-eth1"
Interface "int-br-eth1"
type: patch
options: {peer="phy-br-eth1"}
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "tap5d460e96-f2"
tag: 1
Interface "tap5d460e96-f2"
type: internal
Port br-int
Interface br-int
type: internal
Port "qg-96178c89-7a"
tag: 1
Interface "qg-96178c89-7a"
type: internal
Port "qr-232080af-bb"
tag: 2
Interface "qr-232080af-bb"
type: internal
Port "tap31ad97cd-15"
tag: 2
Interface "tap31ad97cd-15"
type: internal
Bridge br-ex
Port "eth0"
Interface "eth0"
Port br-ex
Interface br-ex
type: internal
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
Port "vxlan-c0a8015c"
Interface "vxlan-c0a8015c"
type: vxlan
options: {df_default="true", in_key=flow,
local_ip="192.168.1.90", out_key=flow, remote_ip="192.168.1.92"}
Port "vxlan-c0a8015b"
Interface "vxlan-c0a8015b"
type: vxlan
options: {df_default="true", in_key=flow,
local_ip="192.168.1.90", out_key=flow, remote_ip="192.168.1.91"}
ovs_version: "2.9.0"
floating IP network = 192.168.30.0/24
moment interface network on all nodes = 192.168.1.0/24
tenant network = 10.10.1.0/24
[root@controller01 neutron(keystone_admin)]# ip netns exec
qrouter-c2d1460b-3585-4d37-a782-0ae4a713738b route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG0 00
qg-96178c89-7a
10.10.1.0 0.0.0.0 255.255.255.0 U 0 00
qr-232080af-bb
192.168.1.1 0.0.0.0 255.255.255.255 UH0 00
qg-96178c89-7a
192.168.30.00.0.0.0 255.255.255.0 U 0 00
qg-96178c89-7a
[root@controller01 neutron(keystone_admin)]# openstack server list
+--+-++--+--+-+
| ID | Name| Status | Networks
| Image| Flavor |
+--+-+-
[Yahoo-eng-team] [Bug 1747747] [NEW] Making Payload consistent for all the operations of an object
Public bug reported: I observed while implementing L3 flavor driver for OpenDaylight, the payload sent to all the callbacks in a driver is not consistent, which in some cases is an oslo versioned object and sometimes a dictionary, due to this driver always have to do tweaks and hacks for driver and test code. It would make more sense to have one type of payload passed for all the operations of an object, which will help achieving some stability and simplicity. ** 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/1747747 Title: Making Payload consistent for all the operations of an object Status in neutron: New Bug description: I observed while implementing L3 flavor driver for OpenDaylight, the payload sent to all the callbacks in a driver is not consistent, which in some cases is an oslo versioned object and sometimes a dictionary, due to this driver always have to do tweaks and hacks for driver and test code. It would make more sense to have one type of payload passed for all the operations of an object, which will help achieving some stability and simplicity. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1747747/+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 1769751] [NEW] flavor data ignored by router tests
Public bug reported: as neutron/tests/unit/extensions/test_l3.py is used networking-odl for functional tests, it ignores flavor data because flavor_id is not included in hardcoded argument list. suppose using aforementioned framework some try to create test routers with self.router(flavor_id=flavor_id) as router: some code it will discard the flavor, request will either fallback to driver in neutron or emits error response saying Flavor None not found. ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1769751 Title: flavor data ignored by router tests Status in neutron: In Progress Bug description: as neutron/tests/unit/extensions/test_l3.py is used networking-odl for functional tests, it ignores flavor data because flavor_id is not included in hardcoded argument list. suppose using aforementioned framework some try to create test routers with self.router(flavor_id=flavor_id) as router: some code it will discard the flavor, request will either fallback to driver in neutron or emits error response saying Flavor None not found. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1769751/+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 1778118] [NEW] missing transaction in driver_controller.py for l3 flavors
Public bug reported: All the operations related to router associations like add or delete etc were executed under transactions, there was a case 'get_provider_for_router' doing add_resource_association out of db transaction, luckily due to autocommit there were no issues. https://github.com/openstack/neutron/blob/master/neutron/services/l3_router/service_providers/driver_controller.py#L160 need to be in under transaction. ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1778118 Title: missing transaction in driver_controller.py for l3 flavors Status in neutron: In Progress Bug description: All the operations related to router associations like add or delete etc were executed under transactions, there was a case 'get_provider_for_router' doing add_resource_association out of db transaction, luckily due to autocommit there were no issues. https://github.com/openstack/neutron/blob/master/neutron/services/l3_router/service_providers/driver_controller.py#L160 need to be in under transaction. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1778118/+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 1782001] Re: Install and configure for Ubuntu in Neutron
can you point to specific sections in those docs you're talking about ? ** Changed in: neutron Status: Invalid => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1782001 Title: Install and configure for Ubuntu in Neutron Status in neutron: Incomplete Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: __ this document have fault in nova.conf, neutron.conf auth_url = http://controller:35357 <--- is wrong. because all the keystone endpoints are http://controller:5000. (admin, public, internal) queen version install guide instructs that. but other version install guide instructs, internal = http://controller:35357 others = http://controller:5000 and OS_AUTH_URL=http://controller:35357/v3 I don't know what those do. but I know they are wrong I had an error when I made instance "Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures" but now that is solved by converting 35357 to 5000 in .conf files please make documents consistently --- Release: 12.0.4.dev37 on 2018-07-13 03:07 SHA: f58fa5c0217fa30e927456b95b9153b33fdd00c5 Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/install-ubuntu.rst URL: https://docs.openstack.org/neutron/queens/install/install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1782001/+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 1698804] Re: Update to existing neutron network results in un-usable network
** 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/1698804
Title:
Update to existing neutron network results in un-usable network
Status in networking-odl:
Confirmed
Status in neutron:
New
Bug description:
Updating an existing Neutron Network with the OpenDaylight V2 Driver,
renders that Neutron Network un-usable inside OpenDaylight Controller.
This is because, when we update existing network the ML2 ODL-V2 Driver
removes the network-type and segment-information when the update-
network REST API is invoked towards the ODL controller. This results
in Neutron Northbound in the ODL controller leaving the network with
no provider-type and thus renders that network un-usable further for
any operations.
Steps for the problem:
neutron net-create ghi
neutron net-update ghi --description "bye"
Below is the Ocata V2 ML2 Driver logs when the incident occurred:
OCATA V2 DRIVER
2017-06-16 10:33:35.987 INFO networking_odl.journal.journal [^[[00;36m-]
^[[01;35mSyncing create network e2cbdd60-f6af-4c00-901c-cbb6047c4d44^[[00m
2017-06-16 10:33:35.988 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mSending METHOD (post) URL
(http://192.168.56.1:8080/controller/nb/v2/neutron/networks) JSON ({
"network": {
"name": "ghi",
"provider:physical_network": null,
"admin_state_up": true,
"tenant_id": "b77ab8e96b7f4593b0848c46e1f0894c",
"mtu": 1500,
"router:external": false,
"provider:network_type": "vxlan",
"port_security_enabled": true,
"shared": false,
"project_id": "b77ab8e96b7f4593b0848c46e1f0894c",
"id": "e2cbdd60-f6af-4c00-901c-cbb6047c4d44",
"provider:segmentation_id": 101
}
OST /v2.0/networks.json HTTP/1.1" 201 867 2.248803^[[00m
2017-06-16 10:33:36.033 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mGot response:
({^M
"network" : {^M
"id" : "e2cbdd60-f6af-4c00-901c-cbb6047c4d44",^M
"tenant_id" : "b77ab8e96b7f4593b0848c46e1f0894c",^M
"name" : "ghi",^M
"admin_state_up" : true,^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"provider:network_type" : "vxlan",^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"provider:network_type" : "vxlan",^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"provider:network_type" : "vxlan",^M
"provider:segmentation_id" : "101",^M
"mtu" : 1500^M
}^M
2017-06-16 10:35:39.274 INFO networking_odl.journal.journal [^[[00;36m-]
^[[01;35mSyncing update network e2cbdd60-f6af-4c00-901c-cbb6047c4d44^[[00m
2017-06-16 10:35:39.275 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mSending METHOD (put) URL
(http://192.168.56.1:8080/controller/nb/v2/neutron/networks/e2cbdd60-f6af-4c00-901c-cbb6047c4d44)
JSON ({
"network": {
"availability_zone_hints": [],
"availability_zones": [],
"name": "ghi",
"admin_state_up": true,
"port_security_enabled": true,
"created_at": "2017-06-16T05:03:34Z",
"tags": [],
"updated_at": "2017-06-16T05:05:34Z",
"ipv6_address_scope": null,
"router:external": false,
"revision_number": 4,
"ipv4_address_scope": null,
"vlan_transparent": null,
"shared": false,
"mtu": 1500,
"description": "bye"
}
})^[[00m ^[[00;33mfrom (pid=17074) request
/opt/stack/networking-odl/networking_odl/common/client.py:86^[[00m
2017-06-16 10:35:39.307 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mGot response:
({^M
"network" : {^M
"id" : "e2cbdd60-f6af-4c00-901c-cbb6047c4d44",^M
"tenant_id" : "b77ab8e96b7f4593b0848c46e1f0894c",^M
"name" : "ghi",^M
"admin_state_up" : true,^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"segments" : [ ]^M
}^M
})^[[00m ^[[00;33mfrom (pid=17074) _check_rensponse
/opt/stack/networking-odl/networking_odl/common/client.py:141^[[00m
Similar trials on Newton release with V2-Driver for ML2 works correctly. The
logs from Newton runs thus:
As you can see below, during the update-network REST API invocation to ODL
Controller, the ML2 V2 Driver supplies the provider-type attributes to ODL
Controller, thereby enabling ODL controller to retain that information in the
Neutron Network.
NEWTON V2 DRIVER
2017-06-19 18:19:31.310 ^[[00;32mDEBUG networking_odl.common.client
[^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mSending METHOD (post) URL
(http://192.168.56.1:8080/controller/nb/v2/neutron/networks) JSON ({
"network": {
"name": "xyz",
"provider:physical_network": null,
"admin_s
[Yahoo-eng-team] [Bug 1698804] Re: Update to existing neutron network results in un-usable network
** Changed in: networking-odl
Status: Confirmed => 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/1698804
Title:
Update to existing neutron network results in un-usable network
Status in networking-odl:
Fix Released
Status in neutron:
Fix Released
Bug description:
Updating an existing Neutron Network with the OpenDaylight V2 Driver,
renders that Neutron Network un-usable inside OpenDaylight Controller.
This is because, when we update existing network the ML2 ODL-V2 Driver
removes the network-type and segment-information when the update-
network REST API is invoked towards the ODL controller. This results
in Neutron Northbound in the ODL controller leaving the network with
no provider-type and thus renders that network un-usable further for
any operations.
Steps for the problem:
neutron net-create ghi
neutron net-update ghi --description "bye"
Below is the Ocata V2 ML2 Driver logs when the incident occurred:
OCATA V2 DRIVER
2017-06-16 10:33:35.987 INFO networking_odl.journal.journal [^[[00;36m-]
^[[01;35mSyncing create network e2cbdd60-f6af-4c00-901c-cbb6047c4d44^[[00m
2017-06-16 10:33:35.988 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mSending METHOD (post) URL
(http://192.168.56.1:8080/controller/nb/v2/neutron/networks) JSON ({
"network": {
"name": "ghi",
"provider:physical_network": null,
"admin_state_up": true,
"tenant_id": "b77ab8e96b7f4593b0848c46e1f0894c",
"mtu": 1500,
"router:external": false,
"provider:network_type": "vxlan",
"port_security_enabled": true,
"shared": false,
"project_id": "b77ab8e96b7f4593b0848c46e1f0894c",
"id": "e2cbdd60-f6af-4c00-901c-cbb6047c4d44",
"provider:segmentation_id": 101
}
OST /v2.0/networks.json HTTP/1.1" 201 867 2.248803^[[00m
2017-06-16 10:33:36.033 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mGot response:
({^M
"network" : {^M
"id" : "e2cbdd60-f6af-4c00-901c-cbb6047c4d44",^M
"tenant_id" : "b77ab8e96b7f4593b0848c46e1f0894c",^M
"name" : "ghi",^M
"admin_state_up" : true,^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"provider:network_type" : "vxlan",^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"provider:network_type" : "vxlan",^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"provider:network_type" : "vxlan",^M
"provider:segmentation_id" : "101",^M
"mtu" : 1500^M
}^M
2017-06-16 10:35:39.274 INFO networking_odl.journal.journal [^[[00;36m-]
^[[01;35mSyncing update network e2cbdd60-f6af-4c00-901c-cbb6047c4d44^[[00m
2017-06-16 10:35:39.275 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mSending METHOD (put) URL
(http://192.168.56.1:8080/controller/nb/v2/neutron/networks/e2cbdd60-f6af-4c00-901c-cbb6047c4d44)
JSON ({
"network": {
"availability_zone_hints": [],
"availability_zones": [],
"name": "ghi",
"admin_state_up": true,
"port_security_enabled": true,
"created_at": "2017-06-16T05:03:34Z",
"tags": [],
"updated_at": "2017-06-16T05:05:34Z",
"ipv6_address_scope": null,
"router:external": false,
"revision_number": 4,
"ipv4_address_scope": null,
"vlan_transparent": null,
"shared": false,
"mtu": 1500,
"description": "bye"
}
})^[[00m ^[[00;33mfrom (pid=17074) request
/opt/stack/networking-odl/networking_odl/common/client.py:86^[[00m
2017-06-16 10:35:39.307 DEBUG networking_odl.common.client [^[[00;36m-]
^[[01;35mGot response:
({^M
"network" : {^M
"id" : "e2cbdd60-f6af-4c00-901c-cbb6047c4d44",^M
"tenant_id" : "b77ab8e96b7f4593b0848c46e1f0894c",^M
"name" : "ghi",^M
"admin_state_up" : true,^M
"status" : "ACTIVE",^M
"shared" : false,^M
"router:external" : false,^M
"segments" : [ ]^M
}^M
})^[[00m ^[[00;33mfrom (pid=17074) _check_rensponse
/opt/stack/networking-odl/networking_odl/common/client.py:141^[[00m
Similar trials on Newton release with V2-Driver for ML2 works correctly. The
logs from Newton runs thus:
As you can see below, during the update-network REST API invocation to ODL
Controller, the ML2 V2 Driver supplies the provider-type attributes to ODL
Controller, thereby enabling ODL controller to retain that information in the
Neutron Network.
NEWTON V2 DRIVER
2017-06-19 18:19:31.310 ^[[00;32mDEBUG networking_odl.common.client
[^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mSending METHOD (post) URL
(http://192.168.56.1:8080/controller/nb/v2/neutron/networks) JSON ({
"network": {
"name": "xyz",
"provider:physical_network": null,
[Yahoo-eng-team] [Bug 1711165] Re: Error during full sync with QoS
** Changed in: networking-odl Status: New => 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/1711165 Title: Error during full sync with QoS Status in networking-odl: Fix Released Status in neutron: Fix Committed Bug description: Error when specifying qos extension driver and service plugin: 2017-08-15 17:47:41.859 64185 INFO neutron.wsgi [-] 192.168.24.3 "OPTIONS / HTTP/1.0" status: 200 len: 249 time: 0.0029640 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task [req-5a639c24-7563-4b14-9f42-7d151264fe84 - - - - -] Failed during periodic task operation full_sync.: TypeError: get_objects() argument after ** must be a mapping, not NoneType 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task Traceback (most recent call last): 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task File "/usr/lib/python2.7/site-packages/networking_odl/journal/periodic_task.py", line 61, in _execute_op 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task operation(context=context) 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task File "/usr/lib/python2.7/site-packages/networking_odl/journal/full_sync.py", line 84, in full_sync 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task collection_name) 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task File "/usr/lib/python2.7/site-packages/networking_odl/journal/full_sync.py", line 120, in _sync_resources 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task resources = obj_getter(context) 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task File "/usr/lib/python2.7/site-packages/neutron/db/db_base_plugin_common.py", line 62, in inner_filter 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task result = f(*args, **kwargs) 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task File "/usr/lib/python2.7/site-packages/neutron/db/db_base_plugin_common.py", line 48, in inner 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task result = f(*args, **kwargs) 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task File "/usr/lib/python2.7/site-packages/neutron/services/qos/qos_plugin.py", line 267, in get_policies 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task **filters) 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task TypeError: get_objects() argument after ** must be a mapping, not NoneType 2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task To manage notifications about this bug go to: https://bugs.launchpad.net/networking-odl/+bug/1711165/+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 1737266] [NEW] Feature fetch return key Error
Public bug reported: networkin-odl has implemented the feature fetch and since the path and key mappings are hard coded, can't be reused without formatting data, it looks for features key the response from neutron northbound, and if someone will try to fetch any other feature like qos rules etc, it will return key Error features not in that json. ** 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/1737266 Title: Feature fetch return key Error Status in neutron: New Bug description: networkin-odl has implemented the feature fetch and since the path and key mappings are hard coded, can't be reused without formatting data, it looks for features key the response from neutron northbound, and if someone will try to fetch any other feature like qos rules etc, it will return key Error features not in that json. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1737266/+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 1742802] [NEW] add notification for floatingip delete event
Public bug reported: As neutron now allows L3 Flavors, but when other backends use L3 flavors, the floating delete only commits db transaction therefore removing fip from neutron db but backend still have that fip as active because there's no notification for the subscribed precommit_delete event. ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1742802 Title: add notification for floatingip delete event Status in neutron: In Progress Bug description: As neutron now allows L3 Flavors, but when other backends use L3 flavors, the floating delete only commits db transaction therefore removing fip from neutron db but backend still have that fip as active because there's no notification for the subscribed precommit_delete event. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1742802/+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 1653780] [NEW] Cyclic import issue with use of common_types
Public bug reported: We have defined some custom types in neutron/object/common_types to better control and validate the input, but use of common_types in objects/quota.py will lead to cyclic import like this neutron.api.v2.base -> neutron.quota -> neutron.db.quota.api -> neutron.objects.quota -> neutron.objects.common_types -> neutron.extensions.dns -> neutron.extensions.l3 -> neutron.api.v2.resource_helper) (cyclic-import) this is required to break for quota_ovo patch https://review.openstack.org/#/c/338625/ ** 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/1653780 Title: Cyclic import issue with use of common_types Status in neutron: New Bug description: We have defined some custom types in neutron/object/common_types to better control and validate the input, but use of common_types in objects/quota.py will lead to cyclic import like this neutron.api.v2.base -> neutron.quota -> neutron.db.quota.api -> neutron.objects.quota -> neutron.objects.common_types -> neutron.extensions.dns -> neutron.extensions.l3 -> neutron.api.v2.resource_helper) (cyclic-import) this is required to break for quota_ovo patch https://review.openstack.org/#/c/338625/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1653780/+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 1627749] Re: qos driver api can have better error handling
For networking-odl we have change documentation to configure driver properly, ** Also affects: networking-odl 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/1627749 Title: qos driver api can have better error handling Status in networking-odl: New Status in neutron: Confirmed Bug description: the current qos (notification) driver api assumes driver methods are async and always success. however, it might not be the case for some of possible backends. eg. a controller based implementation, where a driver would make a rest api call to the backend. - currently one of drivers raises an exception, the rest of drivers are simply skipped. it might not be what an api user would expect. - whan driver calls end up with an error, the db changes should be reverted, or the resource should be marked "possibly not sync". To manage notifications about this bug go to: https://bugs.launchpad.net/networking-odl/+bug/1627749/+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 1658806] [NEW] Broken grenade jobs
Public bug reported:
grenade job are broken, which i believe because of packaging lib version
mismatch
from the logs
here is trace
2017-01-23 19:43:38.572 | Traceback (most recent call last):
2017-01-23 19:43:38.572 | File "", line 1, in
2017-01-23 19:43:38.572 | File "/tmp/pip-wKYqTO-build/setup.py", line 29,
in
2017-01-23 19:43:38.572 | pbr=True)
2017-01-23 19:43:38.572 | File "/usr/lib/python2.7/distutils/core.py",
line 111, in setup
2017-01-23 19:43:38.572 | _setup_distribution = dist = klass(attrs)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/setuptools/dist.py",
line 320, in __init__
2017-01-23 19:43:38.572 | _Distribution.__init__(self, attrs)
2017-01-23 19:43:38.572 | File "/usr/lib/python2.7/distutils/dist.py",
line 287, in __init__
2017-01-23 19:43:38.572 | self.finalize_options()
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/setuptools/dist.py",
line 386, in finalize_options
2017-01-23 19:43:38.572 | ep.require(installer=self.fetch_build_egg)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 2306, in require
2017-01-23 19:43:38.572 | items = working_set.resolve(reqs, env,
installer)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 853, in resolve
2017-01-23 19:43:38.572 | raise VersionConflict(dist,
req).with_context(dependent_req)
2017-01-23 19:43:38.572 | pkg_resources.VersionConflict: (packaging 16.7
(/opt/stack/old/requirements/.venv/lib/python2.7/site-packages),
Requirement.parse('packaging>=16.8'))
** Affects: neutron
Importance: Critical
Status: Confirmed
** Tags: gate-failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1658806
Title:
Broken grenade jobs
Status in neutron:
Confirmed
Bug description:
grenade job are broken, which i believe because of packaging lib version
mismatch
from the logs
here is trace
2017-01-23 19:43:38.572 | Traceback (most recent call last):
2017-01-23 19:43:38.572 | File "", line 1, in
2017-01-23 19:43:38.572 | File "/tmp/pip-wKYqTO-build/setup.py", line
29, in
2017-01-23 19:43:38.572 | pbr=True)
2017-01-23 19:43:38.572 | File "/usr/lib/python2.7/distutils/core.py",
line 111, in setup
2017-01-23 19:43:38.572 | _setup_distribution = dist = klass(attrs)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/setuptools/dist.py",
line 320, in __init__
2017-01-23 19:43:38.572 | _Distribution.__init__(self, attrs)
2017-01-23 19:43:38.572 | File "/usr/lib/python2.7/distutils/dist.py",
line 287, in __init__
2017-01-23 19:43:38.572 | self.finalize_options()
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/setuptools/dist.py",
line 386, in finalize_options
2017-01-23 19:43:38.572 | ep.require(installer=self.fetch_build_egg)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 2306, in require
2017-01-23 19:43:38.572 | items = working_set.resolve(reqs, env,
installer)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 853, in resolve
2017-01-23 19:43:38.572 | raise VersionConflict(dist,
req).with_context(dependent_req)
2017-01-23 19:43:38.572 | pkg_resources.VersionConflict: (packaging 16.7
(/opt/stack/old/requirements/.venv/lib/python2.7/site-packages),
Requirement.parse('packaging>=16.8'))
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1658806/+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 1658806] Re: Broken grenade jobs
since https://review.openstack.org/#/c/424323/ is released we can mark
it fixed, as I don't see the failure anymore
** Changed in: neutron
Status: Confirmed => 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/1658806
Title:
Broken grenade jobs
Status in neutron:
Fix Released
Bug description:
grenade job are broken, which i believe because of packaging lib version
mismatch
from the logs
here is trace
2017-01-23 19:43:38.572 | Traceback (most recent call last):
2017-01-23 19:43:38.572 | File "", line 1, in
2017-01-23 19:43:38.572 | File "/tmp/pip-wKYqTO-build/setup.py", line
29, in
2017-01-23 19:43:38.572 | pbr=True)
2017-01-23 19:43:38.572 | File "/usr/lib/python2.7/distutils/core.py",
line 111, in setup
2017-01-23 19:43:38.572 | _setup_distribution = dist = klass(attrs)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/setuptools/dist.py",
line 320, in __init__
2017-01-23 19:43:38.572 | _Distribution.__init__(self, attrs)
2017-01-23 19:43:38.572 | File "/usr/lib/python2.7/distutils/dist.py",
line 287, in __init__
2017-01-23 19:43:38.572 | self.finalize_options()
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/setuptools/dist.py",
line 386, in finalize_options
2017-01-23 19:43:38.572 | ep.require(installer=self.fetch_build_egg)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 2306, in require
2017-01-23 19:43:38.572 | items = working_set.resolve(reqs, env,
installer)
2017-01-23 19:43:38.572 | File
"/opt/stack/old/requirements/.venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
line 853, in resolve
2017-01-23 19:43:38.572 | raise VersionConflict(dist,
req).with_context(dependent_req)
2017-01-23 19:43:38.572 | pkg_resources.VersionConflict: (packaging 16.7
(/opt/stack/old/requirements/.venv/lib/python2.7/site-packages),
Requirement.parse('packaging>=16.8'))
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1658806/+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 1672921] [NEW] Functional gate job seems broken
Public bug reported: gate-neutron-dsvm-functional-ubuntu-xenial seems to be failing even though tests are being passed. 1. http://logs.openstack.org/53/319353/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/b36e01e/ 2. http://logs.openstack.org/25/338625/33/check/gate-neutron-dsvm-functional-ubuntu-xenial/fc680a7/ ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure ** Tags added: gate-failure -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1672921 Title: Functional gate job seems broken Status in neutron: New Bug description: gate-neutron-dsvm-functional-ubuntu-xenial seems to be failing even though tests are being passed. 1. http://logs.openstack.org/53/319353/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/b36e01e/ 2. http://logs.openstack.org/25/338625/33/check/gate-neutron-dsvm-functional-ubuntu-xenial/fc680a7/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1672921/+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 1674443] [NEW] gate-grenade-dsvm-neutron-linuxbridge-multinode fails on smoke test sometimes
Public bug reported: failure rate for gate-grenade-dsvm-neutron-linuxbridge-multinode is increasing, from logs It looks like it fails mostly on executing smoke tests, there could be range of reasons for it failing, corrupted data plane, timeout for instance build etc. one of my observation is it fails when it runs of rax-node cloud. one other thing I've noticed it runs smoke tests with concurrency=4. ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure upgrades ** Tags added: gate-failure ** Tags added: upgrades -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1674443 Title: gate-grenade-dsvm-neutron-linuxbridge-multinode fails on smoke test sometimes Status in neutron: New Bug description: failure rate for gate-grenade-dsvm-neutron-linuxbridge-multinode is increasing, from logs It looks like it fails mostly on executing smoke tests, there could be range of reasons for it failing, corrupted data plane, timeout for instance build etc. one of my observation is it fails when it runs of rax-node cloud. one other thing I've noticed it runs smoke tests with concurrency=4. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1674443/+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 1675135] [NEW] network update is sending stale data in context to mechanism driver
Public bug reported: when qos_policy is detached from network, the context still sends the stale network data to mechanism_driver which is resulting in policy not being getting dettached from network on the backend side ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1675135 Title: network update is sending stale data in context to mechanism driver Status in neutron: In Progress Bug description: when qos_policy is detached from network, the context still sends the stale network data to mechanism_driver which is resulting in policy not being getting dettached from network on the backend side To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1675135/+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 1597913] Re: refactor model definitions
** Changed in: neutron Status: In Progress => Fix Released ** Changed in: neutron Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1597913 Title: refactor model definitions Status in neutron: Fix Committed Bug description: with Oslo versioned object integration there might be lot of re factors required to avoid cyclic imports. which make it must for every resource to move model definition out of file which has Dbmixins in that. Instead of just creating a separate folder for defining model of each resource like this https://github.com/openstack/neutron/tree/master/neutron/db/extra_dhcp_opt and https://github.com/openstack/neutron/tree/master/neutron/db/allowed_address_pairs we can do it two ways either move all model definitions to single file or divide them based on categories (not more than 3 or 5) and move model definitions to respective ones. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1597913/+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 1597552] [NEW] neutron quota-update returns a list
Public bug reported: When i do neutron quota-list it returns nothing and neutron quota-update just returns the list of quota instead showing the option for updating actual neutron resource quotas. http://paste.openstack.org/show/524140/ ** Affects: python-neutronclient Importance: Undecided Status: New ** Project changed: neutron => python-neutronclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1597552 Title: neutron quota-update returns a list Status in python-neutronclient: New Bug description: When i do neutron quota-list it returns nothing and neutron quota-update just returns the list of quota instead showing the option for updating actual neutron resource quotas. http://paste.openstack.org/show/524140/ To manage notifications about this bug go to: https://bugs.launchpad.net/python-neutronclient/+bug/1597552/+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 1597913] [NEW] refactor model definitions
Public bug reported: with Oslo versioned object integration there might be lot of re factors required to avoid cyclic imports. which make it must for every resource to move model definition out of file which has Dbmixins in that. Instead of just creating a separate folder for defining model of each resource like this https://github.com/openstack/neutron/tree/master/neutron/db/extra_dhcp_opt and https://github.com/openstack/neutron/tree/master/neutron/db/allowed_address_pairs we can do it two ways either move all model definitions to single file or divide them based on categories (not more than 3 or 5) and move model definitions to respective ones. ** Affects: neutron Importance: Undecided Status: New ** Tags: rfe ** Tags added: rfe -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1597913 Title: refactor model definitions Status in neutron: New Bug description: with Oslo versioned object integration there might be lot of re factors required to avoid cyclic imports. which make it must for every resource to move model definition out of file which has Dbmixins in that. Instead of just creating a separate folder for defining model of each resource like this https://github.com/openstack/neutron/tree/master/neutron/db/extra_dhcp_opt and https://github.com/openstack/neutron/tree/master/neutron/db/allowed_address_pairs we can do it two ways either move all model definitions to single file or divide them based on categories (not more than 3 or 5) and move model definitions to respective ones. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1597913/+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 1616253] [NEW] QoS api need to reformat qos_policy_data
Public bug reported:
neutron api pass qos data to notification,
which is qos_policy object
qos_policy like QosPolicy(description='',id=58c5f284-bc0d-420d-9aac-
69b3e7cc6e0c,name='testpolicy-0',rules=[QosRule(403c3298-d51a-
41d3-99f2-bd5cbc698448),QosRule(5c157ba8-0168-4ca9-abbf-
93a0e7483f48)],shared=False,tenant_id='1cbe81ac17ed4703988cd390d4f0dc39')
{'description': u'', 'rules': [{'max_kbps': 100, 'type':
'bandwidth_limit', 'id': '403c3298-d51a-41d3-99f2-bd5cbc698448',
'max_burst_kbps': 0, 'qos_policy_id': '58c5f284-bc0d-420d-9aac-
69b3e7cc6e0c'}, {'dscp_mark': 14, 'type': 'dscp_marking', 'id':
'5c157ba8-0168-4ca9-abbf-93a0e7483f48', 'qos_policy_id': '58c5f284-bc0d-
420d-9aac-69b3e7cc6e0c'}], 'tenant_id':
u'1cbe81ac17ed4703988cd390d4f0dc39', 'shared': False, 'id': '58c5f284
-bc0d-420d-9aac-69b3e7cc6e0c', 'name': u'testpolicy-0'}
Since we can attach only one rule of each type, this format is little
confusing,
having rules key in dict can be mistaken as supporting multiple rules by
policy.
so relevant format would be
{'description': '',
'bandwidth-limit-rule': {}
'dscp-marking-rule': {}
'policy-id' : ''
'project-id': ''
}
and other minor thing, same qos-policy-id can be seen thrice in same
data, we have to specify policy while creating rule of any type, so it
would make sense to pass qos-policy-id just once.
** 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/1616253
Title:
QoS api need to reformat qos_policy_data
Status in neutron:
New
Bug description:
neutron api pass qos data to notification,
which is qos_policy object
qos_policy like QosPolicy(description='',id=58c5f284-bc0d-420d-9aac-
69b3e7cc6e0c,name='testpolicy-0',rules=[QosRule(403c3298-d51a-
41d3-99f2-bd5cbc698448),QosRule(5c157ba8-0168-4ca9-abbf-
93a0e7483f48)],shared=False,tenant_id='1cbe81ac17ed4703988cd390d4f0dc39')
{'description': u'', 'rules': [{'max_kbps': 100, 'type':
'bandwidth_limit', 'id': '403c3298-d51a-41d3-99f2-bd5cbc698448',
'max_burst_kbps': 0, 'qos_policy_id': '58c5f284-bc0d-420d-9aac-
69b3e7cc6e0c'}, {'dscp_mark': 14, 'type': 'dscp_marking', 'id':
'5c157ba8-0168-4ca9-abbf-93a0e7483f48', 'qos_policy_id': '58c5f284
-bc0d-420d-9aac-69b3e7cc6e0c'}], 'tenant_id':
u'1cbe81ac17ed4703988cd390d4f0dc39', 'shared': False, 'id': '58c5f284
-bc0d-420d-9aac-69b3e7cc6e0c', 'name': u'testpolicy-0'}
Since we can attach only one rule of each type, this format is little
confusing,
having rules key in dict can be mistaken as supporting multiple rules by
policy.
so relevant format would be
{'description': '',
'bandwidth-limit-rule': {}
'dscp-marking-rule': {}
'policy-id' : ''
'project-id': ''
}
and other minor thing, same qos-policy-id can be seen thrice in same
data, we have to specify policy while creating rule of any type, so it
would make sense to pass qos-policy-id just once.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616253/+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 1616253] Re: QoS api need to reformat qos_policy_data
I had this ticket to have a discussion with qos folks to consider reformating
the data qos extension pass to notification drivers.
this ticket can be closed or marked duplicated as similar issue is reported here
https://bugs.launchpad.net/neutron/+bug/1614728
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1616253
Title:
QoS api need to reformat qos_policy_data
Status in neutron:
Invalid
Bug description:
neutron api pass qos data to notification,
which is qos_policy object
qos_policy like QosPolicy(description='',id=58c5f284-bc0d-420d-9aac-
69b3e7cc6e0c,name='testpolicy-0',rules=[QosRule(403c3298-d51a-
41d3-99f2-bd5cbc698448),QosRule(5c157ba8-0168-4ca9-abbf-
93a0e7483f48)],shared=False,tenant_id='1cbe81ac17ed4703988cd390d4f0dc39')
{'description': u'', 'rules': [{'max_kbps': 100, 'type':
'bandwidth_limit', 'id': '403c3298-d51a-41d3-99f2-bd5cbc698448',
'max_burst_kbps': 0, 'qos_policy_id': '58c5f284-bc0d-420d-9aac-
69b3e7cc6e0c'}, {'dscp_mark': 14, 'type': 'dscp_marking', 'id':
'5c157ba8-0168-4ca9-abbf-93a0e7483f48', 'qos_policy_id': '58c5f284
-bc0d-420d-9aac-69b3e7cc6e0c'}], 'tenant_id':
u'1cbe81ac17ed4703988cd390d4f0dc39', 'shared': False, 'id': '58c5f284
-bc0d-420d-9aac-69b3e7cc6e0c', 'name': u'testpolicy-0'}
Since we can attach only one rule of each type, this format is little
confusing,
having rules key in dict can be mistaken as supporting multiple rules by
policy.
so relevant format would be
{'description': '',
'bandwidth-limit-rule': {}
'dscp-marking-rule': {}
'policy-id' : ''
'project-id': ''
}
and other minor thing, same qos-policy-id can be seen thrice in same
data, we have to specify policy while creating rule of any type, so it
would make sense to pass qos-policy-id just once.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616253/+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 1564120] [NEW] horizon gave up when i spun 1000 vms
Public bug reported: when i spun 1000 vms horizon showed me error and gave up and not accessible but when i checked through cli all vm's were active. I have 3 node control 3 network and 54 computes . every component extracted from master branch attached logs http://paste.openstack.org/show/492509/ ** 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/1564120 Title: horizon gave up when i spun 1000 vms Status in OpenStack Dashboard (Horizon): New Bug description: when i spun 1000 vms horizon showed me error and gave up and not accessible but when i checked through cli all vm's were active. I have 3 node control 3 network and 54 computes . every component extracted from master branch attached logs http://paste.openstack.org/show/492509/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1564120/+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 1565105] Re: while spining vms on large scale some vms get multiple ips and multiple ports get created
** 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/1565105 Title: while spining vms on large scale some vms get multiple ips and multiple ports get created Status in kolla: New Status in neutron: New Bug description: attached logs from neutron_server not getting any error logs in rabbit mq http://paste.openstack.org/show/492785/ To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1565105/+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 1568202] [NEW] linux bridge agent gets out of sync with plugin
Public bug reported: I am using ml2 plugin with linux bridge which 3 control 3 network and 51 compute nodes. while spinning 500 to 1000 vms sometimes the success rate of getting vms active is 60% 2 out of 6 time 500 or 1000 vms were getting active when being spun. logs here http://paste.openstack.org/show/493553/ ** Affects: kolla Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Status: New ** 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/1568202 Title: linux bridge agent gets out of sync with plugin Status in kolla: New Status in neutron: New Bug description: I am using ml2 plugin with linux bridge which 3 control 3 network and 51 compute nodes. while spinning 500 to 1000 vms sometimes the success rate of getting vms active is 60% 2 out of 6 time 500 or 1000 vms were getting active when being spun. logs here http://paste.openstack.org/show/493553/ To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1568202/+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 1569107] [NEW] tests should be enforced for new alembic scripts
Public bug reported: As new framework for adding data migration testing is added in neutron that does shcema changes should be enforced to write revision test. ** 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/1569107 Title: tests should be enforced for new alembic scripts Status in neutron: New Bug description: As new framework for adding data migration testing is added in neutron that does shcema changes should be enforced to write revision test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1569107/+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 1538369] [NEW] re factor add_router_interface in l3_dvr_db.py
Public bug reported: lot of code is repeated in add_router_interface in l3_db.py and l3_dvr_db.py It would be nice to re factor the code and have one common func _add_router_interface which should be called while add_router_interface in l3_db.py and l3_dvr_db.py ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: New ** Changed in: neutron Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1538369 Title: re factor add_router_interface in l3_dvr_db.py Status in neutron: New Bug description: lot of code is repeated in add_router_interface in l3_db.py and l3_dvr_db.py It would be nice to re factor the code and have one common func _add_router_interface which should be called while add_router_interface in l3_db.py and l3_dvr_db.py To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1538369/+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 1551907] Re: Add API extension for reporting IP availability usage statistics
** Also affects: horizon 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/1551907 Title: Add API extension for reporting IP availability usage statistics Status in OpenStack Dashboard (Horizon): New Status in neutron: Invalid Status in openstack-api-site: New Status in openstack-manuals: New Bug description: https://review.openstack.org/212955 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 2f741ca5f9545c388270ddab774e9e030b006d8a Author: Mike Dorman Date: Thu Aug 13 21:24:58 2015 -0600 Add API extension for reporting IP availability usage statistics Implements an API extension for reporting availibility of IP addresses on Neutron networks/subnets based on the blueprint proposed at https://review.openstack.org/#/c/180803/ This provides an easy way for operators to count the number of used and total IP addresses on any or all networks and/or subnets. Co-Authored-By: David Bingham Co-Authored-By: Craig Jellick APIImpact DocImpact: As a new API, will need all new docs. See devref for details. Implements: blueprint network-ip-usage-api Closes-Bug: 1457986 Change-Id: I81406054d46b2c0e0ffcd56e898e329f943ba46f To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1551907/+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 1519915] Re: Releasenotes wrongly written
** 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/1519915 Title: Releasenotes wrongly written Status in neutron: Fix Released Bug description: Reno puts prelude and issues etc in separate sections. So, each item needs to be written in such a way that it can be read without the rest of the node. Have a look at http://git.openstack.org/cgit/openstack/neutron/tree/releasenotes/notes/performance-considerations-a76dd11d35f1df6a.yaml?h=stable/liberty The prelude is in a complete different part of the text than the rest, see http://docs.openstack.org/releasenotes/neutron/liberty.html Similar problems in ipv6-prefix-delegation-a2a342e5e34534c7.yaml, neutron-rbac-516b499743b57d1f.yaml, qos-api-fde017418657d56a.yaml also in ovs-agent-6137f5f82e10135c.yaml I would merge the two items together. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1519915/+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 1503595] Re: Firewall remain in active state even after deleting router associated with firewall
i don't see this issue with devstack single node its updating status
properly.
I think its resolved I wanted to mark this invalid but seems like only
supervisor can do that.
either you need to provide more info which branch, how many nodes are
you using. or that is fixed or invalid
** Changed in: neutron
Status: Confirmed => 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/1503595
Title:
Firewall remain in active state even after deleting router associated
with firewall
Status in neutron:
Incomplete
Bug description:
Steps to Reproduce:
==
1. Create a network,subnet,router and add router interface
2. Create firewall rule
3. Create firewall Policy with the above firewall rule
4. Create firewall with above policy
And make above route set to the firewall.
5. Then delete the router attached to the firewall and check the
status of the firewall
Issue :
Firewall remain in ACTIVE state even though router id field is blank while
getting the details of the firewall
{code}
stack@stevens-creek:~/firewall$ neutron firewall-list
+--+-+--+
| id | name| firewall_policy_id
|
+--+-+--+
| 71746ed4-4e12-48c6-8db5-31543276058e | user-fw |
320f68ea-4947-484d-af32-5ead4f368348 |
+--+-+--+
stack@stevens-creek:~/firewall$ neutron firewall-show user-fw
++--+
| Field | Value|
++--+
| admin_state_up | True |
| description| |
| firewall_policy_id | 320f68ea-4947-484d-af32-5ead4f368348 |
| id | 71746ed4-4e12-48c6-8db5-31543276058e |
| name | user-fw |
| router_ids | |
| status | ACTIVE |
| tenant_id | 84dc1f66b8b34fb2a48e2dce7031f279 |
++--+
stack@stevens-creek:~/firewall$
{code}
Expected :
Firewall state should change to either pending or error state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1503595/+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 1505786] [NEW] As neutron accepts icpmv6 but on api its not documented in accepted values for api call in security group create
Public bug reported: http://developer.openstack.org/api-ref-networking-v2-ext.html In security group create icmpv6 is missing and and pools does not show Terminated_HTTPS and expected values. ** 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/1505786 Title: As neutron accepts icpmv6 but on api its not documented in accepted values for api call in security group create Status in neutron: New Bug description: http://developer.openstack.org/api-ref-networking-v2-ext.html In security group create icmpv6 is missing and and pools does not show Terminated_HTTPS and expected values. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1505786/+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 1505832] [NEW] when you use icpmv6 as protocol it should use IPV6 ethertype by default but it shows IPV4
Public bug reported: While creating security group if you use protocol icmpv6 without specifying ethertype by default it should be IPV6 but it shows IPv4 steps tp produce create a security group: neutron security-group-rule-create --protocol ICMPv6 2cc9d82e-b5f0-454f-964d-848f17c03819 in dashboard check the rule you added you will see ethertype ipv4 which should be IPv6 ** 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/1505832 Title: when you use icpmv6 as protocol it should use IPV6 ethertype by default but it shows IPV4 Status in neutron: New Bug description: While creating security group if you use protocol icmpv6 without specifying ethertype by default it should be IPV6 but it shows IPv4 steps tp produce create a security group: neutron security-group-rule-create --protocol ICMPv6 2cc9d82e-b5f0-454f-964d-848f17c03819 in dashboard check the rule you added you will see ethertype ipv4 which should be IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1505832/+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 1505833] [NEW] when you use icpmv6 as protocol it should use IPV6 ethertype by default but it shows IPV4
Public bug reported: While creating security group if you use protocol icmpv6 without specifying ethertype by default it should be IPV6 but it shows IPv4 steps tp produce create a security group: neutron security-group-rule-create --protocol ICMPv6 2cc9d82e-b5f0-454f-964d-848f17c03819 in dashboard check the rule you added you will see ethertype ipv4 which should be IPv6 ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: New ** Changed in: neutron Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1505833 Title: when you use icpmv6 as protocol it should use IPV6 ethertype by default but it shows IPV4 Status in neutron: New Bug description: While creating security group if you use protocol icmpv6 without specifying ethertype by default it should be IPV6 but it shows IPv4 steps tp produce create a security group: neutron security-group-rule-create --protocol ICMPv6 2cc9d82e-b5f0-454f-964d-848f17c03819 in dashboard check the rule you added you will see ethertype ipv4 which should be IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1505833/+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 1508106] [NEW] For wrong ethertype exception message is hard coded
Public bug reported:
if you give any wrong ethertype while creating security group rule.
it will always mention reason None in exception message
Invalid input for ethertype. Reason: 'None' is not in ['IPv4', 'IPv6'].
try
neutron security-group-rule-create --ethertype ip --protocol icmp
it will print
Invalid input for ethertype. Reason: 'None' is not in ['IPv4', 'IPv6'].
but actually it should be Invalid input for ethertype. Reason: 'ip' is
not in ['IPv4', 'IPv6'].
** Affects: neutron
Importance: Undecided
Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1508106
Title:
For wrong ethertype exception message is hard coded
Status in neutron:
New
Bug description:
if you give any wrong ethertype while creating security group rule.
it will always mention reason None in exception message
Invalid input for ethertype. Reason: 'None' is not in ['IPv4',
'IPv6'].
try
neutron security-group-rule-create --ethertype ip --protocol icmp
it will print
Invalid input for ethertype. Reason: 'None' is not in ['IPv4', 'IPv6'].
but actually it should be Invalid input for ethertype. Reason: 'ip' is
not in ['IPv4', 'IPv6'].
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1508106/+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 1507055] Re: LBaaS 2.0: Listener create with no tenant id test issue
seems like this bug has been fixed not able to reproduce it
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1507055
Title:
LBaaS 2.0: Listener create with no tenant id test issue
Status in neutron:
Invalid
Bug description:
Steps:
1. Pull down and run the following test code in Tempest:
https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/tests/tempest/v2/api/test_listeners_admin.py#L98
2. Examine logs for actual request/response.
Result:
The test test_create_listener_missing_tenant_id creates a tenant_id with
special characters, instead of leaving it empty.
Expected:
The test should pass in an empty tenant_id into the listener create call.
This is happening because the class variables are being reused for the next
test.Specifically self.create_listener_kwargs should be reinitialized prior
to the proceeding test method.
Log Snippet:
2015-10-15 23:12:27.397 | 2015-10-15 23:12:27.370 | Captured pythonlogging:
2015-10-15 23:12:27.399 | 2015-10-15 23:12:27.371 | ~~~
2015-10-15 23:12:27.400 | 2015-10-15 23:12:27.373 | 2015-10-15
23:12:19,307 3297 INFO [tempest_lib.common.rest_client] Request
(ListenersTestJSON:test_create_listener_missing_tenant_id): 201 POST
http://127.0.0.1:9696/v2.0/lbaas/listeners 0.274s
2015-10-15 23:12:27.401 | 2015-10-15 23:12:27.374 | 2015-10-15
23:12:19,307 3297 DEBUG[tempest_lib.common.rest_client] Request - Headers:
{'Content-Type': 'application/json', 'Accept': 'application/json',
'X-Auth-Token': ''}
2015-10-15 23:12:27.432 | 2015-10-15 23:12:27.375 | Body:
{"listener": {"protocol": "HTTP", "protocol_port": 8081, "loadbalancer_id":
"5109250c-e964-4c1b-80d4-c25996fba62f", "tenant_id": "&^%123"}}
2015-10-15 23:12:27.433 | 2015-10-15 23:12:27.376 | Response -
Headers: {'content-type': 'application/json; charset=UTF-8', 'connection':
'close', 'content-length': '358', 'x-openstack-request-id':
'req-abb60691-16f6-4c70-9260-21e8aa79ddfe', 'date': 'Thu, 15 Oct 2015 23:12:19
GMT', 'status': '201'}
2015-10-15 23:12:27.433 | 2015-10-15 23:12:27.378 | Body:
{"listener": {"protocol_port": 8081, "protocol": "HTTP", "description": "",
"default_tls_container_ref": null, "admin_state_up": true, "loadbalancers":
[{"id": "5109250c-e964-4c1b-80d4-c25996fba62f"}], "tenant_id": "&^%123",
"sni_container_refs": [], "connection_limit": -1, "default_pool_id": null,
"id": "c9a3a3f0-6c70-4e6d-b53c-268468a9641b", "name": ""}}
Logs:
http://logs.openstack.org/75/230875/12/gate/gate-neutron-lbaasv2-dsvm-listener/18155a8/console.html#_2015-10-15_23_12_27_433
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1507055/+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 1508688] [NEW] lbaasv2- Only uppercase string for protocol are accepted while creating listener
Public bug reported: while creating listener only upper case protocol value is accepted where as in neutron securitygroups both uppercase and lower case strings for protocol are accepted. try neutron lbaas-listener-create --loadbalancer --protocol http --protocol-port 80 You will see exception neutron lbaas-listener-create: error: argument --protocol: invalid choice: u'http' (choose from 'TCP', 'HTTP', 'HTTPS'│ , 'TERMINATED_HTTPS') ** 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/1508688 Title: lbaasv2- Only uppercase string for protocol are accepted while creating listener Status in neutron: New Bug description: while creating listener only upper case protocol value is accepted where as in neutron securitygroups both uppercase and lower case strings for protocol are accepted. try neutron lbaas-listener-create --loadbalancer --protocol http --protocol-port 80 You will see exception neutron lbaas-listener-create: error: argument --protocol: invalid choice: u'http' (choose from 'TCP', 'HTTP', 'HTTPS'│ , 'TERMINATED_HTTPS') To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1508688/+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 1508687] [NEW] lbaasv2- Only uppercase string for protocol are accepted while creating listener
Public bug reported: while creating listener only upper case protocol value is accepted where as in neutron securitygroups both uppercase and lower case strings for protocol are accepted. try neutron lbaas-listener-create --loadbalancer --protocol http --protocol-port 80 You will see exception neutron lbaas-listener-create: error: argument --protocol: invalid choice: u'http' (choose from 'TCP', 'HTTP', 'HTTPS'│ , 'TERMINATED_HTTPS') ** 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/1508687 Title: lbaasv2- Only uppercase string for protocol are accepted while creating listener Status in neutron: New Bug description: while creating listener only upper case protocol value is accepted where as in neutron securitygroups both uppercase and lower case strings for protocol are accepted. try neutron lbaas-listener-create --loadbalancer --protocol http --protocol-port 80 You will see exception neutron lbaas-listener-create: error: argument --protocol: invalid choice: u'http' (choose from 'TCP', 'HTTP', 'HTTPS'│ , 'TERMINATED_HTTPS') To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1508687/+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 1515345] [NEW] pep8-gate is broken
Public bug reported: I checked some pacthes and found pep8 gate is broken. saying maximum depth for recursion exceed check http://logs.openstack.org/01/244201/1/check/gate-neutron-lbaas-pep8/e4bdb39/console.html#_2015-11-11_17_35_49_227 and http://logs.openstack.org/80/244180/1/check/gate-neutron-lbaas- pep8/4f13512/console.html#_2015-11-11_16_52_40_857 ** 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/1515345 Title: pep8-gate is broken Status in neutron: New Bug description: I checked some pacthes and found pep8 gate is broken. saying maximum depth for recursion exceed check http://logs.openstack.org/01/244201/1/check/gate-neutron-lbaas-pep8/e4bdb39/console.html#_2015-11-11_17_35_49_227 and http://logs.openstack.org/80/244180/1/check/gate-neutron-lbaas- pep8/4f13512/console.html#_2015-11-11_16_52_40_857 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1515345/+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 1516064] [NEW] Correct the example in readme.md for neutron-lbaas/devstack
Public bug reported: Recently a patch was merged that will not start q-lbaasv2 if octavia driver is being used. https://review.openstack.org/#/c/239087 But in neutron-lbaas/devstack/readme.md the example used is # For LBaaS V2 ENABLED_SERVICES+=,q-lbaasv2 ENABLED_SERVICES+=,octavia,o-cw,o-hk,o-hm,o-api thats confusing for operators. that should be changed. ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: New ** Tags: lbaas ** Changed in: neutron Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia) ** Tags added: lbaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1516064 Title: Correct the example in readme.md for neutron-lbaas/devstack Status in neutron: New Bug description: Recently a patch was merged that will not start q-lbaasv2 if octavia driver is being used. https://review.openstack.org/#/c/239087 But in neutron-lbaas/devstack/readme.md the example used is # For LBaaS V2 ENABLED_SERVICES+=,q-lbaasv2 ENABLED_SERVICES+=,octavia,o-cw,o-hk,o-hm,o-api thats confusing for operators. that should be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516064/+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 1516296] [NEW] Use constants for protocol values in tests in load balancer comonents
Public bug reported: I see direct values for protocols are used while testing listener and pool. It would be good to use constants which are already defined. in functional and unit tests. I was trying to implement its case insensitivity but since protocol value is hardcoded in most tests so all the test were breaking. The changes will be easy if we use already defined constants. ** Affects: neutron Importance: Undecided Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) Status: New ** Tags: lbaas ** Changed in: neutron Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia) ** Tags added: lbaas ** Description changed: - I see direct values for protocols are used while testing listener and pool. + I see direct values for protocols are used while testing listener and pool. It would be good to use constants which are already defined. in functional and unit tests. - - I was trying to implement its case insensitivity but since protocol value is hardcoded - in most tests so all the test were breaking. + I was trying to implement its case insensitivity but since protocol value is hardcoded + in most tests so all the test were breaking. The changes will be easy if we use already defined constants. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1516296 Title: Use constants for protocol values in tests in load balancer comonents Status in neutron: New Bug description: I see direct values for protocols are used while testing listener and pool. It would be good to use constants which are already defined. in functional and unit tests. I was trying to implement its case insensitivity but since protocol value is hardcoded in most tests so all the test were breaking. The changes will be easy if we use already defined constants. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1516296/+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 1518443] [NEW] full stack test_ha_router failing
Public bug reported: For some reason test_ha_router is not able to schedule router to both nodes. neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router is failing on gate as well as locally I tried tox -e dsvm-fullstack neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router reason: logs link. http://paste.openstack.org/show/479625/ ** Affects: neutron Importance: Undecided Status: New ** Summary changed: - full stack test failing + full stack test_ha_router failing ** Description changed: - For some reason test neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router is failing on gate - as well as locally + For some reason test_ha_router is not able to schedule router to both nodes. neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router is failing on gate + as well as locally I tried tox -e dsvm-fullstack neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router reason: logs link. http://paste.openstack.org/show/479625/ -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1518443 Title: full stack test_ha_router failing Status in neutron: New Bug description: For some reason test_ha_router is not able to schedule router to both nodes. neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router is failing on gate as well as locally I tried tox -e dsvm-fullstack neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router reason: logs link. http://paste.openstack.org/show/479625/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1518443/+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 1521422] [NEW] glance image-create should not work without parameters
Public bug reported: when i do glance image-create it creates the empty image and shows a image without name on image-list It should not be created without specifying parameters like container and image path or is it like you can create empty one and later update it ? ** 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/1521422 Title: glance image-create should not work without parameters Status in Glance: New Bug description: when i do glance image-create it creates the empty image and shows a image without name on image- list It should not be created without specifying parameters like container and image path or is it like you can create empty one and later update it ? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521422/+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 1521423] [NEW] is-public = true should be removed from manual seems
Public bug reported: when i tried creating image using --is-public True I gave me following message unrecognized arguments: --is-public True ubuntu-14.04-server-cloudimg- amd64-disk1.img It should be removed from manuals http://docs.openstack.org/cli- reference/content/glanceclient_commands.html ** 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/1521423 Title: is-public = true should be removed from manual seems Status in Glance: New Bug description: when i tried creating image using --is-public True I gave me following message unrecognized arguments: --is-public True ubuntu-14.04-server-cloudimg- amd64-disk1.img It should be removed from manuals http://docs.openstack.org/cli- reference/content/glanceclient_commands.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521423/+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 1522494] [NEW] neutron tests are messed up
Public bug reported: Today i was resolving merge conflict for a patch and found tox test are breaking kind of failure I am seeing http://paste.openstack.org/show/480793/ ** 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/1522494 Title: neutron tests are messed up Status in neutron: New Bug description: Today i was resolving merge conflict for a patch and found tox test are breaking kind of failure I am seeing http://paste.openstack.org/show/480793/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1522494/+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 1522903] [NEW] neutron.conf is going in wrong directory
Public bug reported: There was patch to autogenerate core configuration I think neutron.conf which devstack expects in etc/neutron/neutron.conf is actually created in etc/oslo-config-generator/neutron.conf either that has to corrected on devstack or neutron. My devstack ends up in error 2015-12-04 16:17:26.128 | + cp /opt/stack/neutron/etc/neutron.conf /etc/neutron/neutron.conf 2015-12-04 16:17:26.129 | cp: cannot stat '/opt/stack/neutron/etc/neutron.conf': No such file or directory ** 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/1522903 Title: neutron.conf is going in wrong directory Status in neutron: New Bug description: There was patch to autogenerate core configuration I think neutron.conf which devstack expects in etc/neutron/neutron.conf is actually created in etc/oslo-config-generator/neutron.conf either that has to corrected on devstack or neutron. My devstack ends up in error 2015-12-04 16:17:26.128 | + cp /opt/stack/neutron/etc/neutron.conf /etc/neutron/neutron.conf 2015-12-04 16:17:26.129 | cp: cannot stat '/opt/stack/neutron/etc/neutron.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1522903/+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
