Settings get stale, if a DHCP agent fails

Bug #1248048 reported by Roman Prykhodchenko
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Medium
Unassigned

Bug Description

In the story where several DHCP agents are running one of them might fail. In that case it's possible to re-schedule the networks it was hosting to a different one.
However, if DHCP service is still running on the failed node it will contain the old network settings which will conflict with the new ones.

description: updated
tags: added: l3-ipam-dhcp
Changed in neutron:
status: New → Triaged
tags: added: agent
Changed in neutron:
importance: Undecided → Medium
Revision history for this message
vaibhav_kale (vaibhav-kale) wrote :

Is it possible to reproduce the same bug in single node? if possible then provide more details

Romil Gupta (romilg)
Changed in neutron:
assignee: nobody → Romil Gupta (romilg)
Revision history for this message
Cedric Brandily (cbrandily) wrote :

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Romil Gupta (romilg) → nobody
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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