updating NetDHCPAgent doesn't work with new network_id that is associated with specific dhcp_agent_id
Bug #1272258 reported by
Mitsuru Kanabuchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Undecided
|
Ryo Miki |
Bug Description
UPDATE_FAILED occured when update NetDHCPAgent resource.
In my understand, Neutron's behavior is:
1) create netwrok and subnet (neutron create-network, create-subnet)
2) create port to the network (neutron port-create)
3) at the same time, dhcp-agent is associated automatically by Neutron
4) 409 error will happen when adding same association (we can add other dhcp-agents if it is not associated with the Network)
I think Heat should remove old dhcp-agent before associating new dhcp-agent.
Or Heat should check same dhcp-agent existence before associating.
Changed in heat: | |
assignee: | nobody → Ryo Miki (miki-ryo-e) |
status: | New → In Progress |
Changed in heat: | |
status: | In Progress → Fix Committed |
Changed in heat: | |
milestone: | none → icehouse-3 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/69311
Review: https:/