tempest

tests.compute.test_floating_ips_actions test_associate_already_associated_floating_ip invalid expected result

Bug #1060450 reported by Wayne Vestal Weeks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Invalid
Medium
Wayne Vestal Weeks

Bug Description

Essex was throwing a 500 error when attempting to associate a floating ip that was already assocated to another server. The fix to this issue was to return a 400 since it was an invalid request.

Nova Bug: #1000571

The tempest test case currently expects the ip to be reassigned. The test needs to be update to pass on a 400 response.

See original description
Tags: folsom
Jay Pipes (jaypipes)
description: updated
tags: added: folsom
Changed in tempest:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Sean Gallagher (torandu)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

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

Changed in tempest:
status: Triaged → In Progress
Revision history for this message
Wayne Vestal Weeks (wayneweeks) wrote :

The review for this fix has gone to an abandoned state and I have some time to play with it tonight. I'm poaching it.

Changed in tempest:
assignee: Sean Gallagher (torandu) → Wayne Vestal Weeks (wayneweeks)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

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

Revision history for this message
Wayne Vestal Weeks (wayneweeks) wrote :

marking as invalid

Seems like the nova bug this was based off of is invalid.

Changed in tempest:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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