neutron

[SRU] Fix Race between L3 agent and neutron-ns-cleanup

Bug #1623664 reported by Gautam Kulkarni on 2016-09-14

This bug affects 3 people

	Status	Importance	Assigned to
Ubuntu Cloud Archive	Fix Released	Undecided	Unassigned
neutron	Invalid	Undecided	Unassigned
neutron (Ubuntu)	Fix Released	Undecided	Unassigned
Xenial	Fix Released	Undecided	Unassigned
Yakkety	Fix Released	Undecided	Unassigned
Zesty	Fix Released	Undecided	Unassigned
neutron-lbaas (Ubuntu)	Fix Released	Undecided	Unassigned
Xenial	Fix Released	Undecided	Unassigned
Yakkety	Fix Released	Undecided	Unassigned

Bug Description

I suspect a race between the neutron L3 agent and the neutron-netns-cleanup script, which runs as a CRON job in Ubuntu. Here's a stack trace in the router delete code path:

2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager [-] Error during notification for neutron.agent.metadata.driver.before_router_removed router, before_delete
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Traceback (most recent call last):
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager File "/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py", line 141, in _notify_loop
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager callback(resource, event, trigger, **kwargs)
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager File "/usr/lib/python2.7/dist-packages/neutron/agent/metadata/driver.py", line 176, in before_router_removed
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager router.iptables_manager.apply()
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", line 423, in apply
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return self._apply()
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", line 431, in _apply
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return self._apply_synchronized()
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", line 457, in _apply_synchronized
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager save_output = self.execute(args, run_as_root=True)
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 159, in execute
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager raise RuntimeError(m)
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager RuntimeError:
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8', 'iptables-save']
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Exit code: 1
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdin:
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdout:
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stderr: Cannot open network namespace "qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8": No such file or directory
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent [-] Error while deleting router 69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Traceback (most recent call last):
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 344, in _safe_router_removed
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent self._router_removed(router_id)
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 360, in _router_removed
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent self, router=ri)
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/dist-packages/neutron/callbacks/registry.py", line 44, in notify
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent _get_callback_manager().notify(resource, event, trigger, **kwargs)
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py", line 123, in notify
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent raise exceptions.CallbackFailure(errors=errors)
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent CallbackFailure: Callback neutron.agent.metadata.driver.before_router_removed failed with "
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8', 'iptables-save']
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Exit code: 1
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Stdin:
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Stdout:
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Stderr: Cannot open network namespace "qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8": No such file or directory
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent "
2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent

In this case, the cleanup first deleted the qrouter namespace it found to be empty (not containing any netdevs other than lo). The router delete flow attempts to delete iptables rules within the namespace before deleting the namespace itself. However, if the namespace is deleted first, the iptables-save command on a non-existent namespace fails. The resulting exception prevents the router delete flow from succeeding and the L3 agent gets stuck in a failure loop.

Can somebody confirm if this is a known issue or if I've misunderstood the problem. Assuming my analysis is correct, would the following fix work?

