Public bug reported:
An example exception can be found in
http://paste.openstack.org/show/594276/ .
** Affects: neutron
Importance: High
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: gate-failure l3-ha
--
You received this bug notification because you are
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Importance: Undecided => Critical
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
** Changed in
Public bug reported:
When switching an ovs-agent from iptables to ovsfw, new instances will
be created using the ovsfw, but old instances will stick with iptables.
In fact, there isn't a way to migrate an instance from iptables to
ovsfw, and one should be provided.
Considerations:
a. It isn't eno
Public bug reported:
See [1] and [2] - console.html produce this line: "/bin/sh: 1: brctl:
not found" and the job fails early on.
[1]:
http://logs.openstack.org/99/407099/16/check/gate-tempest-dsvm-neutron-dvr-ubuntu-xenial/b28dcbd/console.html
[2]:
http://logs.openstack.org/99/407099/16/check/
** Also affects: neutron
Importance: Undecided
Status: New
** Tags added: gate-failure l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1649867
Title:
Gate tempes
(each triggers a SIGHUP), the master node will forfeit re-election
(causing it to switch to BACKUP, thus removing all the remaining FIP's
IPs and severing connectivity.
** Affects: neutron
Importance: High
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags:
x27;t switched
back to its non-HA counterpart. This can cause migration of the router
to DVR to not work properly as the snat interface isn't created.
A log and reproducible can be found in [1].
[1]: http://paste.openstack.org/show/590804/
** Affects: neutron
Importance: High
Assi
Status: Confirmed => Invalid
** Changed in: rally
Assignee: (unassigned) => John Schwarz (jschwarz)
** Changed in: rally
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https:/
No worries :) Glad we could help.
** Changed in: neutron
Status: Incomplete => Invalid
** Changed in: neutron
Importance: High => Undecided
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad
hub.com/openstack/neutron/blob/15d65607a47810f7d155d43902d358cb9f953a7a/neutron/agent/linux/utils.py#L176
** Affects: neutron
Importance: Critical
Assignee: John Schwarz (jschwarz)
Status: Confirmed
** Tags: mitaka-backport-potential newton-backport-potential
--
You received this bug notificati
Looking at the log involving the server ([1] - the same one you provided
in the first comment and in comment #3), and specifically lines 19 and
21, it's clear that sync_routers() is triggering
auto_schedule_routers(). Before [2] removed in, the call from
sync_routers() to auto_schedule_routers() wa
Adding a new configuration option is almost never temporary as deleting
config options is rarely backward-compatible.
The race condition, as I understand it, is as following:
1. Create HA router, have worker1 send 'router_updated' to agent1.
2. Delete HA router (done by worker2). worker2 will now
same
binding_index is being used by 2 different workers).
** Affects: neutron
Importance: Medium
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: l3-dvr-backlog l3-ha
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
Public bug reported:
Encountered in https://review.openstack.org/#/c/365326/8/, specifically
http://logs.openstack.org/26/365326/8/check/gate-neutron-dsvm-
functional-ubuntu-trusty/cc5f8eb/testr_results.html.gz
Stack trace from tempest (if the logs are deleted from the server):
http://paste.opens
This seems like a bug to me. I understand that it stands as a limitation
that keepalived always selects the higher-IP to be master, but then I
would expect the non-higher-IP nodes to revert to backups. If this isn't
the case (as it seems from what Ann and Gustavo write) then this is a
bug.
Reopeni
Looks like this is working as planned.
** 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/1621086
Title:
Port delete on router interface
Marking this as Incomplete seeing as how the no progress has been made
on the bug report or on the patch.
** 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:
This should have been mitigated by
https://review.openstack.org/#/c/364278/10/neutron/scheduler/l3_agent_scheduler.py@207
so I'm closing this.
** Changed in: neutron
Status: In Progress => Fix Released
** Changed in: neutron
Importance: Undecided => Medium
--
You received this bug not
Public bug reported:
As the title say:
2016-09-01 16:38:46.026 ERROR neutron.api.v2.resource
[req-d738cdb2-01bb-41a7-a2a9-534bf8b06377 admin
85a2b05da4be46b19bc5f7cf41055e45] update failed: No details.
2016-09-01 16:38:46.026 TRACE neutron.api.v2.resource Traceback (most recent
call last):
201
Public bug reported:
There is a new gate failure that can be found using the following
logstash query:
message:"One or more ports have an IP allocation from this subnet" &&
filename:"console.html" && build_queue:"gate"
This seems to be specific to DVR jobs and is separate from [1] (see
comment #
0.0.0.0/24 |
+--++--+
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: New
** Tags: l3-ha
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
--
You received this bug notificatio
]:
https://github.com/openstack/neutron/blob/ff5b38071e7e134baa0dc7a52280f9bcbc06efaf/neutron/db/l3_hamode_db.py#L570
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: New
** Tags: l3-ha
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
--
ffects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: New
** Tags: l3-ha
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whic
If this needs changing, the docimpact-group
option needs to be added for the project. You can ask the OpenStack infra team
(#openstack-infra on freenode) for help if you need to.
commit 42f4332a2b6c7aaeadc9c1bdc87f6d4bf4b662d7
Author: John Schwarz
Date: Mon Oct 12 16:54:17 2015 +0300
** Changed in: neutron
Status: New => Opinion
** Changed in: neutron
Status: Opinion => 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/1605282
Title:
Transaction
*** This bug is a duplicate of bug 1533457 ***
https://bugs.launchpad.net/bugs/1533457
** This bug is no longer a duplicate of bug 1605546
Race with deleting HA routers
** This bug has been marked a duplicate of bug 1533457
Neutron server unable to sync HA info after race between HA rout
As per comment #39, this can be closed - this bug report is mostly a
tracker bug and I'm under most of the races that made test_ha_router
fail are resolved.
Some other races are https://bugs.launchpad.net/neutron/+bug/1605285 and
https://bugs.launchpad.net/neutron/+bug/1605282, but these can be
ad
I've gone through all 5 of the initial reported problems. There are all
either fixed or referenced by other bugs:
1. DBReferenceError: referenced by
https://bugs.launchpad.net/neutron/+bug/1533460 and fixed by
https://review.openstack.org/#/c/260303/
2. AttributeError: referenced by
https://bugs.
I've gone through the 2 errors initially reported:
1. Concurrency issues with HA ports: fixed by
https://review.openstack.org/#/c/257059/ (introduction of the ALLOCATING
status for routers)
2. AttributeError: already referenced by
https://bugs.launchpad.net/neutron/+bug/1605546
So this bug can b
3 of the 4 original issues in the first post are now fixed, and the one
that isn't is addressed by a separate bug report:
1. NetworkNotFound: fixed by the introduction of
_create_ha_interfaces_and_ensure_network
2. IpAddressGenerationFailure:
https://bugs.launchpad.net/neutron/+bug/1562887
3. DB
utron/common/rpc.py
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: liberty-backport-potential mitaka-backport-potential
** Description changed:
The scenario which initially revealed this issue involved mul
Public bug reported:
Stacktrace: http://paste.openstack.org/show/539055/
There are a number of currently opened bugs that might deal with this,
but they are clouded with information that might not be relevant. I will
wade through them in the upcoming days to see if I can find something
similar to
Public bug reported:
The stacktrace can be found here:
http://paste.openstack.org/show/539052/
This was discovered while running the create_and_delete_router rally
test with a high (~10) concurrency number.
I encountered this on stable/mitaka so it's interesting to see if this
reproduces on mast
Public bug reported:
When creating a new DVR+HA, the router is created (the API returns
successfully) but the l3 agent enters an endless loop:
2016-03-23 13:57:37.340 ERROR neutron.agent.l3.agent [-] Failed to process
compatible router 'a04b3fd7-d46c-4520-82af-18d16835469d'
2016-03-23 13:57:37.3
Public bug reported:
Neutron has many code paths that can collide and be raceful which each
other. Current ongoing work can mitigate and minimize these races but
work is slow and it's very hard to fight against what you don't know
(ie. there can always be more races you're not aware of). A DLM
(Di
y way to fix this is either restarting one of the L3 agents which
didn't get scheduled, or recreating the router. Either is a bad option.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: l3-ha
** Changed i
Public bug reported:
Iptables doesn't work properly with fullstack, as can be observed in
[1].
The gist is that since all ovs-agents are running on the same namespace, they
try to override each other's iptables, causing the failures. This will
obviously cause security groups to fail.
Also, Assa
gent/ovsdb/impl_idl.py#L21
[2]:
https://github.com/openstack/neutron/blob/7a5ebc171f9ff342d7526808b1063b58cc631fec/requirements.txt
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Changed in: neutron
Assignee: (unassigne
Public bug reported:
Following [1], Neutron depends on WatchedFileHandler having a 'delay' property.
This attribute is not defined in Python's API [2] but Neutron depends on it
anyway.
In Python 2.7.6 and later versions (like the one running at the gate), this
attribute exists, but in 2.7.5 and
find out it
does not exist and crash.
[1]: https://review.openstack.org/#/c/154043/
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Tags: fullstack
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschw
them, and the ovs agent got deadlocked a lot.
[1]: http://linux.die.net/man/7/pipe (Section called "Pipe capacity")
[2]:
https://github.com/openstack/neutron/blob/stable/liberty/neutron/agent/linux/async_process.py#L163
** Affects: neutron
Importance: Undecided
Assigne
Public bug reported:
Steps to reproduce:
1. Create an HA router,
2. Connect the router to a gateway,
3. neutron router-update --admin-state-down=False
This results in the following traceback on the l3 agent:
2015-10-12 14:43:44.755 ERROR neutron.agent.l3.router_info [-]
Command: ['ip', 'netns
*** This bug is a duplicate of bug 1489372 ***
https://bugs.launchpad.net/bugs/1489372
@Arthur, you are correct. I've used 'git bisect' and found out that [1]
already fixes this issue. I will close this bug as a duplicate.
[1]: https://review.openstack.org/#/c/218118/
** Changed in: neutron
Public bug reported:
When, on a setup that has a DVR router, an OVS agent restarts, it fails
to re-create some of the flows for br-tun. For example:
$ # flows before agent restart
$ sudo ovs-ofctl dump-flows br-tun
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=77.325s, table=0, n_packets=0, n_
Public bug reported:
My ml2 configuration file contains the following:
[ml2]
extension_drivers = port_security,qos
mechanism_drivers = openvswitch,l2population
However, when trying to get a list of available rule types, the neutron-server
logs this to the log file:
WARNING neutron.plugins.ml2
fects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
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/1487053
Title:
validate_loc
Public bug reported:
Creating a new router, attaching it to some tenant network and then
adding a gateway for the router doesn't create the snat resources (such
as 'snat-%s' namespace and other interfaces).
Adding a gateway first (before attaching the router to a tenant network)
creates the snat
he fixtures that are used in
the environment (processes, configurations, namespaces...) not to be
cleaned.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: New
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
--
Public bug reported:
On startup, the L3 agent looks for namespaces to clean that don't belong
to him, in order to minimize system resources (namespaces) in the
machine.
The fullstack tests run an l3 agent that after deletes some namespaces
that he doesn't know. This in turns causes the deletion o
Public bug reported:
The patch introduced by https://review.openstack.org/#/c/143539/ changed
the sanity script to do all sorts of tests. Among those, it creates a
new temporary directory using /bin/mktemp.
On OS X, the executable is present in /usr/bin/mktemp.
** Affects: neutron
Importanc
Public bug reported:
Current HA related code should have functional tests merged to upstream.
All patches relevant to HA functional tests should be related to this
bug.
** Affects: neutron
Importance: Medium
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Changed in
Public bug reported:
Current HA related code should have integration tests merged to
upstream. All patches relevant to HA integration tests should be related
to this bug, until a proper blueprint is written for Kilo.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz
nt's log should show "Port: dummy12312312 is on
br-a, not on br-int".
Expected result: ovs agent should know to iterate though the options and
find the correct port in the correct bridge.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
** 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/1358206
Title:
ovsdb_monitor.SimpleInterfaceMonitor throws
eventlet.t
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
** Changed in: neutron
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineerin
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
** Changed in: neutron
Status: New => In Progress
--
You received this bug notification b
the end-user
the ability to apply this filter using the neutronclient.
** Affects: neutron
Importance: Undecided
Assignee: John Schwarz (jschwarz)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => John Schwarz (jschwarz)
** Changed in: neut
57 matches
Mail list logo
