metadata proxy is not started when network has ipv6 and ipv4 subnets

Bug #1392564 reported by Xu Han Peng on 2014-11-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
High
Xu Han Peng
Juno
High
Alan Pevec

Bug Description

Commit 1b66e11b5d8c0b3de0610ca02c3e10b6f64ae375 introduce a new problem that metadata proxy will not be started when a isolated network contains ipv6 subnet with dhcp enabled and a ipv4 subnet.

See the discussion in the code review for details:

https://review.openstack.org/#/c/123671/1/neutron/agent/dhcp_agent.py

Fix proposed to branch: master
Review: https://review.openstack.org/134432

Changed in neutron:
assignee: nobody → Xu Han Peng (xuhanp)
status: New → In Progress
Alan Pevec (apevec) on 2014-11-25
tags: added: juno-backport-potential
Changed in neutron:
importance: Undecided → High

Reviewed: https://review.openstack.org/134432
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4c128c351589ef9f2fc1e084c655a97bdbbda7ce
Submitter: Jenkins
Branch: master

commit 4c128c351589ef9f2fc1e084c655a97bdbbda7ce
Author: Xu Han Peng <email address hidden>
Date: Fri Nov 14 10:53:59 2014 +0800

    Fix metadata proxy start problem for v6-v4 network

    Commit 1b66e11b5d8c0b3de0610ca02c3e10b6f64ae375 introduces
    a new problem that metadata proxy will not be started when
    an isolated network contains ipv6 subnet with dhcp enabled
    and a ipv4 subnet.

    This fix separates the checks to enable dhcp and enable metadata
    so metadata proxy can be started if there is ipv4 subnet exists
    in the network with metadata enabled.

    Change-Id: If26806083db225e9ab30d75fa6c728ce99a7cafe
    Closes-Bug: 1392564

Changed in neutron:
status: In Progress → Fix Committed
Alan Pevec (apevec) on 2014-11-26
tags: removed: juno-backport-potential

Reviewed: https://review.openstack.org/137238
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b5c08b35e75de6e09b75ed01120b6fdedb9125f
Submitter: Jenkins
Branch: stable/juno

commit 8b5c08b35e75de6e09b75ed01120b6fdedb9125f
Author: Xu Han Peng <email address hidden>
Date: Fri Nov 14 10:53:59 2014 +0800

    Fix metadata proxy start problem for v6-v4 network

    Commit 1b66e11b5d8c0b3de0610ca02c3e10b6f64ae375 introduces
    a new problem that metadata proxy will not be started when
    an isolated network contains ipv6 subnet with dhcp enabled
    and a ipv4 subnet.

    This fix separates the checks to enable dhcp and enable metadata
    so metadata proxy can be started if there is ipv4 subnet exists
    in the network with metadata enabled.

    Change-Id: If26806083db225e9ab30d75fa6c728ce99a7cafe
    Closes-Bug: 1392564
    (cherry picked from commit 4c128c351589ef9f2fc1e084c655a97bdbbda7ce)

Thierry Carrez (ttx) on 2014-12-18
Changed in neutron:
milestone: none → kilo-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2015-04-30
Changed in neutron:
milestone: kilo-1 → 2015.1.0

Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/icehouse
Review: https://review.openstack.org/163784
Reason: Icehouse is about to EOL.

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

Other bug subscribers