tempest

Tempest assumes you are using floating IPs

Bug #1052747 reported by Sam Morrison
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tempest
Invalid
Medium
Unassigned

Bug Description

Would be good to have a flag that could disable floating IP checks

Revision history for this message
David Kranz (david-kranz) wrote :

There are dozens of extensions for which the same case could be made. One way to deal with it would be to have tempest first ask for a list of the extensions and mark each test class with a required extension, skipping the test is it is not present. This would be a fair bit of work.

Changed in tempest:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Attila Fazekas (afazekas) wrote :

Automated skip decisions usually source of trouble, it should be made by explicit configuration or the test cases should be excluded by attribute.

Revision history for this message
Castulo J. Martinez (castulo-martinez) wrote :

This bug is very old, and hasn't been updated in a long time.
I guess this bug is no longer valid since the connect_method key was added to the tempest configuration file under the [vaildation] section.

I will close this bug as Incomplete, if someone think this bug should remain open please provide more information and re-open it.

Changed in tempest:
status: Triaged → Incomplete
Revision history for this message
Castulo J. Martinez (castulo-martinez) wrote :

Moving the bug to invalid.

Changed in tempest:
status: Incomplete → 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.