[Yahoo-eng-team] [Bug 1589427] [NEW] Import undefined attribute PROTO_NAME_IPV6_ICMP_LEGACY
Public bug reported:
In neutron/common/constants.py, it uses attribute
'PROTO_NAME_IPV6_ICMP_LEGACY' imported from neutron_lib.constants , like
this:
https://github.com/openstack/neutron/blob/master/neutron/common/constants.py#L61
```
IP_PROTOCOL_NAME_ALIASES = {lib_constants.PROTO_NAME_IPV6_ICMP_LEGACY:
lib_constants.PROTO_NAME_IPV6_ICMP}
```
but the attribute 'PROTO_NAME_IPV6_ICMP_LEGACY' is not defined in
neutron_lib.constants.
An AttributeError occured:
```
Traceback (most recent call last):
File "/usr/bin/neutron-ovs-cleanup", line 6, in
from neutron.cmd.ovs_cleanup import main
File "/opt/stack/neutron/neutron/cmd/ovs_cleanup.py", line 20, in
from neutron.agent.common import config as agent_config
File "/opt/stack/neutron/neutron/agent/common/config.py", line 21, in
from neutron.common import config
File "/opt/stack/neutron/neutron/common/config.py", line 33, in
from neutron.common import constants
File "/opt/stack/neutron/neutron/common/constants.py", line 62, in
lib_constants.PROTO_NAME_IPV6_ICMP}
AttributeError: 'module' object has no attribute 'PROTO_NAME_IPV6_ICMP_LEGACY'
```
** 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/1589427
Title:
Import undefined attribute PROTO_NAME_IPV6_ICMP_LEGACY
Status in neutron:
New
Bug description:
In neutron/common/constants.py, it uses attribute
'PROTO_NAME_IPV6_ICMP_LEGACY' imported from neutron_lib.constants ,
like this:
https://github.com/openstack/neutron/blob/master/neutron/common/constants.py#L61
```
IP_PROTOCOL_NAME_ALIASES = {lib_constants.PROTO_NAME_IPV6_ICMP_LEGACY:
lib_constants.PROTO_NAME_IPV6_ICMP}
```
but the attribute 'PROTO_NAME_IPV6_ICMP_LEGACY' is not defined in
neutron_lib.constants.
An AttributeError occured:
```
Traceback (most recent call last):
File "/usr/bin/neutron-ovs-cleanup", line 6, in
from neutron.cmd.ovs_cleanup import main
File "/opt/stack/neutron/neutron/cmd/ovs_cleanup.py", line 20, in
from neutron.agent.common import config as agent_config
File "/opt/stack/neutron/neutron/agent/common/config.py", line 21, in
from neutron.common import config
File "/opt/stack/neutron/neutron/common/config.py", line 33, in
from neutron.common import constants
File "/opt/stack/neutron/neutron/common/constants.py", line 62, in
lib_constants.PROTO_NAME_IPV6_ICMP}
AttributeError: 'module' object has no attribute 'PROTO_NAME_IPV6_ICMP_LEGACY'
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1589427/+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 1571448] [NEW] HA_DEFAULT_PRIORITY should be configurable
Public bug reported: Now, HA_DEFAULT_PRIORITY is set to 50 as hardcode, and it's not configurable. As below: https://github.com/openstack/neutron/blob/master/neutron/agent/linux/keepalived.py#L31 Thinking about the scenario that administrator may want to make one special network node trend to act as master, but current code base don't has this ability. ** Affects: neutron Importance: Undecided Assignee: yaowei (yaowei) Status: New ** Changed in: neutron Assignee: (unassigned) => yaowei (yaowei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1571448 Title: HA_DEFAULT_PRIORITY should be configurable Status in neutron: New Bug description: Now, HA_DEFAULT_PRIORITY is set to 50 as hardcode, and it's not configurable. As below: https://github.com/openstack/neutron/blob/master/neutron/agent/linux/keepalived.py#L31 Thinking about the scenario that administrator may want to make one special network node trend to act as master, but current code base don't has this ability. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1571448/+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 1554837] [NEW] port of network:router_interface exists even if the subnet updated to no-gateway
Public bug reported: reproduce steps: 1. create a subnet 2. connect to a router 3. update subnet --no-gateway 4. check port exists with device owner network:router_interface and fixed ip was the subnet gateway ip 5. check in router ns qr-xxx has ip address gateway ip this bug was found in master branch, but I think it also affects previous version. fix solutions: when update subnet --no-gateway: 1. check and router interface delete 2. delete gateway port 3. update dhcp configure ** Affects: neutron Importance: Undecided Assignee: yaowei (yaowei) Status: New ** Changed in: neutron Assignee: (unassigned) => yaowei (yaowei) ** Description changed: reproduce steps: 1. create a subnet 2. connect to a router 3. update subnet --no-gateway 4. check port exists with device owner network:router_interface and fixed ip was the subnet gateway ip 5. check in router ns qr-xxx has ip address gateway ip - this problem was found in master branch, but I think it also previous - version. + this bug was found in master branch, but I think it also affects + previous version. fix solutions: when update subnet --no-gateway: 1. check and router interface delete 2. delete gateway port 3. update dhcp configure -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1554837 Title: port of network:router_interface exists even if the subnet updated to no-gateway Status in neutron: New Bug description: reproduce steps: 1. create a subnet 2. connect to a router 3. update subnet --no-gateway 4. check port exists with device owner network:router_interface and fixed ip was the subnet gateway ip 5. check in router ns qr-xxx has ip address gateway ip this bug was found in master branch, but I think it also affects previous version. fix solutions: when update subnet --no-gateway: 1. check and router interface delete 2. delete gateway port 3. update dhcp configure To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1554837/+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 1554379] [NEW] lbaas agent_callbacks of get_loadbalancer error because of subnet extra parameters
File
"/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line
464, in send
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mretry=retry)
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m File
"/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line
455, in _send
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mraise result
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mTypeError: __init__() got an unexpected keyword argument
'description'
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mTraceback (most recent call last):
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m File
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142,
in _dispatch_and_reply
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mexecutor_callback))
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m File
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186,
in _dispatch
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mexecutor_callback)
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m File
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 129,
in _do_dispatch
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mresult = func(ctxt, **new_args)
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m File
"/opt/stack/neutron-lbaas/neutron_lbaas/drivers/common/agent_callbacks.py",
line 74, in get_loadbalancer
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00msubnet_dict))
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m File
"/opt/stack/neutron-lbaas/neutron_lbaas/services/loadbalancer/data_models.py",
line 183, in from_dict
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mreturn Subnet(**model_dict)
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00mTypeError: __init__() got an unexpected keyword argument
'description'
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
^[[01;31m2016-03-08 14:49:48.929 TRACE neutron_lbaas.agent.agent_manager
^[[01;35m^[[00m
** Affects: neutron
Importance: Undecided
Assignee: yaowei (yaowei)
Status: New
** Changed in: neutron
Assignee: (unassigned) => yaowei (yaowei)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1554379
Title:
lbaas agent_callbacks of get_loadbalancer error because of subnet
extra parameters
Status in neutron:
New
Bug description:
lbaas agent_callbacks of get_loadbalancer error because of subnet extra
parameters.
Too many extra parameters pass to Subnet.__init__().
https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/services/loadbalancer/data_models.py#L183
model_dict is:
{'description': u'', 'updated_at': '2016-03-07T13:42:29', 'ipv6_ra_mode':
None, 'allocation_pools':
[], 'host_routes': [], 'ipv6_address_mode': None, 'cidr':
u'10.0.1.0/24', 'id': u'80c886fa-1f7a-452c-8977-07504404ffe5', 'subnetpool_id':
None, 'name': u'net1_sub', 'enable_dhcp': True, 'network_id':
u'61e5c140-d68e-4801-8b41-d01eb25dfad1', 'tenant_id':
u'dc19598c3a8b4cc8bbd2b7d22163a9f5', 'created_at': '2016-03-07T13:42:29',
'dns_nameservers': [], 'gateway_ip': u'10.0.1.1', 'ip_version': 4, 'shared':
False}
q-server trace:
2016-03-08 14:49:48.920 ^[[01;31mERROR oslo_messaging.rpc.dispatcher
[^[[01;36mreq-9c8b7836-7f0d-415b-98bc-93e95619c7d1 ^[[00;36mNone None^[[01;31m]
^[[01;35m^[[01;31mException during message handling: __init__() got an
unexpected keyword argument 'description'^[[00m
^[[01;31m2016-03-08 14:49:48.920 TRACE oslo_messaging.rpc.dispatcher
^[[01;35m^[[00mTraceback (most recent call last):
^[[01;3
[Yahoo-eng-team] [Bug 1552614] [NEW] Add enable_dhcp filter in get_network_info rpc
Public bug reported: As code in https://github.com/openstack/neutron/blob/master/neutron/api/rpc/handlers/dhcp_rpc.py#L163 the rpc get_active_network called by dhcp-agent to fetch network info, and subnet which enable_dhcp = False is not needed. It would better add 'enable_dhcp=True' into filter and recheck in dhcp agent would not need. https://github.com/openstack/neutron/blob/master/neutron/agent/linux/dhcp.py#L344 ** Affects: neutron Importance: Undecided Assignee: yaowei (yaowei) Status: New ** Changed in: neutron Assignee: (unassigned) => yaowei (yaowei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1552614 Title: Add enable_dhcp filter in get_network_info rpc Status in neutron: New Bug description: As code in https://github.com/openstack/neutron/blob/master/neutron/api/rpc/handlers/dhcp_rpc.py#L163 the rpc get_active_network called by dhcp-agent to fetch network info, and subnet which enable_dhcp = False is not needed. It would better add 'enable_dhcp=True' into filter and recheck in dhcp agent would not need. https://github.com/openstack/neutron/blob/master/neutron/agent/linux/dhcp.py#L344 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1552614/+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 1541191] [NEW] Limit to create only one external network
Public bug reported: Since L3 agent support only one external network, https://github.com/openstack/neutron/blob/master/neutron/db/external_net_db.py#L149 But now, we can create any number of external network that will cause to raise TooManyExternalNetworks exception in agent rpc get_external_network_id(). We should modify create_network api to limit only one external_network could be create. ** Affects: neutron Importance: Undecided Assignee: yaowei (yaowei) Status: New ** Changed in: neutron Assignee: (unassigned) => yaowei (yaowei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1541191 Title: Limit to create only one external network Status in neutron: New Bug description: Since L3 agent support only one external network, https://github.com/openstack/neutron/blob/master/neutron/db/external_net_db.py#L149 But now, we can create any number of external network that will cause to raise TooManyExternalNetworks exception in agent rpc get_external_network_id(). We should modify create_network api to limit only one external_network could be create. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1541191/+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 1535285] [NEW] More log needed when dhcp agent sync_state
Public bug reported: Add more log when dhcp agent sync_state ** 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/1535285 Title: More log needed when dhcp agent sync_state Status in neutron: New Bug description: Add more log when dhcp agent sync_state To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1535285/+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 1534587] [NEW] increase default num_sync_threads of GreenPool to speed up dhcp sync_state
Public bug reported: dhcp-agent create a green thread for every network when sync_state. But default GreenPool threads num is 4. It can be increase to speed up sync_state process. Int my test environment, twice times faster when it increase to 16 with 1500+ networks ** Affects: neutron Importance: Undecided Assignee: yaowei (yaowei) Status: New ** Changed in: neutron Assignee: (unassigned) => yaowei (yaowei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1534587 Title: increase default num_sync_threads of GreenPool to speed up dhcp sync_state Status in neutron: New Bug description: dhcp-agent create a green thread for every network when sync_state. But default GreenPool threads num is 4. It can be increase to speed up sync_state process. Int my test environment, twice times faster when it increase to 16 with 1500+ networks To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1534587/+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 1476079] Re: Show and update method of pool's network and subnet add to LBaaS api v2
** 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/1476079 Title: Show and update method of pool's network and subnet add to LBaaS api v2 Status in neutron: Invalid Bug description: Pool is defined in loadbalancerv2.py, it has attributes network_id and subnet_id,but we can't see all these attributes by `neutron lbaas- pool-show` and modify these attributes by `neutron lbaas-pool-update`. I suggest to add these methods to lbaas api v2. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1476079/+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 1499224] [NEW] lb not deployable but still add into instance_mapping when lbaas agent restart
Public bug reported: lb not deployable but still add into instance_mapping when lbaas agent restart and reload loadbalancer. ** Affects: neutron Importance: Undecided Assignee: yaowei (yaowei) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => yaowei (yaowei) ** Changed in: neutron Status: New => 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/1499224 Title: lb not deployable but still add into instance_mapping when lbaas agent restart Status in neutron: In Progress Bug description: lb not deployable but still add into instance_mapping when lbaas agent restart and reload loadbalancer. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1499224/+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
