ipv6 tests break on postgresql

Bug #1101645 reported by Sean Dague
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Sean Dague

Bug Description

Tests that use IPv6 addresses are breaking on Postgresql because pg now uses native IPv6 in the column definitions, so the returned value might be different in format but equivalent.

For instance, if we store ::babe: when we call it later we get ::babe:202:202. This is the same address, but the format is different.

Long term we should probably put IPv6 comparitor into things, but for now we can handle this by just using the second format in our tests.

Sean Dague (sdague)
Changed in tempest:
importance: Undecided → High
assignee: nobody → Sean Dague (sdague-b)
Changed in tempest:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/20067
Committed: http://github.com/openstack/tempest/commit/ab3d5d41c89ea5ba24fae62c62436333ebdc4f67
Submitter: Jenkins
Branch: master

commit ab3d5d41c89ea5ba24fae62c62436333ebdc4f67
Author: Sean Dague <email address hidden>
Date: Fri Jan 18 19:10:14 2013 -0500

    change ipv6 format to pass on postgresql

    postgresql recently moved to storing ip addresses as native types.
    The problem being that we send down some slightly unnatural looking
    IPv6 strings, so when we return them our simple comparitors fail.

    Converting this to a more IPv6 natural definition makes it pass with

    Fixes bug #1101645

    Change-Id: I282eb7e873d824e7c03923c2200bbe1e2d0bbada

Changed in tempest:
status: In Progress → Fix Released
Sean Dague (sdague)
Changed in tempest:
milestone: none → havana-3
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.