Amphora create should check for ERROR status in compute

Bug #1490180 reported by Brandon Logan
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Trevor Vardeman

Bug Description

When creating an Amphora, the code does not stop checking when Compute says the amphora is in an ERROR state. Octavia's poller for this will continue checking for ACTIVE until the timeout/retry limit is hit. The code should really see that its in ERROR state and immediately update the Amphora to ERROR state and/or delete the Amphora and try to recreate a new one.

Changed in octavia:
status: New → Confirmed
importance: Undecided → Medium
importance: Medium → High
Changed in octavia:
assignee: nobody → Trevor Vardeman (trevor-vardeman)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to octavia (master)

Fix proposed to branch: master

Changed in octavia:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to octavia (master)

Submitter: Jenkins
Branch: master

commit 9bf1d0a5f53e60bb10aa3897e7eede262371e68d
Author: Trevor Vardeman <email address hidden>
Date: Wed Jan 13 13:57:05 2016 -0600

    Amphora Create now fails when amphora goes into ERROR status

    Removed the retry flow and added retry logic to the task. Upon
    the ampora status returning "ERROR", the ComputeWaitTimeoutException
    is raised and the flow reverts. Also updated the failover amphora
    flow to the same logic.

    Change-Id: I74353bfebd14ce3d1aacdf5dd94152a019e932da
    Closes-Bug: #1494931
    Closes-Bug: #1490180

Changed in octavia:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers