non-existent namespace errors in DHCP agent

Bug #1627691 reported by Kevin Benton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Low
Kevin Benton

Bug Description

The DHCP agent log gets sprinkled with ERROR logs when a call to disable DHCP for a network happens twice. This can happen if an agent's port is deleted and then a delete network call for its network happens before it resyncs (both events call 'disable' on the driver).

http://logs.openstack.org/91/375791/9/check/gate-tempest-dsvm-neutron-dvr-ubuntu-xenial/16e9b8f/logs/screen-q-dhcp.txt.gz?level=TRACE

2016-09-25 12:56:37.463 15334 ERROR neutron.agent.linux.utils [req-3882fc97-98a1-410e-8638-4de87841e5ee - -] Exit code: 1; Stdin: ; Stdout: ; Stderr: Cannot remove namespace file "/var/run/netns/qdhcp-3e0f2433-c53d-43e4-8c1e-5c6b863ad693": No such file or directory

2016-09-25 12:56:37.463 15334 WARNING neutron.agent.linux.dhcp [req-3882fc97-98a1-410e-8638-4de87841e5ee - -] Failed trying to delete namespace: qdhcp-3e0f2433-c53d-43e4-8c1e-5c6b863ad693
2016-09-25 12:57:24.774 15334 ERROR neutron.agent.linux.utils [req-113e268a-f42d-4a45-8e4e-e5530a14f43f - -] Exit code: 1; Stdin: ; Stdout: ; Stderr: Cannot remove namespace file "/var/run/netns/qdhcp-82696d3a-3ef9-4744-a685-cfd38730b541": No such file or directory

2016-09-25 12:57:24.774 15334 WARNING neutron.agent.linux.dhcp [req-113e268a-f42d-4a45-8e4e-e5530a14f43f - -] Failed trying to delete namespace: qdhcp-82696d3a-3ef9-4744-a685-cfd38730b541
2016-09-25 12:57:32.672 15334 ERROR neutron.agent.linux.utils [req-702f653b-f69b-485b-917f-9231622a5fae - -] Exit code: 1; Stdin: ; Stdout: ; Stderr: Cannot remove namespace file "/var/run/netns/qdhcp-4a536dcd-5047-4c39-91cb-30ab11cb3d73": No such file or directory

2016-09-25 12:57:32.673 15334 WARNING neutron.agent.linux.dhcp [req-702f653b-f69b-485b-917f-9231622a5fae - -] Failed trying to delete namespace: qdhcp-4a536dcd-5047-4c39-91cb-30ab11cb3d73

Revision history for this message
Kevin Benton (kevinbenton) wrote :

Would like RC2 for this because the fix is simple and it cleans up the DHCP agent logs.

Changed in neutron:
milestone: none → newton-rc2
Changed in neutron:
assignee: nobody → Kevin Benton (kevinbenton)
status: New → In Progress
Revision history for this message
Kevin Benton (kevinbenton) wrote :
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

The gate is pretty clogged, let's give priority to higher severity fixes.

Changed in neutron:
milestone: newton-rc2 → ocata-1
tags: added: newton-rc-potential
tags: added: logging
Changed in neutron:
importance: Undecided → Low
tags: added: newton-backport-potential
removed: newton-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/376010
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=98de72e9f32090a93c9c1b6f45cc0f2385c27792
Submitter: Jenkins
Branch: master

commit 98de72e9f32090a93c9c1b6f45cc0f2385c27792
Author: Kevin Benton <email address hidden>
Date: Sat Sep 24 01:53:38 2016 -0700

    Don't try to delete non-existent namespace

    The namespace in the DHCP agent may already have been
    deleted by a previous event when _destroy_namespace_and_port
    is called (e.g. all subnets deleted from network and then network
    is deleted). To avoid log errors every time this happens, check
    for the existence of the namespace before trying to delete it.

    Closes-Bug: #1627691
    Change-Id: I204ba7a0de056f13af505541d67f0acdd70fd54d

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 10.0.0.0b1

This issue was fixed in the openstack/neutron 10.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers