[Yahoo-eng-team] [Bug 1652157] [NEW] privsep configuration is invalid
Public bug reported: http://logs.openstack.org/76/414176/6/check/gate-devstack-dsvm-py35 -updown-ubuntu-xenial- nv/e100b7f/logs/devstacklog.txt.gz#_2016-12-22_19_44_56_941 2016-12-22 19:44:56.941 | 2016-12-22 19:44:56.940 24861 ERROR neutron.agent.ovsdb.impl_vsctl [-] Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', '--id=@manager', 'create', 'Manager', 'target="ptcp:6640:127.0.0.1"', '--', 'add', 'Open_vSwitch', '.', 'manager_options', '@manager']. Exception: Failed to spawn rootwrap process. 2016-12-22 19:44:56.941 | stderr: 2016-12-22 19:44:56.941 | b'Traceback (most recent call last):\n File "/usr/local/bin/neutron-rootwrap-daemon", line 10, in \n sys.exit(daemon())\n File "/usr/local/lib/python3.5/dist-packages/oslo_rootwrap/cmd.py", line 57, in daemon\nreturn main(run_daemon=True)\n File "/usr/local/lib/python3.5/dist-packages/oslo_rootwrap/cmd.py", line 91, in main\nfilters = wrapper.load_filters(config.filters_path)\n File "/usr/local/lib/python3.5/dist-packages/oslo_rootwrap/wrapper.py", line 120, in load_filters\nfilterconfig.read(os.path.join(filterdir, filterfile))\n File "/usr/lib/python3.5/configparser.py", line 696, in read\n self._read(fp, filename)\n File "/usr/lib/python3.5/configparser.py", line 1089, in _read\nfpname, lineno)\nconfigparser.DuplicateOptionError: While reading from \'/etc/neutron/rootwrap.d/privsep.filters\' [line 32]: option \'privsep\' in section \'Filters\' already exists\n' https://github.com/openstack/neutron/blob/master/etc/neutron/rootwrap.d/privsep.filters#L32-L36 ** 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/1652157 Title: privsep configuration is invalid Status in neutron: New Bug description: http://logs.openstack.org/76/414176/6/check/gate-devstack-dsvm-py35 -updown-ubuntu-xenial- nv/e100b7f/logs/devstacklog.txt.gz#_2016-12-22_19_44_56_941 2016-12-22 19:44:56.941 | 2016-12-22 19:44:56.940 24861 ERROR neutron.agent.ovsdb.impl_vsctl [-] Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', '--id=@manager', 'create', 'Manager', 'target="ptcp:6640:127.0.0.1"', '--', 'add', 'Open_vSwitch', '.', 'manager_options', '@manager']. Exception: Failed to spawn rootwrap process. 2016-12-22 19:44:56.941 | stderr: 2016-12-22 19:44:56.941 | b'Traceback (most recent call last):\n File "/usr/local/bin/neutron-rootwrap-daemon", line 10, in \n sys.exit(daemon())\n File "/usr/local/lib/python3.5/dist-packages/oslo_rootwrap/cmd.py", line 57, in daemon\nreturn main(run_daemon=True)\n File "/usr/local/lib/python3.5/dist-packages/oslo_rootwrap/cmd.py", line 91, in main\nfilters = wrapper.load_filters(config.filters_path)\n File "/usr/local/lib/python3.5/dist-packages/oslo_rootwrap/wrapper.py", line 120, in load_filters\nfilterconfig.read(os.path.join(filterdir, filterfile))\n File "/usr/lib/python3.5/configparser.py", line 696, in read\n self._read(fp, filename)\n File "/usr/lib/python3.5/configparser.py", line 1089, in _read\nfpname, lineno)\nconfigparser.DuplicateOptionError: While reading from \'/etc/neutron/rootwrap.d/privsep.filters\' [line 32]: option \'privsep\' in section \'Filters\' already exists\n' https://github.com/openstack/neutron/blob/master/etc/neutron/rootwrap.d/privsep.filters#L32-L36 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1652157/+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 1571657] Re: it's possible to create IPv6 subnet without address & RA mode
This was intentional
** Changed in: neutron
Status: Opinion => Invalid
** Changed in: python-neutronclient
Status: In Progress => 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/1571657
Title:
it's possible to create IPv6 subnet without address & RA mode
Status in neutron:
Invalid
Status in python-neutronclient:
Invalid
Bug description:
We can create IPv6 subnet without address mode & Ra_mode parameters .
When creating this kind of subnet and attach it to network that have ipv4
when booting VM it does not get any ip address .
No Meaning produce ipv6 subnet without those parameters
[root@puma15 ~(keystone_admin)]# rpm -qa |grep neut
openstack-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-ml2-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
python-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-openvswitch-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-common-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
python-neutronclient-4.1.2-0.20160304195803.5d28651.el7.centos.noarch
python-neutron-lib-0.0.3-0.20160227020344.999828a.el7.centos.noarch
openstack-neutron-metering-agent-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
[root@puma15 ~(keystone_admin)]#
[root@puma15 ~(keystone_admin)]# neutron net-list
+--+--+-+
| id | name |
subnets |
+--+--+-+
| e1af28fe-6725-471f-9dcb-21139dd815af | tempest-network-smoke--922626247 |
dd3f38b2-ba3d-49cf-b5c5-9fd05af1b207 2003::/64 |
| | |
bdd6fe30-d278-437f-97a1-10a93862a338 10.100.0.0/28 |
| ae26ce01-d0f4-46ac-ac74-f652477b0a4c | external_network |
1771fd81-9c6c-4f5b-a7e9-246221e28577 10.35.166.0/24 |
+--+--+-+
[root@puma15 ~(keystone_admin)]# neutron subnet-create
e1af28fe-6725-471f-9dcb-21139dd815af 2001:db1:0::2/64 --name
dhcpv6_slaac_subnete --ip-version 6Created a new subnet:
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2001:db1::2", "end":
"2001:db1:::::"} |
| cidr | 2001:db1::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2001:db1::1
|
| host_routes |
|
| id| 6d30c5c2-c7a7-4439-aa7b-24c10bd26ec8
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode |
|
| name | dhcpv6_slaac_subnete
|
| network_id| e1af28fe-6725-471f-9dcb-21139dd815af
|
| subnetpool_id |
|
| tenant_id | 9a0058cf974c47ecb4f778d8e199f7ae
|
+---+--+
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1571657/+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 1521793] Re: l3ha with L2pop disabled breaks neutron
** No longer affects: neutron ** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1521793 Title: l3ha with L2pop disabled breaks neutron Status in neutron: In Progress Status in openstack-ansible: Fix Released Status in openstack-ansible liberty series: Fix Released Status in openstack-ansible trunk series: Fix Released Bug description: when using l3ha the system will fail to build a vm if L2 population is disabled under most circumstances. To resolve this issue the variable `neutron_l2_population` should be set to "true" by default. The current train of thought was that we'd use L3HA by default however due to current differences in the neutron linux bridge agent it seems that is impossible and will require additional upstream work within neutron. In the near term we should re-enable l2 pop by default and effectively disable the built in L3HA. This issue was reported in the channel by @Ville Vuorinen (IRC: kysse), see http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2015-12-01.log.html from 18:47 onwards. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1521793/+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 1597160] Re: linuxbridget agent-id is not linuxbridge agent uuid
** Tags added: linuxbridge ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1597160 Title: linuxbridget agent-id is not linuxbridge agent uuid Status in neutron: Opinion Bug description: i found that linuxbridget call rpc to api server,call method is 'get_devices_details_list' and pass a param agent_id to rpc server. and i also found that param agent_id does not used in api server, it is just user to debug output message, so i think agent_id is just to used for mark the incoming agent. and if it is used like that, why doesn't use agent uuid instead of 'lb'+pythical_interface mac(like lb00505636ff2d), because uuid is more quickly to see the incoming linuxbridge host than mac address. of course you have another ways to know the incoming linuxbrige host linke param host,so why not delete the useless param ./server.log:48649:2016-06-27 16:36:56.403 108124 DEBUG neutron.plugins.ml2.rpc [req-d8a17733-6e4e-4012-8157-e7b9403c127d - - - - -] Device tapb57d75e8-f4 details requested by agent lb00505636ff2d with host com-net get_device_details /usr/lib/python2.7/site- packages/neutron/plugins/ml2/rpc.py:70 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1597160/+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 1495433] Re: IPv6 packets from non-EUI-64 addresses dropped on SLAAC subnets
** Changed in: neutron Status: New => Opinion ** Tags added: ipv6 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1495433 Title: IPv6 packets from non-EUI-64 addresses dropped on SLAAC subnets Status in neutron: Opinion Bug description: A newly created instance on an IPv6 subnet is provisioned with the following ip6tables chain on the hypervisor: tore@node-a3-02:~$ sudo ip6tables -vL neutron-openvswi-sb6a851ba-e Chain neutron-openvswi-sb6a851ba-e (1 references) pkts bytes target prot opt in out source destination 8869 1298K RETURN all anyany 2001:db8:200:f020:f816:3eff:fea7:b27d anywhere MAC FA:16:3E:A7:B2:7D /* Allow traffic from defined IP/MAC pairs. */ 23 1820 DROP all anyany anywhere anywhere /* Drop traffic without an IP/MAC allow rule. */ This blocks outbound traffic from the instance sourced from addresses other than the one mentioned in the RETURN rule. (Inbound traffic does work fine though, and can can be observed in a tcpdump session on the VM. Also ICMPv6 appears to be allowed elsewhere, so ping6 works.) The logic appears to be based on a faulty assumption, namely that an IPv6 node on a SLAAC subnet will only have a single IPv6 address, and that this address has an EUI-64 based Interface ID. That is, however, quite simply not how IPv6 works; when a host receives an ICMPv6 Router Advertisement containing a /64 Prefix Information Option with the Autonomous flag set, this essentially informs the host that it can freely use *any* arbitrary address inside that /64 (provided that it performs the Duplicate Address Detection algorithm). The host is under no obligation to use the EUI-64 algorithm in order to constructs its Interface ID. Even if it does use EUI-64, there is no requirement that prevents it from at the same time self-configuring other addresses using a different Interface ID generation algorithm. This bug breaks the algorithms defined in RFC4941, RFC6877, RFC7217, I-D.ietf-v6ops-siit-dc-2xlat, as well as any other application or use case that requires multiple IPv6 addresses. See also I-D.ietf-v6ops- host-addr-availability. The fix should be trivial, namely to mask the source address in the RETURN rule with a /64. (In the example above, it should have been 2001:db8:200:f020::/64 rather than 2001:db8:200:f020:f816:3eff:fea7:b27d. (Note that the ip6tables binary will do so automatically if it is being given an address such as "2001:db8:200:f020:f816:3eff:fea7:b27d/64".) Tore To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1495433/+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 1588880] [NEW] Upgrade doc needs --expand parameter
Public bug reported: Following the instructions at http://docs.openstack.org/developer/neutron/devref/upgrade.html#server- upgrade results in an error. (neutron-newton) root@aio1-neutron-server-container-c1cf8f9d:/openstack/venvs/neutron-newton/bin# ./neutron-db-manage upgrade -expand INFO [alembic.runtime.migration] Context impl MySQLImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. Traceback (most recent call last): File "./neutron-db-manage", line 10, in sys.exit(main()) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 724, in main return_val |= bool(CONF.command.func(config, CONF.command.name)) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 216, in do_upgrade run_sanity_checks(config, revision) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 702, in run_sanity_checks script_dir.run_env() File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/script/base.py", line 397, in run_env util.load_python_file(self.dir, 'env.py') File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/util/pyfiles.py", line 93, in load_python_file module = load_module_py(module_id, path) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/util/compat.py", line 79, in load_module_py mod = imp.load_source(module_id, path, fp) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/alembic_migrations/env.py", line 120, in run_migrations_online() File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/alembic_migrations/env.py", line 114, in run_migrations_online context.run_migrations() File "", line 8, in run_migrations File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/runtime/environment.py", line 797, in run_migrations self.get_context().run_migrations(**kw) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/runtime/migration.py", line 303, in run_migrations for step in self._migrations_fn(heads, self): File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 693, in check_sanity revision, rev, implicit_base=True): File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/script/revision.py", line 664, in _iterate_revisions raise RangeNotAncestorError(lower, upper) alembic.script.revision.RangeNotAncestorError: Revision (u'4ffceebfcdc',) is not an ancestor of revision expand The invocation should be neutron-db-manage upgrade --expand ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) 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/150 Title: Upgrade doc needs --expand parameter Status in neutron: In Progress Bug description: Following the instructions at http://docs.openstack.org/developer/neutron/devref/upgrade.html #server-upgrade results in an error. (neutron-newton) root@aio1-neutron-server-container-c1cf8f9d:/openstack/venvs/neutron-newton/bin# ./neutron-db-manage upgrade -expand INFO [alembic.runtime.migration] Context impl MySQLImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. Traceback (most recent call last): File "./neutron-db-manage", line 10, in sys.exit(main()) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 724, in main return_val |= bool(CONF.command.func(config, CONF.command.name)) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 216, in do_upgrade run_sanity_checks(config, revision) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 702, in run_sanity_checks script_dir.run_env() File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/script/base.py", line 397, in run_env util.load_python_file(self.dir, 'env.py') File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/util/pyfiles.py", line 93, in load_python_file module = load_module_py(module_id, path) File "/openstack/venvs/neutron-newton/local/lib/python2.7/site-packages/alembic/util/compat.py", line 79, in loa
[Yahoo-eng-team] [Bug 1578281] Re: IPv6 IP allocated on port-create for IPv4 subnet
This is the intended behavior
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-
ipv6-prefixes.html
** Changed in: neutron
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1578281
Title:
IPv6 IP allocated on port-create for IPv4 subnet
Status in neutron:
Opinion
Bug description:
* High level description: When you have a network that has both IPv4
subnet and a IPv6 stateless subnet, a neutron port-create in which
only a IPv4 subnet is requested (via fixed_ip) results in both IPv4
and IPv6 addresses being allocated for the port. An IPv6 address
should not be allocated in this case.
* Pre-conditions: None. CLI commands executed as tenant user.
* Step-by-step reproduction steps: CLI commands shown below
* Expected output: When creating neutron port with fixed_ip of IPv4
subnet, expected the resulting port to contain only an IPv4 address.
* Actual output: IPv6 and IPv4 addresses were allocated on the port-
create
* Version: master / DevStack
* Steps to re-create:
Create a neutron network with 2 subnets (v4 and v6-slaac)
$ neutron net-create network
$ neutron subnet-create --name subnet_v4 --ip-version 4 network
172.16.1.0/24
$ neutron subnet-create --name subnet_v6 --ip-version 6 --ipv6-ra-mode slaac
--ipv6-address-mode slaac network 2001:db8::/64
$ neutron net-list
+--+-+-+
| id | name| subnets
|
+--+-+-+
| e0c605e7-f117-4319-8eab-6429c8d53b4b | network |
bba5da3a-500c-466b-9d1d-f917d5c24d64 172.16.1.0/24 |
| | |
49d0ce59-6888-4e0c-8aff-7def31087524 2001:db8::/64 |
|+--+-+-+
When creating a neutron port, an IP address is allocated out of both subnets
(as expected).
$ neutron port-create network
Created a new port:
+---+--+
| Field | Value
|
+---+--+
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:vnic_type | normal
|
| created_at| 2016-05-04T15:33:08
|
| description |
|
| device_id |
|
| device_owner |
|
| dns_name |
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id":
"bba5da3a-500c-466b-9d1d-f917d5c24d64", "ip_address": "172.16.1.3"}
|
| | {"subnet_id":
"49d0ce59-6888-4e0c-8aff-7def31087524", "ip_address":
"2001:db8::f816:3eff:feb6:75cc"} |
| id| 0e631b7c-0a1d-4d90-a2d6-23f006d7a345
|
| mac_address | fa:16:3e:b6:75:cc
|
| name |
|
| network_id| e0c605e7-f117-4319-8eab-6429c8d53b4b
|
| port_security_enabled | True
|
| security_groups | b886de86-0fdf-4dff-8f07-e67fb7a9a1aa
|
| status| DOWN
[Yahoo-eng-team] [Bug 1460720] Re: [RFE] Add API to set ipv6 gateway
Going to revive this, as part of the RFE review done during the Austin '16 summit ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) ** Changed in: neutron Status: Expired => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1460720 Title: [RFE] Add API to set ipv6 gateway Status in neutron: Confirmed Bug description: Currently the ipv6 external gateway is an admin configuration item. We want instead to have an API to set the ipv6 gateway. Background: The ipv6 router BP (https://blueprints.launchpad.net/neutron/+spec/ipv6-router) added a new L3 agent config called ipv6_gateway wherein an admin can configure the IPv6 LLA of the upstream physical router, so that the neutron virtual router has a default V6 gateway route to the upstream router. This solution is however not scalable when there are multiple external routers per L3 agent. Per review comments - https://review.openstack.org/#/c/156283/42/etc/l3_agent.ini It is better to move this config to the CLI. As discussed in the L3 weekly meeting - http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-11-15.04.log.html, this change aims to make this exact change by updating neutron net- create CLI will to now have a new option to set an ipv6_gateway (for the external router). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1460720/+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 1372441] Re: [RFE] Creating port in dual-stack network requires IPv4 and IPv6 addresses to be allocated
We took a look at this again during the Austin '16 summit, let's see if we can resurrect this. ** Changed in: neutron Status: Expired => Confirmed ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1372441 Title: [RFE] Creating port in dual-stack network requires IPv4 and IPv6 addresses to be allocated Status in neutron: Confirmed Bug description: Currently, when creating port in dual-stack network (network with one ore more IPv4 subnets and one or more IPv6 subnets), Neutron allocates fixed-ip from both, v4 and v6 subnets. If one of the subnets do not have available addresses, it is considered as error. IMO, this is wrong. Operation should succeed if at least one address (IPv4 of IPv6) was allocated. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1372441/+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 1570681] Re: neutron server side should not specified the firewall driver
I'm setting this to opinion, because the author has a lot to say about what we do wrong, but until a patch comes along, it's just that. ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1570681 Title: neutron server side should not specified the firewall driver Status in neutron: Opinion Bug description: In neutron master, We must use the OVSHybridIptablesFirewallDriver to set in neutron-server side now. If not , neutron will return the port contained "ovs_hybrid_plug": false", so nova will plug the vm port on br-int directly. This will cause the security group not available even the iptables rules set correct. The case in this view: 1.There are some agent types in openstack, 1 type agent use iptables for security group, 1 type agent use flow tables for security group. 2.If the firewall driver of background agent realize the security group based on ovs flow table, the port should be plugged on br-int directly and not use linux bridge. 3.The firewall driver of background agent realize security group based on iptables should still use the linux bridge. 4.If neutron server side not config the firewall driver, the vms on the iptables agents hosts will lose efficacy as nova will plug the vm port on br-int, but flow table based agents will ok. 5.If neutron server side want hybrid_plug_required, it will set firewall driver as neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver, it will cause the port of the vms on the ovs-flow agent hosts plug on linux bridge , this must be strange. So what I feel strange is why neutron should config firewall driver, it should only set enable_sg is ok, and agent will realize their own function. And agents should report their own firewall driver , then server side could check it if return "ovs_hybrid_plug": false" /"true" to nova. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1570681/+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 1571657] Re: it's possible to create IPv6 subnet without address & RA mode
Some plugins, pre Kilo may have had a working IPv6 stack, so the ipv6_*
parameters have always been optional.
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1571657
Title:
it's possible to create IPv6 subnet without address & RA mode
Status in neutron:
Opinion
Bug description:
We can create IPv6 subnet without address mode & Ra_mode parameters .
When creating this kind of subnet and attach it to network that have ipv4
when booting VM it does not get any ip address .
No Meaning produce ipv6 subnet without those parameters
[root@puma15 ~(keystone_admin)]# rpm -qa |grep neut
openstack-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-ml2-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
python-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-openvswitch-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-common-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
python-neutronclient-4.1.2-0.20160304195803.5d28651.el7.centos.noarch
python-neutron-lib-0.0.3-0.20160227020344.999828a.el7.centos.noarch
openstack-neutron-metering-agent-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
[root@puma15 ~(keystone_admin)]#
[root@puma15 ~(keystone_admin)]# neutron net-list
+--+--+-+
| id | name |
subnets |
+--+--+-+
| e1af28fe-6725-471f-9dcb-21139dd815af | tempest-network-smoke--922626247 |
dd3f38b2-ba3d-49cf-b5c5-9fd05af1b207 2003::/64 |
| | |
bdd6fe30-d278-437f-97a1-10a93862a338 10.100.0.0/28 |
| ae26ce01-d0f4-46ac-ac74-f652477b0a4c | external_network |
1771fd81-9c6c-4f5b-a7e9-246221e28577 10.35.166.0/24 |
+--+--+-+
[root@puma15 ~(keystone_admin)]# neutron subnet-create
e1af28fe-6725-471f-9dcb-21139dd815af 2001:db1:0::2/64 --name
dhcpv6_slaac_subnete --ip-version 6Created a new subnet:
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2001:db1::2", "end":
"2001:db1:::::"} |
| cidr | 2001:db1::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2001:db1::1
|
| host_routes |
|
| id| 6d30c5c2-c7a7-4439-aa7b-24c10bd26ec8
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode |
|
| name | dhcpv6_slaac_subnete
|
| network_id| e1af28fe-6725-471f-9dcb-21139dd815af
|
| subnetpool_id |
|
| tenant_id | 9a0058cf974c47ecb4f778d8e199f7ae
|
+---+--+
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1571657/+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 1570976] [NEW] neutronclient is missing help text for the purge command
Public bug reported: stack@devstack-1:~/devstack$ neutron --help port-update Update port's information. purge qos-available-rule-types List available qos rule types. stack@devstack-1:~/devstack$ neutron --version 4.2.0 ** Affects: neutron Importance: Undecided Status: New ** Description changed: $neutron --help ... - port-update Update port's information. - purge - qos-available-rule-types List available qos rule types. + port-update Update port's information. + purge + qos-available-rule-types List available qos rule types. ... ** Description changed: - $neutron --help - - ... + stack@devstack-1:~/devstack$ neutron --help + port-update Update port's information. purge qos-available-rule-types List available qos rule types. - ... + + + stack@devstack-1:~/devstack$ neutron --version + 4.2.0 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1570976 Title: neutronclient is missing help text for the purge command Status in neutron: New Bug description: stack@devstack-1:~/devstack$ neutron --help port-update Update port's information. purge qos-available-rule-types List available qos rule types. stack@devstack-1:~/devstack$ neutron --version 4.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1570976/+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 1566942] [NEW] Nova live-migrations cannot be done with mixed versions of nova-api and nova-compute
Public bug reported: When running a controller (nova was SHA b55d5bc), and nova-compute (from Liberty) on a separate node, and attempting to live-migrate instances off the liberty nova-compute, the following error occurs: http://paste.openstack.org/show/492327/ ** Affects: nova Importance: Undecided Status: New ** Tags: live-migration -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1566942 Title: Nova live-migrations cannot be done with mixed versions of nova-api and nova-compute Status in OpenStack Compute (nova): New Bug description: When running a controller (nova was SHA b55d5bc), and nova-compute (from Liberty) on a separate node, and attempting to live-migrate instances off the liberty nova-compute, the following error occurs: http://paste.openstack.org/show/492327/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1566942/+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 1561938] Re: python-novaclient live_migrate args mismatch
** Also affects: python-novaclient Importance: Undecided Status: New ** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1561938 Title: python-novaclient live_migrate args mismatch Status in python-novaclient: New Bug description: When attempting to use python-novaclient to do a host-evacuate-live - the following error is returned. http://paste.openstack.org/show/491762/ Nova git commits are b55d5bc and 1feab8. Controller is b55d5bc and compute is 1feab8. novaclient version is 3.3.0 No errors are reported in the traces on the controller or compute - which leads me to believe it's an error client side. passing the --debug option yields the following http://paste.openstack.org/show/491863/ Doing a little research, this commit looks suspicious. https://github.com/openstack/python- novaclient/commit/ae598280acc46dd4ee20af78a5780a450f96b084 To manage notifications about this bug go to: https://bugs.launchpad.net/python-novaclient/+bug/1561938/+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 1561938] [NEW] python-novaclient live_migrate args mismatch
Public bug reported: When attempting to use python-novaclient to do a host-evacuate-live - the following error is returned. http://paste.openstack.org/show/491762/ Nova git commits are b55d5bc and 1feab8. Controller is b55d5bc and compute is 1feab8. novaclient version is 3.3.0 No errors are reported in the traces on the controller or compute - which leads me to believe it's an error client side. passing the --debug option yields the following http://paste.openstack.org/show/491863/ Doing a little research, this commit looks suspicious. https://github.com/openstack/python- novaclient/commit/ae598280acc46dd4ee20af78a5780a450f96b084 ** Affects: nova Importance: Undecided Status: New ** Tags: live-migration -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1561938 Title: python-novaclient live_migrate args mismatch Status in OpenStack Compute (nova): New Bug description: When attempting to use python-novaclient to do a host-evacuate-live - the following error is returned. http://paste.openstack.org/show/491762/ Nova git commits are b55d5bc and 1feab8. Controller is b55d5bc and compute is 1feab8. novaclient version is 3.3.0 No errors are reported in the traces on the controller or compute - which leads me to believe it's an error client side. passing the --debug option yields the following http://paste.openstack.org/show/491863/ Doing a little research, this commit looks suspicious. https://github.com/openstack/python- novaclient/commit/ae598280acc46dd4ee20af78a5780a450f96b084 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1561938/+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'll set this to incomplete - to see if the reporter can come back and
verify. There may have been a related fix that resolved this, but was
not linked to this bug.
** Changed in: neutron
Status: Fix Released => 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/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 1554762] [NEW] Neutron fwaas install doc needs to replace the wiki page
Public bug reported: It's outdated and refers to DevStack. https://wiki.openstack.org/wiki/Neutron/FWaaS/HowToInstall ** Affects: neutron Importance: Low Assignee: Sean M. Collins (scollins) Status: Confirmed ** Tags: fwaas ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Importance: Undecided => Low ** Changed in: neutron Milestone: None => next -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1554762 Title: Neutron fwaas install doc needs to replace the wiki page Status in neutron: Confirmed Bug description: It's outdated and refers to DevStack. https://wiki.openstack.org/wiki/Neutron/FWaaS/HowToInstall To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1554762/+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 1549471] [NEW] Networks with an MTU of zero makes zero sense
Public bug reported: vagrant@vagrant-ubuntu-wily-32:~/devstack$ neutron net-show a99a3d30-19a0-4e69-9e90-129d192e5948 +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | availability_zone_hints | | | availability_zones| nova | | id| a99a3d30-19a0-4e69-9e90-129d192e5948 | | is_default| False| | mtu | 0| | name | public | | port_security_enabled | True | | provider:network_type | flat | | provider:physical_network | default | | provider:segmentation_id | | | router:external | True | | shared| False| | status| ACTIVE | | subnets | f83007e9-0907-488b-9a45-940984d1f4dc | | | 2cb54543-2302-4142-8f3b-735fd5aa73fb | | tenant_id | f8190c1517b7455a89dc952d43f890eb | +---+--+ So yeah let's try and clean this up somehow. I imagine that part of it has to be the physical_network_mtus setting ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) Status: New ** Summary changed: - Networks with an MTU of zero make zero sense + Networks with an MTU of zero makes zero sense ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1549471 Title: Networks with an MTU of zero makes zero sense Status in neutron: New Bug description: vagrant@vagrant-ubuntu-wily-32:~/devstack$ neutron net-show a99a3d30-19a0-4e69-9e90-129d192e5948 +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | availability_zone_hints | | | availability_zones| nova | | id| a99a3d30-19a0-4e69-9e90-129d192e5948 | | is_default| False| | mtu | 0| | name | public | | port_security_enabled | True | | provider:network_type | flat | | provider:physical_network | default | | provider:segmentation_id | | | router:external | True | | shared| False| | status| ACTIVE | | subnets | f83007e9-0907-488b-9a45-940984d1f4dc | | | 2cb54543-2302-4142-8f3b-735fd5aa73fb | | tenant_id | f8190c1517b7455a89dc952d43f890eb | +---+--+ So yeah let's try and clean this up somehow. I imagine that part of it has to be the physical_network_mtus setting To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1549471/+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 1548803] [NEW] neutron-lbaas 6aee0434f911_independent_pools.py errors out in postgres db
Public bug reported: http://logs.openstack.org/39/279339/6/experimental/gate-tempest-dsvm- neutron-pg-full/ab0fcf0/logs/devstacklog.txt.gz#_2016-02-22_23_58_03_932 2016-02-22 23:58:03.926 | INFO [alembic.runtime.migration] Running upgrade 3426acbc12de -> 6aee0434f911, independent pools 2016-02-22 23:58:03.930 | Traceback (most recent call last): 2016-02-22 23:58:03.930 | File "/usr/local/bin/neutron-db-manage", line 10, in 2016-02-22 23:58:03.930 | sys.exit(main()) 2016-02-22 23:58:03.930 | File "/opt/stack/new/neutron/neutron/db/migration/cli.py", line 744, in main 2016-02-22 23:58:03.930 | return_val |= bool(CONF.command.func(config, CONF.command.name)) 2016-02-22 23:58:03.930 | File "/opt/stack/new/neutron/neutron/db/migration/cli.py", line 220, in do_upgrade 2016-02-22 23:58:03.930 | desc=branch, sql=CONF.command.sql) 2016-02-22 23:58:03.930 | File "/opt/stack/new/neutron/neutron/db/migration/cli.py", line 127, in do_alembic_command 2016-02-22 23:58:03.930 | getattr(alembic_command, cmd)(config, *args, **kwargs) 2016-02-22 23:58:03.930 | File "/usr/local/lib/python2.7/dist-packages/alembic/command.py", line 174, in upgrade 2016-02-22 23:58:03.930 | script.run_env() 2016-02-22 23:58:03.930 | File "/usr/local/lib/python2.7/dist-packages/alembic/script/base.py", line 397, in run_env 2016-02-22 23:58:03.931 | util.load_python_file(self.dir, 'env.py') 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file 2016-02-22 23:58:03.931 | module = load_module_py(module_id, path) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/util/compat.py", line 79, in load_module_py 2016-02-22 23:58:03.931 | mod = imp.load_source(module_id, path, fp) 2016-02-22 23:58:03.931 | File "/opt/stack/new/neutron-lbaas/neutron_lbaas/db/migration/alembic_migrations/env.py", line 85, in 2016-02-22 23:58:03.931 | run_migrations_online() 2016-02-22 23:58:03.931 | File "/opt/stack/new/neutron-lbaas/neutron_lbaas/db/migration/alembic_migrations/env.py", line 76, in run_migrations_online 2016-02-22 23:58:03.931 | context.run_migrations() 2016-02-22 23:58:03.931 | File "", line 8, in run_migrations 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/runtime/environment.py", line 797, in run_migrations 2016-02-22 23:58:03.931 | self.get_context().run_migrations(**kw) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/runtime/migration.py", line 312, in run_migrations 2016-02-22 23:58:03.931 | step.migration_fn(**kw) 2016-02-22 23:58:03.931 | File "/opt/stack/new/neutron-lbaas/neutron_lbaas/db/migration/alembic_migrations/versions/mitaka/expand/6aee0434f911_independent_pools.py", line 46, in upgrade 2016-02-22 23:58:03.931 | type_='foreignkey') 2016-02-22 23:58:03.931 | File "", line 8, in drop_constraint 2016-02-22 23:58:03.931 | File "", line 3, in drop_constraint 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/operations/ops.py", line 145, in drop_constraint 2016-02-22 23:58:03.931 | return operations.invoke(op) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/operations/base.py", line 318, in invoke 2016-02-22 23:58:03.931 | return fn(self, operation) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/operations/toimpl.py", line 146, in drop_constraint 2016-02-22 23:58:03.931 | schema=operation.schema, 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/ddl/impl.py", line 183, in drop_constraint 2016-02-22 23:58:03.931 | self._exec(schema.DropConstraint(const)) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/alembic/ddl/impl.py", line 118, in _exec 2016-02-22 23:58:03.931 | return conn.execute(construct, *multiparams, **params) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 914, in execute 2016-02-22 23:58:03.931 | return meth(self, multiparams, params) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/ddl.py", line 68, in _execute_on_connection 2016-02-22 23:58:03.931 | return connection._execute_ddl(self, multiparams, params) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 968, in _execute_ddl 2016-02-22 23:58:03.931 | compiled 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1146, in _execute_context 2016-02-22 23:58:03.931 | context) 2016-02-22 23:58:03.931 | File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1337, in _handle_dbapi_exception 2016-02-22 23:58:03.932 | util.raise_from_cause(newraise, exc_info) 2016-02-22 23:58:03.9
[Yahoo-eng-team] [Bug 1545101] Re: "TypeError: __init__() takes exactly 3 arguments (2 given)" in n-api logs for nova metadata api request
+Neutron and myself since it's the grenade multinode job that is being hit ** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1545101 Title: "TypeError: __init__() takes exactly 3 arguments (2 given)" in n-api logs for nova metadata api request Status in neutron: In Progress Status in OpenStack Compute (nova): In Progress Bug description: http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm- neutron- multinode/8f1deec/logs/new/screen-n-api.txt.gz?level=INFO#_2016-02-12_16_28_16_860 2016-02-12 16:28:16.860 20168 INFO nova.metadata.wsgi.server [-] Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 470, in handle_one_response result = self.application(self.environ, start_response) File "/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 216, in __call__ return app(environ, start_response) File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func return self.func(req, *args, **kwargs) File "/opt/stack/new/nova/nova/api/ec2/__init__.py", line 32, in __call__ return webob.exc.HTTPException(message=_DEPRECATION_MESSAGE) TypeError: __init__() takes exactly 3 arguments (2 given) This only shows up in the gate-grenade-dsvm-neutron-multinode job which is not running the n-api-meta service but is running the neutron metadata service, which has a bunch of warnings because it's not getting valid responses back from the nova metadata API (b/c it's not running): http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm- neutron-multinode/8f1deec/logs/new/screen-q-meta.txt.gz?level=TRACE To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1545101/+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 1542962] Re: DHCP agent RuntimeError when dnsmasq_config_file is not given
** Changed in: neutron Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1542962 Title: DHCP agent RuntimeError when dnsmasq_config_file is not given Status in neutron: Opinion Bug description: DHCP agent RuntimeError when is not given To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1542962/+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 1534458] Re: [RFE] Multi-region Security Group
Yes. There are numerous resources that are not currently synced between regions. SGs are just one. Images, flavors, keypairs, etc... ** Changed in: neutron Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1534458 Title: [RFE] Multi-region Security Group Status in neutron: Won't Fix Bug description: This RFE is requesting feature "Multi-region Security Group" to configure security group across multiple regions. [Backgroud] OpenStack 'Regions' is used to construct more than one openstack environments between geographically-distributed places. Each region is independent openstack environment and placed in a datacenter which is geographically distant from each other, for example, different country. This is important to ensure availability. Even if one region stops due to problems, we can continue our work in other regions. [Existing problem] In multi-region environment, the one of inconvenient points is configuring security group. For example, there are two regions 'region 1' and 'region 2'. Each region has web server and its db server. Region 1: web server(W1) and db server (D1) Region 2: web server(W2) and db server (D2) Say that each region is connected in L3 layer (IP is reachable each other). In such a case, we want to set up security group so that both of W1 and W2 can access to D1 and D2. But each region is independent and we have to set up security group one by one in each region. [Proposal] Multi-region security group enables us to create security group across regions. Once it is introduced, we can add security group which can be shared between regions. In the case above: - Make two multi-region security group, SG1 and SG2 - Add W1,W2 to SG1 - Add D1,D2 to SG2 And then by adding rule to SG2 to allow access from SG1, W1 and W2 can access to D1 and D2. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1534458/+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 1541738] Re: Rule on the tun bridge is not updated in time while migrating the vm
OK. Marking this as confirmed and moving to wishlist, based on the fact that this seems to be more about an enhancement to migration time. If you have a patch feel free to submit it to gerrit and link to this bug in your commit message. ** Changed in: neutron Status: Incomplete => Opinion ** Changed in: neutron Assignee: Sean M. Collins (scollins) => (unassigned) ** Changed in: neutron Status: Opinion => Confirmed ** Changed in: neutron Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1541738 Title: Rule on the tun bridge is not updated in time while migrating the vm Status in neutron: Confirmed Bug description: ENV：neutron/master, vxlan After the vm live migration, we can observe that the vm is active using command "nova show". However, the vm network is not ready. When processing vm live migration, nova invokes neutron update_port. It only updates the host ID of the port attribute, but doesn't update the rules on the tun bridge. This means the output port in the rule below is not updated to the vxlan port, which should be connected to the host node that the vm is migrated to. ovs-ofctl dump-flows br-tun | grep 1ef cookie=0x0, duration=194.884s, table=20, n_packets=0, n_bytes=0, hard_timeout=300, idle_age=194, priority=1,vlan_tci=0x0306/0x0fff,dl_dst=5a:c6:4f:34:61:06 actions=load:0->NXM_OF_VLAN_TCI[],load:0x1ef->NXM_NX_TUN_ID[],output:24 Due to the reason explained above, the time for vm migration is increased. By monitoring the rule status on the tun bridge and the network connectivity, the network connectivity is restored after the rule of tun bridge is updated. Therefore, the time for vm migration can be reduced by updating the rule immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1541738/+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 1538740] [NEW] SIGTERM on neutron-l3 agent process causes stacktrace
Public bug reported: vagrant@vagrant-ubuntu-wily-32:/opt/stack/logs$ pkill l3 Log: 2016-01-27 20:45:39.152 14651 DEBUG neutron.agent.linux.utils [-] Exit code: 0 execute /opt/stack/neutron/neutron/agent/linux/utils.py:142 2016-01-27 20:45:50.012 DEBUG oslo_concurrency.lockutils [req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Acquired semaphore "singleton_lock" lock /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:212 2016-01-27 20:45:50.014 DEBUG oslo_concurrency.lockutils [req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Releasing semaphore "singleton_lock" lock /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:225 2016-01-27 20:45:50.015 14651 ERROR oslo.messaging._drivers.impl_rabbit [-] Failed to consume message from queue: 'NoneType' object has no attribute 'info' 2016-01-27 20:45:50.015 14651 ERROR root [-] Unexpected exception occurred 1 time(s)... retrying. 2016-01-27 20:45:50.015 14651 ERROR root Traceback (most recent call last): 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 234, in wrapper 2016-01-27 20:45:50.015 14651 ERROR root return infunc(*args, **kwargs) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_executors/impl_pooledexecutor.py", line 98, in _runner 2016-01-27 20:45:50.015 14651 ERROR root prefetch_size=self.dispatcher.batch_size) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/base.py", line 45, in wrapper 2016-01-27 20:45:50.015 14651 ERROR root msg = func(in_self, timeout=watch.leftover(return_none=True)) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 212, in poll 2016-01-27 20:45:50.015 14651 ERROR root self.conn.consume(timeout=timeout) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 904, in consume 2016-01-27 20:45:50.015 14651 ERROR root error_callback=_error_callback) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 689, in ensure 2016-01-27 20:45:50.015 14651 ERROR root ret, channel = autoretry_method() 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 449, in _ensured 2016-01-27 20:45:50.015 14651 ERROR root errback and errback(exc, 0) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 625, in on_error 2016-01-27 20:45:50.015 14651 ERROR root info.update(self.connection.info()) 2016-01-27 20:45:50.015 14651 ERROR root AttributeError: 'NoneType' object has no attribute 'info' 2016-01-27 20:45:50.015 14651 ERROR root 2016-01-27 20:45:50.021 INFO oslo_rootwrap.client [req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Stopping rootwrap daemon process with pid=14684 ** Affects: neutron Importance: Low Status: New ** Changed in: neutron Importance: Undecided => Low ** Description changed: + vagrant@vagrant-ubuntu-wily-32:/opt/stack/logs$ pkill l3 + + + Log: + 2016-01-27 20:45:39.152 14651 DEBUG neutron.agent.linux.utils [-] Exit code: 0 execute /opt/stack/neutron/neutron/agent/linux/utils.py:142 2016-01-27 20:45:50.012 DEBUG oslo_concurrency.lockutils [req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Acquired semaphore "singleton_lock" lock /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:212 2016-01-27 20:45:50.014 DEBUG oslo_concurrency.lockutils [req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Releasing semaphore "singleton_lock" lock /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:225 2016-01-27 20:45:50.015 14651 ERROR oslo.messaging._drivers.impl_rabbit [-] Failed to consume message from queue: 'NoneType' object has no attribute 'info' 2016-01-27 20:45:50.015 14651 ERROR root [-] Unexpected exception occurred 1 time(s)... retrying. 2016-01-27 20:45:50.015 14651 ERROR root Traceback (most recent call last): 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 234, in wrapper 2016-01-27 20:45:50.015 14651 ERROR root return infunc(*args, **kwargs) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_executors/impl_pooledexecutor.py", line 98, in _runner 2016-01-27 20:45:50.015 14651 ERROR root prefetch_size=self.dispatcher.batch_size) 2016-01-27 20:45:50.015 14651 ERROR root File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/base.py", line 45, in wrapper 2016-01-27 20:45:50.015 14651 ERROR root msg = func(in_self, timeout=
[Yahoo-eng-team] [Bug 1537734] [NEW] Users cannot clear allowed address pairs from a port
Public bug reported: http://lists.openstack.org/pipermail/openstack- dev/2016-January/084819.html It appears that the validator "validate_allowed_address_pairs" does not take into account the --action=clear parameter that is used to update a port and remove allowed address pairs. ** 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/1537734 Title: Users cannot clear allowed address pairs from a port Status in neutron: New Bug description: http://lists.openstack.org/pipermail/openstack- dev/2016-January/084819.html It appears that the validator "validate_allowed_address_pairs" does not take into account the --action=clear parameter that is used to update a port and remove allowed address pairs. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1537734/+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 1537661] Re: devstack with stable/liberty and neutron lbaas v2 is failing
** Also affects: octavia 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/1537661 Title: devstack with stable/liberty and neutron lbaas v2 is failing Status in devstack: New Status in neutron: New Status in octavia: New Bug description: I am using following localrc KEYSTONE_BRANCH=stable/liberty NOVA_BRANCH=stable/liberty GLANCE_BRANCH=stable/liberty CINDER_BRANCH=stable/liberty NEUTRON_BRANCH=stable/liberty HEAT_BRANCH=stable/liberty CEILOMETER_BRANCH=stable/liberty SWIFT_BRANCH=2.3.0 OCTAVIA_BRANCH=stable/liberty NEUTRON_LBAAS_BRANCH=stable/liberty # Logging LOGFILE=$DEST/logs/stack.sh.log VERBOSE=True LOGDAYS=1 LOG_COLOR=False SCREEN_LOGDIR=/opt/stack/logs # Load the external LBaaS plugin. enable_plugin neutron-lbaas https://git.openstack.org/openstack/neutron-lbaas enable_plugin octavia https://git.openstack.org/openstack/octavia # Pre-requisite ENABLED_SERVICES=rabbit,mysql,key # Nova ENABLED_SERVICES+=,n-api,n-crt,n-cpu,n-cond,n-sch # Glance ENABLED_SERVICES+=,g-api,g-reg # Neutron ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta # Enable LBaaS v2 ENABLED_SERVICES+=,q-lbaasv2 ENABLED_SERVICES+=,octavia,o-cw,o-hk,o-hm,o-api # Cinder ENABLED_SERVICES+=,c-api,c-vol,c-sch # Heat ENABLED_SERVICES+=,h-api,h-api-cfn,h-eng # Tempest ENABLED_SERVICES+=,tempest neutron fails to start with "Plugin not found" error and hence devstack fails. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1537661/+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 1523638] Re: tempest fails with No IPv4 addresses found
Adding tempest to the list of affected projects. It's possible that the tempest code is holding onto a reference to an instance after it has been deleted and attempts to use it again. ** Also affects: tempest Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1523638 Title: tempest fails with No IPv4 addresses found Status in neutron: Confirmed Status in tempest: New Bug description: http://logs.openstack.org/42/250542/7/check/gate-tempest-dsvm-neutron- linuxbridge/3a00f8b/logs/testr_results.html.gz Traceback (most recent call last): File "tempest/test.py", line 113, in wrapper return f(self, *func_args, **func_kwargs) File "tempest/scenario/test_network_basic_ops.py", line 550, in test_subnet_details self._setup_network_and_servers(dns_nameservers=[initial_dns_server]) File "tempest/scenario/test_network_basic_ops.py", line 123, in _setup_network_and_servers floating_ip = self.create_floating_ip(server) File "tempest/scenario/manager.py", line 842, in create_floating_ip port_id, ip4 = self._get_server_port_id_and_ip4(thing) File "tempest/scenario/manager.py", line 821, in _get_server_port_id_and_ip4 "No IPv4 addresses found in: %s" % ports) File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/unittest2/case.py", line 845, in assertNotEqual raise self.failureException(msg) AssertionError: 0 == 0 : No IPv4 addresses found in: [] To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1523638/+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 1527675] [NEW] Neutron multinode grenade sometimes fails at resource phase create
Public bug reported:
Mailing list thread:
http://lists.openstack.org/pipermail/openstack-
dev/2015-November/080503.html
http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/a5af283/logs/grenade.sh.txt.gz
Pinging the VM works, however when SSH'ing in to verify further, the
connection is repeatedly closed.
http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-
neutron-
multinode/a5af283/logs/grenade.sh.txt.gz#_2015-11-30_20_25_18_391
2015-11-30 20:20:18.283 | + ssh -o UserKnownHostsFile=/dev/null -o
StrictHostKeyChecking=no -i /opt/stack/save/cinder_key.pem cirros@172.24.5.53
'echo '\''I am a teapot'\'' > verify.txt'
2015-11-30 20:25:18.391 | Connection closed by 172.24.5.53
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sean M. Collins (scollins)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1527675
Title:
Neutron multinode grenade sometimes fails at resource phase create
Status in neutron:
New
Bug description:
Mailing list thread:
http://lists.openstack.org/pipermail/openstack-
dev/2015-November/080503.html
http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/a5af283/logs/grenade.sh.txt.gz
Pinging the VM works, however when SSH'ing in to verify further, the
connection is repeatedly closed.
http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-
neutron-
multinode/a5af283/logs/grenade.sh.txt.gz#_2015-11-30_20_25_18_391
2015-11-30 20:20:18.283 | + ssh -o UserKnownHostsFile=/dev/null -o
StrictHostKeyChecking=no -i /opt/stack/save/cinder_key.pem cirros@172.24.5.53
'echo '\''I am a teapot'\'' > verify.txt'
2015-11-30 20:25:18.391 | Connection closed by 172.24.5.53
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1527675/+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 1524913] Re: Potential gate problem for neutron-linuxbridge job in stable/liberty
** Project changed: openstack-manuals => neutron ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524913 Title: Potential gate problem for neutron-linuxbridge job in stable/liberty Status in neutron: Confirmed Bug description: The neutron-linuxbridge gate job repeatedly fails for the following patch to stable/liberty: https://review.openstack.org/#/c/251753 Perhaps useful: http://logs.openstack.org/53/251753/3/check/gate-tempest-dsvm-neutron- linuxbridge/76832b3/logs/screen-q-l3.txt.gz#_2015-12-10_11_52_31_751 http://logs.openstack.org/53/251753/3/gate/gate-tempest-dsvm-neutron- linuxbridge/3a4e5fc/logs/devstacklog.txt.gz#_2015-12-08_13_25_33_311 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524913/+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 1523638] [NEW] tempest test_subnet_details fails with No IPv4 addresses found
Public bug reported: http://logs.openstack.org/42/250542/7/check/gate-tempest-dsvm-neutron- linuxbridge/3a00f8b/logs/testr_results.html.gz Traceback (most recent call last): File "tempest/test.py", line 113, in wrapper return f(self, *func_args, **func_kwargs) File "tempest/scenario/test_network_basic_ops.py", line 550, in test_subnet_details self._setup_network_and_servers(dns_nameservers=[initial_dns_server]) File "tempest/scenario/test_network_basic_ops.py", line 123, in _setup_network_and_servers floating_ip = self.create_floating_ip(server) File "tempest/scenario/manager.py", line 842, in create_floating_ip port_id, ip4 = self._get_server_port_id_and_ip4(thing) File "tempest/scenario/manager.py", line 821, in _get_server_port_id_and_ip4 "No IPv4 addresses found in: %s" % ports) File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/unittest2/case.py", line 845, in assertNotEqual raise self.failureException(msg) AssertionError: 0 == 0 : No IPv4 addresses found in: [] ** Affects: neutron Importance: Undecided Status: New ** Tags: linuxbridge ** Tags added: linuxbridge -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1523638 Title: tempest test_subnet_details fails with No IPv4 addresses found Status in neutron: New Bug description: http://logs.openstack.org/42/250542/7/check/gate-tempest-dsvm-neutron- linuxbridge/3a00f8b/logs/testr_results.html.gz Traceback (most recent call last): File "tempest/test.py", line 113, in wrapper return f(self, *func_args, **func_kwargs) File "tempest/scenario/test_network_basic_ops.py", line 550, in test_subnet_details self._setup_network_and_servers(dns_nameservers=[initial_dns_server]) File "tempest/scenario/test_network_basic_ops.py", line 123, in _setup_network_and_servers floating_ip = self.create_floating_ip(server) File "tempest/scenario/manager.py", line 842, in create_floating_ip port_id, ip4 = self._get_server_port_id_and_ip4(thing) File "tempest/scenario/manager.py", line 821, in _get_server_port_id_and_ip4 "No IPv4 addresses found in: %s" % ports) File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/unittest2/case.py", line 845, in assertNotEqual raise self.failureException(msg) AssertionError: 0 == 0 : No IPv4 addresses found in: [] To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1523638/+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 1523616] [NEW] Failing to bind a port should report why it failed, even outside of DEBUG level
Public bug reported:
Some useful information about *why* a port binding failed should be
pushed up into ERROR level, since it has a useful error to help diagnose
the issue, and if someone doesn't have DEBUG level enabled they'd miss
it and wonder why it failed.
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Checking segment:
{'segmentation_id': None, 'physical_network': u'default', 'id':
u'eec249a0-829d-4a8c-a556-d04ffe7533ad', 'network_type': u'flat'} for mappings:
{} with network types: [u'vxlan', 'local', 'flat', 'vlan'] from (pid=13302)
check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:182
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Network
eec249a0-829d-4a8c-a556-d04ffe7533ad is connected to physical network default,
but agent vagrant-ubuntu-trusty-64.localdomain reported physical networks {}.
The physical network must be configured on the agent if binding is to succeed.
from (pid=13302) check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:208
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
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/1523616
Title:
Failing to bind a port should report why it failed, even outside of
DEBUG level
Status in neutron:
In Progress
Bug description:
Some useful information about *why* a port binding failed should be
pushed up into ERROR level, since it has a useful error to help
diagnose the issue, and if someone doesn't have DEBUG level enabled
they'd miss it and wonder why it failed.
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Checking segment:
{'segmentation_id': None, 'physical_network': u'default', 'id':
u'eec249a0-829d-4a8c-a556-d04ffe7533ad', 'network_type': u'flat'} for mappings:
{} with network types: [u'vxlan', 'local', 'flat', 'vlan'] from (pid=13302)
check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:182
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Network
eec249a0-829d-4a8c-a556-d04ffe7533ad is connected to physical network default,
but agent vagrant-ubuntu-trusty-64.localdomain reported physical networks {}.
The physical network must be configured on the agent if binding is to succeed.
from (pid=13302) check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:208
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1523616/+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 1501338] Re: Add VLAN Transparency tests for Neutron API v2
Gary - 216021 does not look like a relevant URL ** Changed in: neutron Status: Incomplete => New ** 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/1501338 Title: Add VLAN Transparency tests for Neutron API v2 Status in neutron: Invalid Bug description: VLAN transparency tests are missing. These need to be added. Tests to be Implemented: 1. Create VLAN transparent Network 2. Show VLAN Transparent Networks 3. Delete VLAN Transparent Networks To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1501338/+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 1519509] Re: Creating instances fails after enabling port_security extension on existing deployment
*** This bug is a duplicate of bug 1453667 *** https://bugs.launchpad.net/bugs/1453667 ** This bug is no longer a duplicate of bug 1519112 Enabling port_security extension in ML2 won't work for networks created *before* enabling it ** This bug has been marked a duplicate of bug 1453667 Changing --port_security_enabled=False in network does not propagated to already existing ports -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1519509 Title: Creating instances fails after enabling port_security extension on existing deployment Status in neutron: New Bug description: Creating instances fails after enabling the port_security extension on an existing deployment. 1) Create necessary network components to launch an instance. 2) Launch an instance. 3) Enable the port_security extension and restart the neutron-server service. 4) Launch another instance which fails with the following errors in the nova-compute service log: http://paste.openstack.org/show/479924/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1519509/+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 1514494] Re: DevStack needs to update the default IPv6 route when moving addresses onto the bridge
Dang it, wrong friggin bug queue! ** Project changed: neutron => devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1514494 Title: DevStack needs to update the default IPv6 route when moving addresses onto the bridge Status in devstack: New Bug description: DevStack takes the ip address assignments from p3p1 (my ethernet adapter) and adds them to the bridge, but fails to remove the duplicate route for p3p1, and also fails to set the default route. stack@devstack-1:~/devstack$ ip -6 r s 2001:db8::/64 dev br-ex proto kernel metric 256 2601:42:600:6154::/64 dev p3p1 proto kernel metric 256 expires 2591480sec 2601:42:600:6154::/64 dev br-ex proto kernel metric 256 fddb:2aa8:48c::/64 via 2001:db8::3 dev br-ex metric 1024 fe80::/64 dev p3p1 proto kernel metric 256 fe80::/64 dev br-int proto kernel metric 256 fe80::/64 dev br-ex proto kernel metric 256 fe80::/64 dev br-tun proto kernel metric 256 stack@devstack-2:~/devstack$ ip -6 r s 2601:42:600:6154::/64 dev p3p1 proto kernel metric 256 expires 2591959sec default via fe80::16da:e9ff:fe21:4348 dev p3p1 proto ra metric 1024 expires 1759sec hoplimit 64 stack@devstack-1:~/devstack$ sudo ip -6 route add default via fe80::16da:e9ff:fe21:4348 dev br-ex stack@devstack-1:~/devstack$ ping6 google.com PING google.com(lga25s40-in-x0e.1e100.net) 56 data bytes 64 bytes from lga25s40-in-x0e.1e100.net: icmp_seq=1 ttl=54 time=26.6 ms 64 bytes from lga25s40-in-x0e.1e100.net: icmp_seq=2 ttl=54 time=20.3 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 20.369/23.496/26.623/3.127 ms To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1514494/+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 1514494] [NEW] DevStack needs to update the default IPv6 route when moving addresses onto the bridge
Public bug reported: DevStack takes the ip address assignments from p3p1 (my ethernet adapter) and adds them to the bridge, but fails to remove the duplicate route for p3p1, and also fails to set the default route. stack@devstack-1:~/devstack$ ip -6 r s 2001:db8::/64 dev br-ex proto kernel metric 256 2601:42:600:6154::/64 dev p3p1 proto kernel metric 256 expires 2591480sec 2601:42:600:6154::/64 dev br-ex proto kernel metric 256 fddb:2aa8:48c::/64 via 2001:db8::3 dev br-ex metric 1024 fe80::/64 dev p3p1 proto kernel metric 256 fe80::/64 dev br-int proto kernel metric 256 fe80::/64 dev br-ex proto kernel metric 256 fe80::/64 dev br-tun proto kernel metric 256 stack@devstack-2:~/devstack$ ip -6 r s 2601:42:600:6154::/64 dev p3p1 proto kernel metric 256 expires 2591959sec default via fe80::16da:e9ff:fe21:4348 dev p3p1 proto ra metric 1024 expires 1759sec hoplimit 64 stack@devstack-1:~/devstack$ sudo ip -6 route add default via fe80::16da:e9ff:fe21:4348 dev br-ex stack@devstack-1:~/devstack$ ping6 google.com PING google.com(lga25s40-in-x0e.1e100.net) 56 data bytes 64 bytes from lga25s40-in-x0e.1e100.net: icmp_seq=1 ttl=54 time=26.6 ms 64 bytes from lga25s40-in-x0e.1e100.net: icmp_seq=2 ttl=54 time=20.3 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 20.369/23.496/26.623/3.127 ms ** Affects: devstack Importance: Undecided Assignee: Sean M. Collins (scollins) Status: New ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1514494 Title: DevStack needs to update the default IPv6 route when moving addresses onto the bridge Status in devstack: New Bug description: DevStack takes the ip address assignments from p3p1 (my ethernet adapter) and adds them to the bridge, but fails to remove the duplicate route for p3p1, and also fails to set the default route. stack@devstack-1:~/devstack$ ip -6 r s 2001:db8::/64 dev br-ex proto kernel metric 256 2601:42:600:6154::/64 dev p3p1 proto kernel metric 256 expires 2591480sec 2601:42:600:6154::/64 dev br-ex proto kernel metric 256 fddb:2aa8:48c::/64 via 2001:db8::3 dev br-ex metric 1024 fe80::/64 dev p3p1 proto kernel metric 256 fe80::/64 dev br-int proto kernel metric 256 fe80::/64 dev br-ex proto kernel metric 256 fe80::/64 dev br-tun proto kernel metric 256 stack@devstack-2:~/devstack$ ip -6 r s 2601:42:600:6154::/64 dev p3p1 proto kernel metric 256 expires 2591959sec default via fe80::16da:e9ff:fe21:4348 dev p3p1 proto ra metric 1024 expires 1759sec hoplimit 64 stack@devstack-1:~/devstack$ sudo ip -6 route add default via fe80::16da:e9ff:fe21:4348 dev br-ex stack@devstack-1:~/devstack$ ping6 google.com PING google.com(lga25s40-in-x0e.1e100.net) 56 data bytes 64 bytes from lga25s40-in-x0e.1e100.net: icmp_seq=1 ttl=54 time=26.6 ms 64 bytes from lga25s40-in-x0e.1e100.net: icmp_seq=2 ttl=54 time=20.3 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 20.369/23.496/26.623/3.127 ms To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1514494/+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 1513412] [NEW] FwaaS extension quota exceeded at the gate
Public bug reported: [20:40]| sc68cal: how do we go about debugging these failures? http://logs.openstack.org/19/225319/20/gate/gate-neutron-dsvm-api/9d9b806/console.html#_2015-11-05_00_01_58_095 - there are a bunch of failures in the q-svc logs but they don't result in 100% job fails in logstash, [20:40] < mriedem> where is the fwaas stuff logged? i assume q-svc [20:40] < mriedem> which is confusing if it's run as it's own service [20:42]<-- | tmatsu [~tmatsu@103.2.128.1] has quit (Read error: Connection reset by peer) [20:42]<-- | rfolco [~rfolco@201.74.199.134] has quit (Quit: This computer has gone to sleep) [20:43] < mriedem> i guess i can use this http://logs.openstack.org/96/237896/4/gate/gate-neutron-dsvm-api/6e1d5c7/logs/screen-q-svc.txt.gz#_2015-11-04_20_14_34_810 ** Affects: neutron Importance: Undecided Status: New ** Tags: fwaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1513412 Title: FwaaS extension quota exceeded at the gate Status in neutron: New Bug description: [20:40] | sc68cal: how do we go about debugging these failures? http://logs.openstack.org/19/225319/20/gate/gate-neutron-dsvm-api/9d9b806/console.html#_2015-11-05_00_01_58_095 - there are a bunch of failures in the q-svc logs but they don't result in 100% job fails in logstash, [20:40] < mriedem> where is the fwaas stuff logged? i assume q-svc [20:40] < mriedem> which is confusing if it's run as it's own service [20:42]<-- | tmatsu [~tmatsu@103.2.128.1] has quit (Read error: Connection reset by peer) [20:42]<-- | rfolco [~rfolco@201.74.199.134] has quit (Quit: This computer has gone to sleep) [20:43] < mriedem> i guess i can use this http://logs.openstack.org/96/237896/4/gate/gate-neutron-dsvm-api/6e1d5c7/logs/screen-q-svc.txt.gz#_2015-11-04_20_14_34_810 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1513412/+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 1332475] Re: neutron should give an error if we give Segmentation_id beyond specified range
This is still an opinion bug, looks like changing it to invalid caused someone to think it should be worked on. ** Changed in: neutron Status: In Progress => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1332475 Title: neutron should give an error if we give Segmentation_id beyond specified range Status in neutron: Opinion Bug description: Problem in segment-Id range, it should belongs to given range, command to reproduce : neutron net-create demo_net --provider:network_type gre --provider:Segmentation_id 2000 right now its allowing to create. expected: neutron should give an error if we give Segmentation_id beyond specified range. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1332475/+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 1217750] Re: Port not released after the instance is deleted
*** This bug is a duplicate of bug 1158684 *** https://bugs.launchpad.net/bugs/1158684 ** This bug is no longer a duplicate of bug 1161015 terminating nova instance always terminates quantum port. ** This bug has been marked a duplicate of bug 1158684 Pre-created ports get deleted on VM delete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1217750 Title: Port not released after the instance is deleted Status in neutron: New Status in OpenStack Compute (nova): New Bug description: I launched an instance with the command "nova boot --image image-id --flavor 1 --nic port-id=port-id vm-name1" and deleted this instance. I ran the same command again and a message prompt in the command line, telling me that "ERROR: Port id 4ffb4e17-f701-4644-8699-de6226e9beaa could not be found. (HTTP 400) (Request-ID: req-ce6b4152-f1f8-4258-8e42-96457aa2846c) ". However, the reality is the instance has already been deleted. I think it is an issue with the port release. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1217750/+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 1161015] Re: terminating nova instance always terminates quantum port.
*** This bug is a duplicate of bug 1158684 *** https://bugs.launchpad.net/bugs/1158684 ** This bug has been marked a duplicate of bug 1158684 Pre-created ports get deleted on VM delete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1161015 Title: terminating nova instance always terminates quantum port. Status in neutron: Incomplete Bug description: I created a port provisioned a instance using this port Now when i terminate the instance nova automatically deletes/terminates the port. Is this a right behavior ? In my opinion since nova instance creation api was given the port_id it shoudnt terminate the port, since some one might want to reuse the port To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1161015/+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 1509924] [NEW] Tempest needs to test DHCPv6 stateful
Public bug reported: Currently there are no tests for DHCPv6 stateful IPv6 configurations, due to a bug in Cirros, which does not have support for DHCPv6 https://bugs.launchpad.net/cirros/+bug/1487041 Work needs to be done in Tempest to select an image that has DHCPv6 stateful support. ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) Status: New ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) ** Description changed: Currently there are no tests for DHCPv6 stateful IPv6 configurations, due to a bug in Cirros, which does not have support for DHCPv6 https://bugs.launchpad.net/cirros/+bug/1487041 + + Work needs to be done in Tempest to select an image that has DHCPv6 + stateful support. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1509924 Title: Tempest needs to test DHCPv6 stateful Status in neutron: New Bug description: Currently there are no tests for DHCPv6 stateful IPv6 configurations, due to a bug in Cirros, which does not have support for DHCPv6 https://bugs.launchpad.net/cirros/+bug/1487041 Work needs to be done in Tempest to select an image that has DHCPv6 stateful support. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1509924/+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 1377841] Re: Instances won't obtain IPv6 address and gateway when using SLAAC provided by OpenStack
You must attach a router to the network when ipv6_address_mode is set to "slaac" for instances to get addresses. You specified via the API that you want openstack to use stateless auto address configuration, and that requires a router to transmit RAs. ** 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/1377841 Title: Instances won't obtain IPv6 address and gateway when using SLAAC provided by OpenStack Status in neutron: Invalid Bug description: Description of problem: === I Created an IPv6 subnet with: 1. ipv6_ra_mode: slaac 2. ipv6_address_mode: slaac Version-Release number of selected component (if applicable): = openstack-neutron-2014.2-0.7.b3 How reproducible: = 100% Steps to Reproduce: === 1. create a neutron network 2. create an IPv6 subnet: # neutron subnet-create2001:db1::/64 --name usecase1_ipv6_slaac --ipv6-address-mode slaac --ipv6_ra_mode slaac --ip-version 6 3. boot an instance with that network Actual results: === 1. Instance did not obtain IPv6 address 2. default gw is not set Expected results: = The instance should have IPv6 address a default gw configured. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1377841/+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 1504647] [NEW] Ensure new interface hashing does not break upgrades
Public bug reported: Code introduced in https://review.openstack.org/#/c/224064/ touches code that did the interface name hashing. Let's ensure that it doesn't break upgrades. IRC conversation: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron /%23openstack-neutron.2015-10-09.log.html#t2015-10-09T16:26:18 ** Affects: neutron Importance: High Status: Confirmed ** Tags: linuxbridge -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504647 Title: Ensure new interface hashing does not break upgrades Status in neutron: Confirmed Bug description: Code introduced in https://review.openstack.org/#/c/224064/ touches code that did the interface name hashing. Let's ensure that it doesn't break upgrades. IRC conversation: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron /%23openstack-neutron.2015-10-09.log.html#t2015-10-09T16:26:18 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504647/+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 1484196] Re: Re-enable test_firewall_insertion_mode_add_remove_router FwaaS test
Fix was committed during the Liberty cycle, with https://review.openstack.org/#/c/212145/ ** Changed in: neutron Status: New => Fix Committed ** Changed in: neutron Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484196 Title: Re-enable test_firewall_insertion_mode_add_remove_router FwaaS test Status in neutron: Fix Released Bug description: After we resolve whatever is causing #1483875 https://review.openstack.org/#/c/211979/1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1484196/+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 1500960] [NEW] Decouple FwaaS from L3 Agent
Public bug reported: The FwaaS code is tightly coupled to the L3 agent, which is a concern because in CI we need to eliminate circular dependencies. ** 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/1500960 Title: Decouple FwaaS from L3 Agent Status in neutron: New Bug description: The FwaaS code is tightly coupled to the L3 agent, which is a concern because in CI we need to eliminate circular dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1500960/+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 1490885] [NEW] Neutron should not accept invalid subnet CIDRs like '1/24'
Public bug reported: http://lists.openstack.org/pipermail/openstack- dev/2015-August/072610.html ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) 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/1490885 Title: Neutron should not accept invalid subnet CIDRs like '1/24' Status in neutron: In Progress Bug description: http://lists.openstack.org/pipermail/openstack- dev/2015-August/072610.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1490885/+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 1487599] [NEW] fwaas - ip_version and IP address conflicts are not raised
Public bug reported: The FwaaS API currently allows the creation of firewall rules where the IP version is 4 but the source and destination IPs are IPv6 addresses. http://paste.openstack.org/show/412434/ This causes failures when a firewall is created, because iptables is being invoked with IPv6 addresses, which causes an exception in the iptables driver. ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) 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/1487599 Title: fwaas - ip_version and IP address conflicts are not raised Status in neutron: In Progress Bug description: The FwaaS API currently allows the creation of firewall rules where the IP version is 4 but the source and destination IPs are IPv6 addresses. http://paste.openstack.org/show/412434/ This causes failures when a firewall is created, because iptables is being invoked with IPv6 addresses, which causes an exception in the iptables driver. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1487599/+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 1485795] [NEW] fwaas unit tests for the API extension are not runnable
Public bug reported:
When running tox in the neutron-fwaas repo, none of the unit tests are
executed under /tests/unit/extensions are run.
When forcing it to run by overriding
OS_TEST_PATH=./neutron_fwaas/tests/unit/extensions - the following error
occurs.
scollins@Sean-Collins-MBPr15 ~/src/openstack/neutron-fwaas ⚡ » tox -e py27
py27 develop-inst-nodeps: /Users/scollins/src/openstack/neutron-fwaas
py27 runtests: PYTHONHASHSEED='483791098'
py27 runtests: commands[0] | sh tools/pretty_tox.sh
running testr
Traceback (most recent call last):
File
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
line 72, in _run_code
exec code in run_globals
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/subunit/run.py",
line 149, in
main()
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/subunit/run.py",
line 145, in main
stdout=stdout, exit=False)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/testtools/run.py",
line 171, in __init__
self.parseArgs(argv)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/unittest2/main.py",
line 113, in parseArgs
self._do_discovery(argv[2:])
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/testtools/run.py",
line 211, in _do_discovery
super(TestProgram, self)._do_discovery(argv, Loader=Loader)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/unittest2/main.py",
line 223, in _do_discovery
self.test = loader.discover(self.start, self.pattern, self.top)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
line 364, in discover
raise ImportError('Start directory is not importable: %r' % start_dir)
ImportError: Start directory is not importable:
'/Users/scollins/src/openstack/neutron-fwaas/neutron_fwaas/tests/unit/extensions'
Non-zero exit code (1) from test listing.
error: testr failed (3)
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1
${PYTHON:-python} -m subunit.run discover -t ./
${OS_TEST_PATH:-./neutron_fwaas/tests/unit} --list
The test run didn't actually run any tests
ERROR: InvocationError: '/bin/sh tools/pretty_tox.sh '
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
Status: In Progress
** Tags: fwaas
** Tags added: fwaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1485795
Title:
fwaas unit tests for the API extension are not runnable
Status in neutron:
In Progress
Bug description:
When running tox in the neutron-fwaas repo, none of the unit tests are
executed under /tests/unit/extensions are run.
When forcing it to run by overriding
OS_TEST_PATH=./neutron_fwaas/tests/unit/extensions - the following
error occurs.
scollins@Sean-Collins-MBPr15 ~/src/openstack/neutron-fwaas ⚡ » tox -e py27
py27 develop-inst-nodeps: /Users/scollins/src/openstack/neutron-fwaas
py27 runtests: PYTHONHASHSEED='483791098'
py27 runtests: commands[0] | sh tools/pretty_tox.sh
running testr
Traceback (most recent call last):
File
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
line 72, in _run_code
exec code in run_globals
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/subunit/run.py",
line 149, in
main()
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/subunit/run.py",
line 145, in main
stdout=stdout, exit=False)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/testtools/run.py",
line 171, in __init__
self.parseArgs(argv)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/unittest2/main.py",
line 113, in parseArgs
self._do_discovery(argv[2:])
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/py27/lib/python2.7/site-packages/testtools/run.py",
line 211, in _do_discovery
super(TestProgram, self)._do_discovery(argv, Loader=Loader)
File
"/Users/scollins/src/openstack/neutron-fwaas
[Yahoo-eng-team] [Bug 1484196] [NEW] Re-enable test_firewall_insertion_mode_add_remove_router FwaaS test
Public bug reported: After we resolve whatever is causing #1483875 https://review.openstack.org/#/c/211979/1 ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) Status: New ** Tags: fwaas ** Tags added: fwaas ** Changed in: neutron Assignee: (unassigned) => Sean M. Collins (scollins) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484196 Title: Re-enable test_firewall_insertion_mode_add_remove_router FwaaS test Status in neutron: New Bug description: After we resolve whatever is causing #1483875 https://review.openstack.org/#/c/211979/1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1484196/+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 1483875] [NEW] FWaaS - firewall deleted unexpectedly by agent
Public bug reported: q-svc log entries 2015-08-11 18:16:06.041 WARNING neutron_fwaas.services.firewall.fwaas_plugin [req- 9e82a535-e233-4190-8bb2-d40476291cd0 FWaaSExtensionTestJSON-1654170307 FWaaSExtensionTestJSON-582089387] Firewall 2d586bfd-a8ae-431d-b88b- 7169520de59d unexpectedly deleted by agent, status was ACTIVE q-agt log: 2015-08-11 18:17:29.409 10414 DEBUG neutron.agent.linux.utils [-] Running command (rootwrap daemon): ['ip', 'netns', 'exec', 'qrouter-543f9f00-3b3e-4683-8659-8fb6b4a986a8', 'ip', '-6', 'route', 'replace', 'default', 'via', '2001:db8::2', 'dev', 'qg-bfc277d3-a2'] execute_rootwrap_daemon /opt/stack/new/neutron/neutron/agent/linux/utils.py:101 2015-08-11 18:17:29.449 DEBUG neutron.agent.l3.agent [req-5784cb5d-5ca4-4fa2-b804-e6a7acf8eec2 RoutersIpV6Test-1482608198 RoutersIpV6Test-1725884989] Got routers updated notification :[u'8b0f2f15-c8b4-4bc2-9e74-d713b7acb917'] routers_updated /opt/stack/new/neutron/neutron/agent/l3/agent.py:371 2015-08-11 18:17:29.450 10414 DEBUG neutron.agent.l3.agent [-] Starting router update for 8b0f2f15-c8b4-4bc2-9e74-d713b7acb917, action None, priority 0 _process_router_update /opt/stack/new/neutron/neutron/agent/l3/agent.py:442 2015-08-11 18:17:29.450 10414 DEBUG oslo_messaging._drivers.amqpdriver [-] MSG_ID is 1b13de7d03104d96b4324b5328454e3d _send /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:392 2015-08-11 18:17:29.452 DEBUG neutron_fwaas.services.firewall.drivers.linux.iptables_fwaas [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Updating firewall 2d586bfd-a8ae-431d-b88b-7169520de59d for tenant 0c0cac5e07754eb1be4d747a6865ccee) update_firewall /opt/stack/new/neutron-fwaas/neutron_fwaas/services/firewall/drivers/linux/iptables_fwaas.py:112 2015-08-11 18:17:29.452 DEBUG neutron.agent.linux.iptables_manager [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Attempted to remove chain iv42d586bfd which does not exist remove_chain /opt/stack/new/neutron/neutron/agent/linux/iptables_manager.py:170 2015-08-11 18:17:29.452 DEBUG neutron.agent.linux.iptables_manager [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Attempted to remove chain ov42d586bfd which does not exist remove_chain /opt/stack/new/neutron/neutron/agent/linux/iptables_manager.py:170 2015-08-11 18:17:29.452 DEBUG neutron.agent.linux.iptables_manager [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Attempted to remove chain iv62d586bfd which does not exist remove_chain /opt/stack/new/neutron/neutron/agent/linux/iptables_manager.py:170 2015-08-11 18:17:29.452 DEBUG neutron.agent.linux.iptables_manager [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Attempted to remove chain ov62d586bfd which does not exist remove_chain /opt/stack/new/neutron/neutron/agent/linux/iptables_manager.py:170 2015-08-11 18:17:29.453 DEBUG neutron.agent.linux.iptables_manager [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Attempted to remove chain fwaas-defau which does not exist remove_chain /opt/stack/new/neutron/neutron/agent/linux/iptables_manager.py:170 2015-08-11 18:17:29.453 DEBUG neutron.agent.linux.iptables_manager [req-c8ebb00d-2415-4b8d-b647-2a1efd1f0fbb None None] Attempted to remove chain fwaas-defau which does not exist remove_chain /opt/stack/new/neutron/neutron/agent/linux/iptables_manager.py:170 Kibana query: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwidGVhckRvd25DbGFzcyAobmV1dHJvbi50ZXN0cy5hcGkudGVzdF9md2Fhc19leHRlbnNpb25zLkZXYWFTRXh0ZW5zaW9uVGVzdEpTT04pXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjQzMjAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQzOTMyMjE4Nzg0M30= ** Affects: neutron Importance: Undecided Status: New ** Tags: fwaas ** Tags added: fwaas ** Description changed: q-svc log entries - 2015-08-11 18:16:06.041 WARNING neutron_fwaas.services.firewall.fwaas_plugin [req-9e82a535-e233-4190-8bb2-d40476291cd0 FWaaSExtensionTestJSON-1654170307 FWaaSExtensionTestJSON-582089387] Firewall 2d586bfd-a8ae-431d-b88b-7169520de59d unexpectedly deleted by agent, status was ACTIVE + + 2015-08-11 18:16:06.041 WARNING + neutron_fwaas.services.firewall.fwaas_plugin [req- + 9e82a535-e233-4190-8bb2-d40476291cd0 FWaaSExtensionTestJSON-1654170307 + FWaaSExtensionTestJSON-582089387] Firewall 2d586bfd-a8ae-431d-b88b- + 7169520de59d unexpectedly deleted by agent, status was ACTIVE q-agt log: - http://paste.openstack.org/show/412604/ + 2015-08-11 18:17:29.409 10414 DEBUG neutron.agent.linux.utils [-] Running command (rootwrap daemon): ['ip', 'netns', 'exec', 'qrouter-543f9f00-3b3e-4683-8659-8fb6b4a986a8', 'ip', '-6', 'route', 'replace', 'default', 'via', '2001:db8::2', 'dev', 'qg-bfc277d3-a2'] execute_rootwrap_daemon /opt/stack/new/neutron/neutron/agent/linux/utils.py:101 + 2015-08-11 18:17:29.449 DEBUG neutron.agent.l3.agent [req-5784cb5d-5ca4-4fa2-b804-e6a7acf8eec2 RoutersIpV6Test-1482608198 RoutersIpV6Test-1725884989] Got r
[Yahoo-eng-team] [Bug 1483387] [NEW] neutron-fwaas needs oslotest
Public bug reported:
scollins@Sean-Collins-MBPr15 ~/src/openstack/neutron-fwaas ±ipv6_validate⚡ »
tox -e functional
functional develop-inst-nodeps: /Users/scollins/src/openstack/neutron-fwaas
functional runtests: PYTHONHASHSEED='2715531808'
functional runtests: commands[0] | python setup.py testr --slowest --testr-args=
running testr
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1
${PYTHON:-python} -m subunit.run discover -t ./
${OS_TEST_PATH:-./neutron_fwaas/tests/unit} --list
No handlers could be found for logger "neutron.quota"
--- import errors ---
Failed to import test module: neutron_fwaas.tests.functional.test_fwaas_driver
Traceback (most recent call last):
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/lib/python2.7/site-packages/unittest2/loader.py",
line 456, in _find_test_path
module = self._get_module_from_name(name)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/lib/python2.7/site-packages/unittest2/loader.py",
line 395, in _get_module_from_name
__import__(name)
File "neutron_fwaas/tests/functional/test_fwaas_driver.py", line 19, in
from neutron.tests.functional import base
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/src/neutron/neutron/tests/functional/base.py",
line 23, in
from neutron.tests.common import base as common_base
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/src/neutron/neutron/tests/common/base.py",
line 17, in
from oslo_db.sqlalchemy import test_base
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_base.py",
line 23, in
raise NameError('Oslotest is not installed. Please add oslotest in your'
NameError: Oslotest is not installed. Please add oslotest in your
test-requirements
Non-zero exit code (2) from test listing.
error: testr failed (3)
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
Status: In Progress
** Tags: fwaas
** Tags added: fwaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1483387
Title:
neutron-fwaas needs oslotest
Status in neutron:
In Progress
Bug description:
scollins@Sean-Collins-MBPr15 ~/src/openstack/neutron-fwaas ±ipv6_validate⚡ »
tox -e functional
functional develop-inst-nodeps: /Users/scollins/src/openstack/neutron-fwaas
functional runtests: PYTHONHASHSEED='2715531808'
functional runtests: commands[0] | python setup.py testr --slowest
--testr-args=
running testr
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1
${PYTHON:-python} -m subunit.run discover -t ./
${OS_TEST_PATH:-./neutron_fwaas/tests/unit} --list
No handlers could be found for logger "neutron.quota"
--- import errors ---
Failed to import test module: neutron_fwaas.tests.functional.test_fwaas_driver
Traceback (most recent call last):
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/lib/python2.7/site-packages/unittest2/loader.py",
line 456, in _find_test_path
module = self._get_module_from_name(name)
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/lib/python2.7/site-packages/unittest2/loader.py",
line 395, in _get_module_from_name
__import__(name)
File "neutron_fwaas/tests/functional/test_fwaas_driver.py", line 19, in
from neutron.tests.functional import base
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/src/neutron/neutron/tests/functional/base.py",
line 23, in
from neutron.tests.common import base as common_base
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/src/neutron/neutron/tests/common/base.py",
line 17, in
from oslo_db.sqlalchemy import test_base
File
"/Users/scollins/src/openstack/neutron-fwaas/.tox/functional/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_base.py",
line 23, in
raise NameError('Oslotest is not installed. Please add oslotest in your'
NameError: Oslotest is not installed. Please add oslotest in your
test-requirements
Non-zero exit code (2) from test listing.
error: testr failed (3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1483387/+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 1480698] [NEW] MySQL error - too many connections
Public bug reported: http://logs.openstack.org/59/138659/33/check/gate-tempest-dsvm-neutron- linuxbridge/29e7adc/logs/screen-n-api.txt.gz?level=ERROR 2015-07-21 11:29:53.660 ERROR nova.api.ec2 [req-522a314d- e88e-4982-b014-64141aeef73a tempest-EC2KeysTest-362858920 tempest- EC2KeysTest-451984995] Unexpected OperationalError raised: (_mysql_exceptions.OperationalError) (1040, 'Too many connections') ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1480698 Title: MySQL error - too many connections Status in OpenStack Compute (nova): New Bug description: http://logs.openstack.org/59/138659/33/check/gate-tempest-dsvm- neutron-linuxbridge/29e7adc/logs/screen-n-api.txt.gz?level=ERROR 2015-07-21 11:29:53.660 ERROR nova.api.ec2 [req-522a314d- e88e-4982-b014-64141aeef73a tempest-EC2KeysTest-362858920 tempest- EC2KeysTest-451984995] Unexpected OperationalError raised: (_mysql_exceptions.OperationalError) (1040, 'Too many connections') To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1480698/+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 1478072] Re: DVR enabled logic needs improvement
http://eavesdrop.openstack.org/irclogs/%23openstack-neutron
/%23openstack-neutron.2015-07-24.log.html#t2015-07-24T16:21:09
** Summary changed:
- DVR enabled on neutron jobs where DVR should be disabled
+ DVR enabled logic needs improvement
** 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/1478072
Title:
DVR enabled logic needs improvement
Status in neutron:
Invalid
Bug description:
Job: gate-tempest-dsvm-neutron-full
http://git.openstack.org/cgit/openstack-infra/project-
config/tree/jenkins/jobs/devstack-gate.yaml#n448
http://logs.openstack.org/77/198877/4/gate/gate-tempest-dsvm-neutron-
full/29bcccb/
Port ID: a84df1ca-0a43-4138-b60b-c4c5
2015-07-23 15:27:56.611 DEBUG neutron.db.l3_dvrscheduler_db [req-
b781d84a-1079-4328-b123-f4cb311c3a4f tempest-
AllowedAddressPairIpV6TestJSON-1876686975 tempest-
AllowedAddressPairIpV6TestJSON-178337704] No namespaces available for
this DVR port fd6aefa9-e1cb-4569-b7dc-1fb546e0d650 on host devstack-
trust
db/l3_dvrscheduler_db.py:LOG.debug('No namespaces
available for this DVR port %(port)s '
Maybe this check is not accurate enough?
https://github.com/openstack/neutron/blob/d266b5a90585634f91f3830b9f99af9dfaac5e31/neutron/plugins/ml2/plugin.py#L1307
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1478072/+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 1478072] [NEW] DVR enabled on neutron jobs where DVR should be disabled
Public bug reported:
Job: gate-tempest-dsvm-neutron-full
http://git.openstack.org/cgit/openstack-infra/project-
config/tree/jenkins/jobs/devstack-gate.yaml#n448
http://logs.openstack.org/77/198877/4/gate/gate-tempest-dsvm-neutron-
full/29bcccb/
Port ID: a84df1ca-0a43-4138-b60b-c4c5
2015-07-23 15:27:56.611 DEBUG neutron.db.l3_dvrscheduler_db [req-
b781d84a-1079-4328-b123-f4cb311c3a4f tempest-
AllowedAddressPairIpV6TestJSON-1876686975 tempest-
AllowedAddressPairIpV6TestJSON-178337704] No namespaces available for
this DVR port fd6aefa9-e1cb-4569-b7dc-1fb546e0d650 on host devstack-
trust
db/l3_dvrscheduler_db.py:LOG.debug('No namespaces available
for this DVR port %(port)s '
Maybe this check is not accurate enough?
https://github.com/openstack/neutron/blob/d266b5a90585634f91f3830b9f99af9dfaac5e31/neutron/plugins/ml2/plugin.py#L1307
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sean M. Collins (scollins)
** Description changed:
+ Job: gate-tempest-dsvm-neutron-full
+
+ http://git.openstack.org/cgit/openstack-infra/project-
+ config/tree/jenkins/jobs/devstack-gate.yaml#n448
+
http://logs.openstack.org/77/198877/4/gate/gate-tempest-dsvm-neutron-
full/29bcccb/
Port ID: a84df1ca-0a43-4138-b60b-c4c5
2015-07-23 15:27:56.611 DEBUG neutron.db.l3_dvrscheduler_db [req-
b781d84a-1079-4328-b123-f4cb311c3a4f tempest-
AllowedAddressPairIpV6TestJSON-1876686975 tempest-
AllowedAddressPairIpV6TestJSON-178337704] No namespaces available for
this DVR port fd6aefa9-e1cb-4569-b7dc-1fb546e0d650 on host devstack-
trust
db/l3_dvrscheduler_db.py:LOG.debug('No namespaces available
for this DVR port %(port)s '
-
Maybe this check is not accurate enough?
https://github.com/openstack/neutron/blob/d266b5a90585634f91f3830b9f99af9dfaac5e31/neutron/plugins/ml2/plugin.py#L1307
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1478072
Title:
DVR enabled on neutron jobs where DVR should be disabled
Status in neutron:
New
Bug description:
Job: gate-tempest-dsvm-neutron-full
http://git.openstack.org/cgit/openstack-infra/project-
config/tree/jenkins/jobs/devstack-gate.yaml#n448
http://logs.openstack.org/77/198877/4/gate/gate-tempest-dsvm-neutron-
full/29bcccb/
Port ID: a84df1ca-0a43-4138-b60b-c4c5
2015-07-23 15:27:56.611 DEBUG neutron.db.l3_dvrscheduler_db [req-
b781d84a-1079-4328-b123-f4cb311c3a4f tempest-
AllowedAddressPairIpV6TestJSON-1876686975 tempest-
AllowedAddressPairIpV6TestJSON-178337704] No namespaces available for
this DVR port fd6aefa9-e1cb-4569-b7dc-1fb546e0d650 on host devstack-
trust
db/l3_dvrscheduler_db.py:LOG.debug('No namespaces
available for this DVR port %(port)s '
Maybe this check is not accurate enough?
https://github.com/openstack/neutron/blob/d266b5a90585634f91f3830b9f99af9dfaac5e31/neutron/plugins/ml2/plugin.py#L1307
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1478072/+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 1470076] [NEW] Security Group Attributes that are documented as UUIDs require validation
Public bug reported: In the API, security_group_id and remote_group_id are documented as requiring UUIDs. ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) 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/1470076 Title: Security Group Attributes that are documented as UUIDs require validation Status in OpenStack Neutron (virtual network service): In Progress Bug description: In the API, security_group_id and remote_group_id are documented as requiring UUIDs. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1470076/+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 1467791] Re: Specific ipv4 subnet to create port and return port contains ipv4 and ipv6 address
** 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/1467791
Title:
Specific ipv4 subnet to create port and return port contains ipv4 and
ipv6 address
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
neutron --version
2.6.0
When a network named 'A' contains a ipv4 subnet and a ipv6 subnet with
ipv6_address_mode and ipv6_ra_mode are 'slaac'/'dhcpv6-stateless'. I
specify the ipv4 subnet without ipv4 addr to create a port based on
this network 'A'. The returned port contains 2 addresses (both ipv4
and ipv6).
It just like:
| fixed_ips | {"subnet_id":
"990f3f53-ee5b-4a6f-b362-34fc339ab6e5", "ip_address": "10.0.0.5"}
| | {"subnet_id":
"59464306-6781-4d33-b10c-214f4ba30e6c", "ip_address": "fd00:dd95:d03f:0:f81
But the result which expected is just :
| fixed_ips | {"subnet_id":
"990f3f53-ee5b-4a6f-b362-34fc339ab6e5", "ip_address": "10.0.0.5"}
repo:
1.create a network
2.create a ipv4 subnet and a ipv6 subnet into this network.And specify
ipv6_address_mode and ipv6_ra_mode are 'slaac'/'dhcpv6-stateless'.
3.run the command
neutron port-create --fixed-ip subnet_id=$[ipv4_subnet_id]
$[network_id/name]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1467791/+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 1468803] [NEW] Modular L2 Agent
Public bug reported: Currently, both the Open vSwitch and Linux Bridge mechanism drivers for the ML2 plugin have their own agents. This means that when improvements are made to one agent implementation, they have to be ported over to the other agent to gain the improvement. This has already happened, with patches like https://review.openstack.org/#/c/138512/ . Much of the functionality that both the OVS and Linux Bridge agents provide is common enough that much of the code could be shared. Discussion on the mailing list. http://lists.openstack.org/pipermail/openstack-dev/2015-June/067605.html ** Affects: neutron Importance: Undecided Status: New ** Tags: linuxbridge ovs 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/1468803 Title: Modular L2 Agent Status in OpenStack Neutron (virtual network service): New Bug description: Currently, both the Open vSwitch and Linux Bridge mechanism drivers for the ML2 plugin have their own agents. This means that when improvements are made to one agent implementation, they have to be ported over to the other agent to gain the improvement. This has already happened, with patches like https://review.openstack.org/#/c/138512/ . Much of the functionality that both the OVS and Linux Bridge agents provide is common enough that much of the code could be shared. Discussion on the mailing list. http://lists.openstack.org/pipermail/openstack- dev/2015-June/067605.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1468803/+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 1467791] Re: Specific ipv4 subnet to create port and return port contains ipv4 and ipv6 address
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-
ipv6-prefixes.html#proposed-change is where this behavior is documented.
** 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/1467791
Title:
Specific ipv4 subnet to create port and return port contains ipv4 and
ipv6 address
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
neutron --version
2.6.0
When a network named 'A' contains a ipv4 subnet and a ipv6 subnet with
ipv6_address_mode and ipv6_ra_mode are 'slaac'/'dhcpv6-stateless'. I
specify the ipv4 subnet without ipv4 addr to create a port based on
this network 'A'. The returned port contains 2 addresses (both ipv4
and ipv6).
It just like:
| fixed_ips | {"subnet_id":
"990f3f53-ee5b-4a6f-b362-34fc339ab6e5", "ip_address": "10.0.0.5"}
| | {"subnet_id":
"59464306-6781-4d33-b10c-214f4ba30e6c", "ip_address": "fd00:dd95:d03f:0:f81
But the result which expected is just :
| fixed_ips | {"subnet_id":
"990f3f53-ee5b-4a6f-b362-34fc339ab6e5", "ip_address": "10.0.0.5"}
repo:
1.create a network
2.create a ipv4 subnet and a ipv6 subnet into this network.And specify
ipv6_address_mode and ipv6_ra_mode are 'slaac'/'dhcpv6-stateless'.
3.run the command
neutron port-create --fixed-ip subnet_id=$[ipv4_subnet_id]
$[network_id/name]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1467791/+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 1465837] [NEW] Dnsmasq is being passed None as an interface
Public bug reported: Command: ['ip', 'netns', 'exec', u'qdhcp-8faea227-4ae4-498d- bfc4-d6e656c77f81', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict- order', '--bind-interfaces', '--interface=None', '--except- interface=lo', u'--pid-file=/opt/stack/data/neutron/dhcp/8faea227-4ae4 -498d-bfc4-d6e656c77f81/pid', u'--dhcp- hostsfile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/host', u'--addn- hosts=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/addn_hosts', u'--dhcp- optsfile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/opts', u'--dhcp- leasefile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/leases', '--dhcp- range=set:tag0,10.100.0.0,static,86400s', '--dhcp- range=set:tag1,2003::,static,64,86400s', '--dhcp-lease-max=16777216', '--conf-file=', '--domain=openstacklocal'] http://logs.openstack.org/35/187235/3/experimental/check-tempest-dsvm- neutron-linuxbridge/35c6dac/logs/screen-q-dhcp.txt.gz?level=ERROR DevStack Configuration: http://git.openstack.org/cgit/openstack-infra/project- config/tree/jenkins/jobs/neutron.yaml#n182 ** Affects: neutron Importance: Undecided Status: New ** Tags: ipv6 linuxbridge ** Tags added: ipv6 linuxbridge ** Description changed: + Command: ['ip', 'netns', 'exec', u'qdhcp-8faea227-4ae4-498d- + bfc4-d6e656c77f81', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict- + order', '--bind-interfaces', '--interface=None', '--except- + interface=lo', u'--pid-file=/opt/stack/data/neutron/dhcp/8faea227-4ae4 + -498d-bfc4-d6e656c77f81/pid', u'--dhcp- + hostsfile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- + bfc4-d6e656c77f81/host', u'--addn- + hosts=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- + bfc4-d6e656c77f81/addn_hosts', u'--dhcp- + optsfile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- + bfc4-d6e656c77f81/opts', u'--dhcp- + leasefile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- + bfc4-d6e656c77f81/leases', '--dhcp- + range=set:tag0,10.100.0.0,static,86400s', '--dhcp- + range=set:tag1,2003::,static,64,86400s', '--dhcp-lease-max=16777216', + '--conf-file=', '--domain=openstacklocal'] http://logs.openstack.org/35/187235/3/experimental/check-tempest-dsvm- neutron-linuxbridge/35c6dac/logs/screen-q-dhcp.txt.gz?level=ERROR -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1465837 Title: Dnsmasq is being passed None as an interface Status in OpenStack Neutron (virtual network service): New Bug description: Command: ['ip', 'netns', 'exec', u'qdhcp-8faea227-4ae4-498d- bfc4-d6e656c77f81', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict- order', '--bind-interfaces', '--interface=None', '--except- interface=lo', u'--pid-file=/opt/stack/data/neutron/dhcp/8faea227-4ae4 -498d-bfc4-d6e656c77f81/pid', u'--dhcp- hostsfile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/host', u'--addn- hosts=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/addn_hosts', u'--dhcp- optsfile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/opts', u'--dhcp- leasefile=/opt/stack/data/neutron/dhcp/8faea227-4ae4-498d- bfc4-d6e656c77f81/leases', '--dhcp- range=set:tag0,10.100.0.0,static,86400s', '--dhcp- range=set:tag1,2003::,static,64,86400s', '--dhcp-lease-max=16777216', '--conf-file=', '--domain=openstacklocal'] http://logs.openstack.org/35/187235/3/experimental/check-tempest-dsvm- neutron-linuxbridge/35c6dac/logs/screen-q-dhcp.txt.gz?level=ERROR DevStack Configuration: http://git.openstack.org/cgit/openstack-infra/project- config/tree/jenkins/jobs/neutron.yaml#n182 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1465837/+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 1464023] [NEW] XML namespaces for API extensions have been deprecated
Public bug reported: The namespaces that are used in Neutron API extensions are not really used anymore - and can be removed from the codebase http://lists.openstack.org/pipermail/openstack-dev/2015-June/066219.html ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) 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/1464023 Title: XML namespaces for API extensions have been deprecated Status in OpenStack Neutron (virtual network service): In Progress Bug description: The namespaces that are used in Neutron API extensions are not really used anymore - and can be removed from the codebase http://lists.openstack.org/pipermail/openstack- dev/2015-June/066219.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1464023/+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 1358297] Re: Port doesn't receive IP SLAAC in subnets with Router advertisements without dnsmasq
** 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/1358297
Title:
Port doesn't receive IP SLAAC in subnets with Router advertisements
without dnsmasq
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
When creating network and subnet of IPv6 with arguments: --ipv6-ra-
mode=slaac or --ipv6-ra-mode=dhcp-stateless and without
ipv6_address_mode set, the created port doesn't receive SLLAC IPv6
address, but one of fixed IPs.
For example:
Let's create network and subnet:
~$ neutron net-create net12
Created a new network:
...
~$ neutron subnet-create --name=subnet-net12 --ipv6-ra-mode=slaac
--ip-version=6 net12 2004::/64
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2004::2", "end":
"2004:::::fffe"} |
| cidr | 2004::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2004::1
|
| host_routes |
|
| id| 81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode | slaac
|
| name | subnet-net12
|
...
~$ neutron router-create router1
Created a new router:
...
~$ neutron router-interface-add 2ca34fba-258f-4395-95b0-4fe32e4f19b7
81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc
Added interface af8ac8d5-9461-4998-b561-007e3646f53f to router
2ca34fba-258f-4395-95b0-4fe32e4f19b7.
Now should be Router Advertisements in the network which should propagate /64
subnet mask for all hosts.
Created port now should receive SLAAC address and mask from RAs. But:
localadmin@devstack-server:~$ neutron port-create net12
Created a new port:
+---++
| Field | Value
|
+---++
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:vnic_type | normal
|
| device_id |
|
| device_owner |
|
| fixed_ips | {"subnet_id":
"81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc", "ip_address": "2004::2"} |
| id| 956d0c15-8ba4-473d-9674-a74d4cf19a47
|
| mac_address | fa:16:3e:4b:14:2b
|
| name |
|
| network_id| b9bfb75a-8908-4fbf-a771-74ec345a0ee4
|
| security_groups | 5c0d2c99-65a4-497c-a5c4-3cb241f669f4
|
| status| DOWN
|
| tenant_id | 74267b5732114ca1a11b7e2849156363
|
+---++
Port receives IP from defualt fixed IP range, it means SLAAC doesn't work.
The same thing with ra_mode=dhcpv6-stateless and add_mode=None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1358297/+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 1459880] [NEW] IP Address length only needs to be 45 chars long
Public bug reported: Currently, Neutron defines the ipallocations table's ip_address column as String(64). IPv4 addresses are 15 chars long, while IPv6 addresses are 39. The longest IP address possible is an IPv4 mapped IPv6 address, that is 45 characters long. ** Affects: neutron Importance: Undecided Assignee: Sean M. Collins (scollins) 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/1459880 Title: IP Address length only needs to be 45 chars long Status in OpenStack Neutron (virtual network service): In Progress Bug description: Currently, Neutron defines the ipallocations table's ip_address column as String(64). IPv4 addresses are 15 chars long, while IPv6 addresses are 39. The longest IP address possible is an IPv4 mapped IPv6 address, that is 45 characters long. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1459880/+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 1438707] Re: Security Group API is undocumented in neutron-specs
** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1438707 Title: Security Group API is undocumented in neutron-specs Status in OpenStack Neutron (virtual network service): New Bug description: http://specs.openstack.org/openstack/neutron-specs/specs/api /security_groups_and_rules__security-groups_.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1438707/+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 1438502] [NEW] XStatic-Angular-Irdragndrop dependency is failing
Public bug reported: http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiQ291bGQgbm90IGluc3RhbGwgcmVxdWlyZW1lbnQgWFN0YXRpYy1Bbmd1bGFyLUlyZHJhZ25kcm9wPj0xLjAuMi4xXCIgQU5EIHRhZ3M6Y29uc29sZSIsInRpbWVmcmFtZSI6IjkwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQyNzc3MzYwMDQ2M30= ** 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/1438502 Title: XStatic-Angular-Irdragndrop dependency is failing Status in OpenStack Dashboard (Horizon): New Bug description: http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiQ291bGQgbm90IGluc3RhbGwgcmVxdWlyZW1lbnQgWFN0YXRpYy1Bbmd1bGFyLUlyZHJhZ25kcm9wPj0xLjAuMi4xXCIgQU5EIHRhZ3M6Y29uc29sZSIsInRpbWVmcmFtZSI6IjkwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQyNzc3MzYwMDQ2M30= To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1438502/+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 1377985] Re: IPv6 Router Advertisments should be allowed by default
If I read this correctly, this bug is saying we should allow RAs from anywhere, which is opposite of the consensus in bug #1262759 ** Changed in: neutron Status: In Progress => Invalid ** Changed in: neutron Status: Invalid => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1377985 Title: IPv6 Router Advertisments should be allowed by default Status in OpenStack Neutron (virtual network service): Opinion Bug description: Description of problem: === Router Advertisments are blocked and can't reach instances. As a direct result of that, All Ipv6 networking won't function for instances. This was tested both with provider Ipv6 router and radvd. Version-Release number of selected component (if applicable): = openstack-neutron-2014.2-0.7.b3 How reproducible: = 100% Steps to Reproduce: === 1. Create Neutron network 2. Create Neutron IPv6 subnet, don't foreget to speficy: a. --ipv6-address-mode b. --ipv6_ra_mode c. --gateway , in case you create this subnet for provider router. speficy the IPv6 link local address. 3. Spawn an instance 4. Check if the instance obtained IPv6 address and defeault gw. (not expected to work) 5. Use tcpdump to see if Router Advertisments reach the instance. 6. Add a rule to allow all ICMP from fe80::/4 7. Repeat steps 4 & 5, it should work ok now. Actual results: === Router Advertisments are blocked and can't reach instances. Expected results: = Router Advertisments should be allowed by default. Additional Info: Might be related to: https://review.openstack.org/#/c/72252/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1377985/+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 1401728] [NEW] Routing updates lost when multiple IPs attached to router
Public bug reported: When attempting to run dual stacked networking at the gate (https://review.openstack.org/#/c/140128/), IPv4 networking breaks, with Tempest scenarios reporting no route to host errors for the floating IPs that tempest attempts to SSH into. The following errors are reported in the l3 agent log: 2014-12-11 23:19:58.393 25977 ERROR neutron.agent.l3.agent [-] Ignoring multiple IPs on router port db0953d3-4bd1-4106-9efc-c16cd9a3e922 2014-12-11 23:19:58.393 25977 ERROR neutron.agent.l3.agent [-] 'subnet' 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent Traceback (most recent call last): 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent File "/opt/stack/new/neutron/neutron/common/utils.py", line 341, in call 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent return func(*args, **kwargs) 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 646, in process_router 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent self._set_subnet_info(ex_gw_port) 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 562, in _set_subnet_info 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent prefixlen = netaddr.IPNetwork(port['subnet']['cidr']).prefixlen 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent KeyError: 'subnet' 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/eventlet/greenpool.py", line 82, in _spawn_n_impl func(*args, **kwargs) File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 1537, in _process_router_update self._process_router_if_compatible(router) File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 1512, in _process_router_if_compatible self.process_router(ri) File "/opt/stack/new/neutron/neutron/common/utils.py", line 344, in call self.logger(e) File "/usr/local/lib/python2.7/dist-packages/oslo/utils/excutils.py", line 82, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/opt/stack/new/neutron/neutron/common/utils.py", line 341, in call return func(*args, **kwargs) File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 646, in process_router self._set_subnet_info(ex_gw_port) File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 562, in _set_subnet_info prefixlen = netaddr.IPNetwork(port['subnet']['cidr']).prefixlen KeyError: 'subnet' http://logs.openstack.org/28/140128/4/check/check-tempest-dsvm-neutron- full/440ec4e/logs/screen-q-l3.txt.gz Tempest reports no route to host: 2014-12-11 22:57:04.385 30680 WARNING tempest.common.ssh [-] Failed to establish authenticated ssh connection to cirros@172.24.4.82 ([Errno 113] No route to host). Number attempts: 1. Retry after 2 seconds. http://logs.openstack.org/28/140128/4/check/check-tempest-dsvm-neutron- full/440ec4e/logs/tempest.txt.gz ** Affects: neutron Importance: Undecided Status: New ** Tags: ipv6 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1401728 Title: Routing updates lost when multiple IPs attached to router Status in OpenStack Neutron (virtual network service): New Bug description: When attempting to run dual stacked networking at the gate (https://review.openstack.org/#/c/140128/), IPv4 networking breaks, with Tempest scenarios reporting no route to host errors for the floating IPs that tempest attempts to SSH into. The following errors are reported in the l3 agent log: 2014-12-11 23:19:58.393 25977 ERROR neutron.agent.l3.agent [-] Ignoring multiple IPs on router port db0953d3-4bd1-4106-9efc-c16cd9a3e922 2014-12-11 23:19:58.393 25977 ERROR neutron.agent.l3.agent [-] 'subnet' 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent Traceback (most recent call last): 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent File "/opt/stack/new/neutron/neutron/common/utils.py", line 341, in call 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent return func(*args, **kwargs) 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 646, in process_router 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent self._set_subnet_info(ex_gw_port) 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent File "/opt/stack/new/neutron/neutron/agent/l3/agent.py", line 562, in _set_subnet_info 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent prefixlen = netaddr.IPNetwork(port['subnet']['cidr']).prefixlen 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent KeyError: 'subnet' 2014-12-11 23:19:58.393 25977 TRACE neutron.agent.l3.agent Traceback (most recent
[Yahoo-eng-team] [Bug 1358297] Re: Port doesn't receive IP SLAAC in subnets with Router advertisements without dnsmasq
@Sergey - that table in that spec you linked, the description is inaccurate.
Having ipv6_address_mode unset means that you have some *external* IPAM system
that OpenStack does not know about, that is assigning addresses to
ports/instances.
** 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/1358297
Title:
Port doesn't receive IP SLAAC in subnets with Router advertisements
without dnsmasq
Status in OpenStack Neutron (virtual network service):
New
Bug description:
When creating network and subnet of IPv6 with arguments: --ipv6-ra-
mode=slaac or --ipv6-ra-mode=dhcp-stateless and without
ipv6_address_mode set, the created port doesn't receive SLLAC IPv6
address, but one of fixed IPs.
For example:
Let's create network and subnet:
~$ neutron net-create net12
Created a new network:
...
~$ neutron subnet-create --name=subnet-net12 --ipv6-ra-mode=slaac
--ip-version=6 net12 2004::/64
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2004::2", "end":
"2004:::::fffe"} |
| cidr | 2004::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2004::1
|
| host_routes |
|
| id| 81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode | slaac
|
| name | subnet-net12
|
...
~$ neutron router-create router1
Created a new router:
...
~$ neutron router-interface-add 2ca34fba-258f-4395-95b0-4fe32e4f19b7
81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc
Added interface af8ac8d5-9461-4998-b561-007e3646f53f to router
2ca34fba-258f-4395-95b0-4fe32e4f19b7.
Now should be Router Advertisements in the network which should propagate /64
subnet mask for all hosts.
Created port now should receive SLAAC address and mask from RAs. But:
localadmin@devstack-server:~$ neutron port-create net12
Created a new port:
+---++
| Field | Value
|
+---++
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:vnic_type | normal
|
| device_id |
|
| device_owner |
|
| fixed_ips | {"subnet_id":
"81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc", "ip_address": "2004::2"} |
| id| 956d0c15-8ba4-473d-9674-a74d4cf19a47
|
| mac_address | fa:16:3e:4b:14:2b
|
| name |
|
| network_id| b9bfb75a-8908-4fbf-a771-74ec345a0ee4
|
| security_groups | 5c0d2c99-65a4-497c-a5c4-3cb241f669f4
|
| status| DOWN
|
| tenant_id | 74267b5732114ca1a11b7e2849156363
|
+---++
Port receives IP from defualt fixed IP range, it means SLAAC doesn't work.
The same thing with ra_mode=dhcpv6-stateless and add_mode=None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1358297/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post
[Yahoo-eng-team] [Bug 1358297] Re: Port doesn't receive IP SLAAC in subnets with Router advertisements without dnsmasq
What we probably should do, is create a patch that when
ipv6_address_mode is unset, but the ipv6_ra_mode attribute is set, is to
not allocate an IPv6 address to the port?
** Changed in: neutron
Status: Invalid => 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/1358297
Title:
Port doesn't receive IP SLAAC in subnets with Router advertisements
without dnsmasq
Status in OpenStack Neutron (virtual network service):
New
Bug description:
When creating network and subnet of IPv6 with arguments: --ipv6-ra-
mode=slaac or --ipv6-ra-mode=dhcp-stateless and without
ipv6_address_mode set, the created port doesn't receive SLLAC IPv6
address, but one of fixed IPs.
For example:
Let's create network and subnet:
~$ neutron net-create net12
Created a new network:
...
~$ neutron subnet-create --name=subnet-net12 --ipv6-ra-mode=slaac
--ip-version=6 net12 2004::/64
+---+--+
| Field | Value
|
+---+--+
| allocation_pools | {"start": "2004::2", "end":
"2004:::::fffe"} |
| cidr | 2004::/64
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| 2004::1
|
| host_routes |
|
| id| 81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode | slaac
|
| name | subnet-net12
|
...
~$ neutron router-create router1
Created a new router:
...
~$ neutron router-interface-add 2ca34fba-258f-4395-95b0-4fe32e4f19b7
81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc
Added interface af8ac8d5-9461-4998-b561-007e3646f53f to router
2ca34fba-258f-4395-95b0-4fe32e4f19b7.
Now should be Router Advertisements in the network which should propagate /64
subnet mask for all hosts.
Created port now should receive SLAAC address and mask from RAs. But:
localadmin@devstack-server:~$ neutron port-create net12
Created a new port:
+---++
| Field | Value
|
+---++
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:vnic_type | normal
|
| device_id |
|
| device_owner |
|
| fixed_ips | {"subnet_id":
"81287be4-0d5a-4185-bdb4-4f3bcc6a0bdc", "ip_address": "2004::2"} |
| id| 956d0c15-8ba4-473d-9674-a74d4cf19a47
|
| mac_address | fa:16:3e:4b:14:2b
|
| name |
|
| network_id| b9bfb75a-8908-4fbf-a771-74ec345a0ee4
|
| security_groups | 5c0d2c99-65a4-497c-a5c4-3cb241f669f4
|
| status| DOWN
|
| tenant_id | 74267b5732114ca1a11b7e2849156363
|
+---++
Port receives IP from defualt fixed IP range, it means SLAAC doesn't work.
The same thing with ra_mode=dhcpv6-stateless and add_mode=None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1358297/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net
[Yahoo-eng-team] [Bug 1316190] [NEW] When IPv6 addresses are added to the dnsmasq host file, dnsmasq stops issuing leases
Public bug reported: When an IPv6 subnet is created, with ipv6_ra_mode not set, and ipv6_address_mode set to "slaac" - ipv6 addresses are added to the host file that dnsmasq uses, and this causes dnsmasq to cease responding to dhcp clients on the v4 side. ** Affects: neutron Importance: Undecided Status: New ** Tags: ipv6 ** Tags added: ipv6 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1316190 Title: When IPv6 addresses are added to the dnsmasq host file, dnsmasq stops issuing leases Status in OpenStack Neutron (virtual network service): New Bug description: When an IPv6 subnet is created, with ipv6_ra_mode not set, and ipv6_address_mode set to "slaac" - ipv6 addresses are added to the host file that dnsmasq uses, and this causes dnsmasq to cease responding to dhcp clients on the v4 side. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1316190/+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 1274992] [NEW] Utils.is_neutron can create race conditions
Public bug reported: It appears that using the utils.is_neutron() function can create race conditions, if not used carefully. Review #56381 was attempting to check the presence of Neutron, in order to determine if hairpinning should be enabled on the bridge that Nova creates. Only after creating a new configuration flag in Nova.conf and checking the setting, were the unit tests passing and the race condition resolved. My hunch is that the global variable that utils.is_neutron( ) creates is the root cause of the issue. https://review.openstack.org/#/c/56381/ ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1274992 Title: Utils.is_neutron can create race conditions Status in OpenStack Compute (Nova): New Bug description: It appears that using the utils.is_neutron() function can create race conditions, if not used carefully. Review #56381 was attempting to check the presence of Neutron, in order to determine if hairpinning should be enabled on the bridge that Nova creates. Only after creating a new configuration flag in Nova.conf and checking the setting, were the unit tests passing and the race condition resolved. My hunch is that the global variable that utils.is_neutron( ) creates is the root cause of the issue. https://review.openstack.org/#/c/56381/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1274992/+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 1252852] Re: ip6tables rules drops traffic that should be allowed
Appears to have been a problem with our configuration. Will re-open if the problem arises again. ** Changed in: neutron Status: In Progress => 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/1252852 Title: ip6tables rules drops traffic that should be allowed Status in OpenStack Neutron (virtual network service): Invalid Bug description: We're experiencing an issue, where ip6tables rules that should be allowing in SSH and HTTP traffic is not being accepted, and it appears that all traffic hits the neutron-openvswi-sg-fallback rule, and is evaluated to a DROP. ip6tables rules: http://paste.openstack.org/show/53144/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1252852/+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
