Create amphora does not store the amphora IP in DB

Bug #1450520 reported by Michael Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Fix Released
Critical
Brandon Logan

Bug Description

When the controller worker creates a new amphora, the management IP address for the amphora is not stored in the database lb_network_ip column.

blogan notes:
Also, to retrieve the IP from nova we have to get the amphora by its compute_id. Nova client will return the amphora object with a dictionary of addresses as an attribute. This dictionary is keyed off the network NAME not the network id, which is just dumb, but it is what we have to deal with. That's why there's currently a networking group with lb_network_name. I would prefer to store the ID though, and just get the name by that ID in code.

Tags: demo
Changed in octavia:
assignee: nobody → German Eichberger (german-eichberger)
Changed in octavia:
assignee: German Eichberger (german-eichberger) → Brandon Logan (brandon-logan)
Changed in octavia:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to octavia (master)

Reviewed: https://review.openstack.org/179452
Committed: https://git.openstack.org/cgit/stackforge/octavia/commit/?id=0837da18a72d1e34a0cf4c7cafe6b2748ebf9cae
Submitter: Jenkins
Branch: master

commit 0837da18a72d1e34a0cf4c7cafe6b2748ebf9cae
Author: Brandon Logan <email address hidden>
Date: Fri May 1 13:43:33 2015 -0500

    Fixed various issues with create lb and amphora flow

    Closes-Bug: #1450520
    Closes-Bug: #1450524
    Closes-Bug: #1450621

    Change-Id: Ibc347dec4bebe10e0c7603bfa6b09833c84f181f

Changed in octavia:
status: In Progress → Fix Committed
Changed in octavia:
status: Fix Committed → Fix Released
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.