diff --git a/neutron/agent/l3/agent.py b/neutron/agent/l3/agent.py
index b096091..8d3e8ae 100644
--- a/neutron/agent/l3/agent.py
+++ b/neutron/agent/l3/agent.py
@@ -358,8 +358,16 @@ class L3NATAgent(firewall_l3_agent.FWaaSL3AgentRpcCallback,
self.namespaces_manager.ensure_router_cleanup(router_id)
return

- registry.notify(resources.ROUTER, events.BEFORE_DELETE,
- self, router=ri)
+ try:
+ registry.notify(resources.ROUTER, events.BEFORE_DELETE,
+ self, router=ri)
+ except Exception as e:
+ ns_err = "Cannot open network namespace qrouter-" + router_id
+ if ns_err not in e:
+ raise
+ else:
+ LOG.warn(_LW("Namespace for router %s already deleted"),
+ router_id)

Tags:

Revision history for this message

Assaf Muller (amuller) wrote on 2016-09-14:

I don't think running the netns-cleanup script in a CRON job is desired behavior.

Revision history for this message

Gautam Kulkarni (kulkarni) wrote on 2016-09-14:

Thanks, Assaf, for your quick response. Do you think that this is an Ubuntu package bug? We are not explicitly creating the CRON job. Would the fix be to remove the CRON job? Thanks.

Revision history for this message

Hirofumi Ichihara (ichihara-hirofumi) wrote on 2016-09-15:

I agree Assaf. Why do we need to run neutron-netns-cleanup with l3-agent? Although I don't know ubuntu package behavior.

Changed in neutron:
status:	New → Invalid

Revision history for this message

Akihiro Motoki (amotoki) wrote on 2016-09-15:

The recommended solution is to disable or delete Ubuntu cron job of neutron-netns-cleanup.
neutron-netns-cleanup command searches network namespaces only with a loopback interface and deletes such namespaces. This potentially creates a situation where undesired netns deletion occurs.

I think the cron job was added when the neutron default behavior was not to delete namespaces. it was long ago.

In addition, Ubuntu package registers three neutron-netns-cleanup cron jobs (for dhcp-agent, l3-agent, lbaas-agent), but all of three do the same job. This also looks tricky.

Revision history for this message

James Dennis (jtmes) wrote on 2017-01-05:

Anyone from the cloud archive project have an opinion on a fix for this?

Revision history for this message

Corey Bryant (corey.bryant) wrote on 2017-01-05:

These cron jobs are quite old (introduced in grizzly) so if we can drop them now I'd like to do that.

Revision history for this message

Corey Bryant (corey.bryant) wrote on 2017-01-06:

I need to confirm for sure that these cron jobs are no longer needed before dropping them. If neutron is handling namespace cleanup now then it sounds like we can, however I need to dig in and confirm. I'll do that soon.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-03-27: Related fix proposed to neutron (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/450271

Chuck Short (zulcss) on 2017-03-27

summary:

- Race between L3 agent and neutron-ns-cleanup
+ [SRU] Race between L3 agent and neutron-ns-cleanup

Revision history for this message

Chuck Short (zulcss) wrote on 2017-03-27: Re: [SRU] Race between L3 agent and neutron-ns-cleanup

[Description]
A race condition on L3 agents can occur when the cron jobs run when the routing tables are empty. This results in the traceback above.

[Test Case]
Run tempest and then check the namespaces after running neutron-ns-cleanup

[Regression Potential]
None

Revision history for this message

Ihar Hrachyshka (ihar-hrachyshka) wrote on 2017-03-27:

#10

Cron job for -cleanup? You should be brave to do that... Please don't.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-03-27:

#11

This bug was fixed in the package neutron-lbaas - 2:10.0.0-0ubuntu2

---------------
neutron-lbaas (2:10.0.0-0ubuntu2) zesty; urgency=medium

  * debian/neutron-lbaas-common.install: Remove cron jobs since
    it will cause a race with L3 agents and neutron. (LP: #1623664)
  * d/control: Remove duplicate depenendency.

-- Chuck Short <email address hidden> Mon, 27 Mar 2017 13:04:16 -0400

Changed in neutron-lbaas (Ubuntu):
status:	New → Fix Released

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2017-03-28:

#12

Can we please have the bug description updated to include SRU information? Thank you!
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Chuck Short (zulcss) on 2017-04-06

summary:

- [SRU] Race between L3 agent and neutron-ns-cleanup
+ [SRU] Fix Race between L3 agent and neutron-ns-cleanup

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2017-04-06:

#13

Another thing besides the bug description needing to follow the SRU template - the same change that has been released to zesty (version 2:10.0.0-0ubuntu4) fails to build from source. Build failure:

https://launchpad.net/ubuntu/+source/neutron/2:10.0.0-0ubuntu4/+build/12366961

Please make sure that the devel version is buildable and migrates to the release pocket.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-17: Related fix merged to neutron (master)

#14

Reviewed: https://review.openstack.org/450271
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3889b0f214fbb1d32531395cff232cf57daf7b17
Submitter: Jenkins
Branch: master

commit 3889b0f214fbb1d32531395cff232cf57daf7b17
Author: Saverio Proto <email address hidden>
Date: Mon Mar 27 16:39:16 2017 +0200

Dont try to apply iptables rules in a endless loop

    If the namespace does not exist the current behavior
    is to try to apply the iptables rules forever in a
    endless loop. This fills up the logs on the network
    node and leads to outage.

    Change-Id: I628b18a66f9478d7349fa1817431aae2f62ee105
    Related-bug: #1623664
    Related-bug: #1573073

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-18: Related fix proposed to neutron (stable/ocata)

#15

Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/457467

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-18: Related fix proposed to neutron (stable/newton)

#16

Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/457468

Revision history for this message

James Page (james-page) wrote on 2017-04-19:

#17

@Lukasz

I working to resolve the autopkgtest failure caused by 10.0.0-0ubuntu5

Revision history for this message

James Page (james-page) wrote on 2017-04-19:

#18

@Lukasz

I've uploaded a new version of neutron 10.0.0-0ubuntu5.1 to unapproved queue (it will show as a sync from biletto).

This resolves the autopkgtest failures and does actually build.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-20: Related fix merged to neutron (stable/newton)

#19

Reviewed: https://review.openstack.org/457468
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=44c3ee8cb2bc9adb6f4f95ba3f6be4c3abe344df
Submitter: Jenkins
Branch: stable/newton

commit 44c3ee8cb2bc9adb6f4f95ba3f6be4c3abe344df
Author: Saverio Proto <email address hidden>
Date: Mon Mar 27 16:39:16 2017 +0200

Dont try to apply iptables rules in a endless loop

    If the namespace does not exist the current behavior
    is to try to apply the iptables rules forever in a
    endless loop. This fills up the logs on the network
    node and leads to outage.

    Change-Id: I628b18a66f9478d7349fa1817431aae2f62ee105
    Related-bug: #1623664
    Related-bug: #1573073
    (cherry picked from commit 3889b0f214fbb1d32531395cff232cf57daf7b17)

tags:

added: in-stable-newton

Revision history for this message

Andy Whitcroft (apw) wrote on 2017-04-21: Please test proposed package

#20

Hello Gautam, or anyone else affected,

Accepted neutron into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:10.0.0-0ubuntu5.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in neutron (Ubuntu Zesty):
status:	New → Fix Committed
tags:	added: verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-04-22:

#21

This bug was fixed in the package neutron - 2:10.0.0-0ubuntu5.1

---------------
neutron (2:10.0.0-0ubuntu5.1) zesty; urgency=medium

  * d/rules: Revert the majority of changes made under 2:10.0.0-0ubuntu5
    as these break default configuration and are the root cause of
    the autopkgtest failures.

neutron (2:10.0.0-0ubuntu5) zesty; urgency=medium

* d/rules: Fix failing unit tests.

neutron (2:10.0.0-0ubuntu4) zesty; urgency=medium

  * d/neutron-common.install, d/neutron-dhcp-agent.install:
    Remove cron jobs since they will cause a race when
    using an L3 agent. (LP: #1623664)

-- James Page <email address hidden> Wed, 19 Apr 2017 11:49:10 +0100

Changed in neutron (Ubuntu):
status:	New → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-28: Related fix merged to neutron (stable/ocata)

#22

Reviewed: https://review.openstack.org/457467
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8fed89b12b3eb6d3c73a4f53dcf66f85f5bd4e8f
Submitter: Jenkins
Branch: stable/ocata

commit 8fed89b12b3eb6d3c73a4f53dcf66f85f5bd4e8f
Author: Saverio Proto <email address hidden>
Date: Mon Mar 27 16:39:16 2017 +0200

Dont try to apply iptables rules in a endless loop

    If the namespace does not exist the current behavior
    is to try to apply the iptables rules forever in a
    endless loop. This fills up the logs on the network
    node and leads to outage.

    Change-Id: I628b18a66f9478d7349fa1817431aae2f62ee105
    Related-bug: #1623664
    Related-bug: #1573073
    (cherry picked from commit 3889b0f214fbb1d32531395cff232cf57daf7b17)

tags:

added: in-stable-ocata

Revision history for this message

Brian Murray (brian-murray) wrote on 2017-05-04: Please test proposed package

#23

Hello Gautam, or anyone else affected,

Accepted neutron into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:8.4.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in neutron (Ubuntu Xenial):
status:	New → Fix Committed

Revision history for this message

Brian Murray (brian-murray) wrote on 2017-05-04:

#24

Hello Gautam, or anyone else affected,

Accepted neutron into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:9.2.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in neutron (Ubuntu Yakkety):
status:	New → Fix Committed

Revision history for this message

Brian Murray (brian-murray) wrote on 2017-05-04:

#25

Hello Gautam, or anyone else affected,

Accepted neutron-lbaas into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron-lbaas/2:8.3.0-0ubuntu3 in a few hours, and then in the -proposed repository.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in neutron-lbaas (Ubuntu Xenial):
status:	New → Fix Committed

Revision history for this message

Brian Murray (brian-murray) wrote on 2017-05-04:

#26

It looks like there has not been an upload of neutron-lbaas to the yakkety SRU queue.

Revision history for this message

James Page (james-page) wrote on 2017-05-05:

#27

Uploaded to the yakkety queue - this must have got missed - apologies.

Revision history for this message

Brian Murray (brian-murray) wrote on 2017-05-05:

#28

Hello Gautam, or anyone else affected,

Accepted neutron-lbaas into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron-lbaas/2:9.0.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in neutron-lbaas (Ubuntu Yakkety):
status:	New → Fix Committed

Revision history for this message

James Page (james-page) wrote on 2017-05-15:

#29

Zesty regression tested as part of OpenStack Deployment using Tempest smoke tests:

======
Totals
======
Ran: 103 tests in 1600.0434 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 830.7650 sec.

All passed.

tags:

added: verification-done-zesty

Revision history for this message

James Page (james-page) wrote on 2017-05-15:

#30

Yakkety proposed regression tested as part of OpenStack Deployment using Tempest smoke tests:

======
Totals
======
Ran: 103 tests in 1004.6364 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 553.9073 sec.

All passed

tags:	added: verification-done removed: verification-done-zesty verification-needed
tags:	added: verification-done-yakkety verification-done-zesty verification-needed removed: verification-done

Revision history for this message

James Page (james-page) wrote on 2017-05-15:

#31

Xenial-Newton proposed regression test passed:

======
Totals
======
Ran: 103 tests in 1048.1681 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 596.4067 sec.

Revision history for this message

James Page (james-page) wrote on 2017-05-15:

#32

Xenial proposed regression tests with OpenStack Tempest Smoke:

======
Totals
======
Ran: 103 tests in 956.7399 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 541.7789 sec.

All passed

tags:

added: verification-done
removed: verification-done-yakkety verification-done-zesty verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-15:

#33

This bug was fixed in the package neutron - 2:10.0.0-0ubuntu5.1

---------------
neutron (2:10.0.0-0ubuntu5.1) zesty; urgency=medium

  * d/rules: Revert the majority of changes made under 2:10.0.0-0ubuntu5
    as these break default configuration and are the root cause of
    the autopkgtest failures.

neutron (2:10.0.0-0ubuntu5) zesty; urgency=medium

* d/rules: Fix failing unit tests.

neutron (2:10.0.0-0ubuntu4) zesty; urgency=medium

  * d/neutron-common.install, d/neutron-dhcp-agent.install:
    Remove cron jobs since they will cause a race when
    using an L3 agent. (LP: #1623664)

-- James Page <email address hidden> Wed, 19 Apr 2017 11:49:10 +0100

Changed in neutron (Ubuntu Zesty):
status:	Fix Committed → Fix Released

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2017-05-15: Update Released

#34

The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-15:

#35

This bug was fixed in the package neutron - 2:9.2.0-0ubuntu2

---------------
neutron (2:9.2.0-0ubuntu2) yakkety; urgency=medium

  * d/neutron-common.install, d/neutron-dhcp-agent.install:
    Remove cron jobs since they will cause a race when
    using an L3 agent. The L3 agent cleans up after itself now.
    (LP: #1623664)

-- Chuck Short <email address hidden> Mon, 27 Mar 2017 13:20:57 -0400

Changed in neutron (Ubuntu Yakkety):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-15:

#36

This bug was fixed in the package neutron-lbaas - 2:8.3.0-0ubuntu3

---------------
neutron-lbaas (2:8.3.0-0ubuntu3) xenial; urgency=medium

* debian/neutron-lbaas-common.install: Remove cron jobs since
it will cause a race with L3 agents and neutron. (LP: #1623664)

-- Chuck Short <email address hidden> Mon, 27 Mar 2017 14:23:58 -0400

Changed in neutron-lbaas (Ubuntu Xenial):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-15:

#37

This bug was fixed in the package neutron-lbaas - 2:9.0.0-0ubuntu2

---------------
neutron-lbaas (2:9.0.0-0ubuntu2) yakkety; urgency=medium

* debian/neutron-lbaas-common.install: Remove cron jobs since
it will cause a race with L3 agents and neutron. (LP: #1623664).

-- Chuck Short <email address hidden> Mon, 27 Mar 2017 13:33:56 -0400

Changed in neutron-lbaas (Ubuntu Yakkety):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-15:

#38

This bug was fixed in the package neutron - 2:8.4.0-0ubuntu2

---------------
neutron (2:8.4.0-0ubuntu2) xenial; urgency=medium

  [ Edward Hope-Morley ]
  * Backport fix for Failure to retry update_ha_routers_states (LP: #1648242)
    - d/p/add-check-for-ha-state.patch

  [ Chuck Short ]
  * d/neutron-common.install, d/neutron-dhcp-agent.install:
    Remove cron jobs since they will cause a race when
    using an L3 agent. The L3 agent cleans up after itself now.
    (LP: #1623664)

-- Chuck Short <email address hidden> Wed, 19 Apr 2017 11:39:09 +0100

Changed in neutron (Ubuntu Xenial):
status:	Fix Committed → Fix Released

Revision history for this message

Corey Bryant (corey.bryant) wrote on 2017-10-26:

#39

Marking fix released for the cloud archive. All of the above package versions have been released to -updates for the corresponding archive pockets.

Changed in cloud-archive:
status:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.