Have scenario tests use ipv4

Bug #1642741 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
High
Peter Stachowski

Bug Description

The scenario tests currently use the first ip address (or in the case of clusters, all) that is found. Unfortunately some datastores don't support IPV6, so if a non-ipv4 ip is used, the test will fail. Until all datastores support IPV6 (or we can come up with a strategy to intelligently decide which to use) we should only use the IPV4 ips.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

Changed in trove:
assignee: nobody → Peter Stachowski (peterstac)
status: New → In Progress
Changed in trove:
importance: Undecided → High
milestone: none → next
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/399247
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=7b36391800ef250735b204d389b9453b346a5cd0
Submitter: Jenkins
Branch: master

commit 7b36391800ef250735b204d389b9453b346a5cd0
Author: Peter Stachowski <email address hidden>
Date: Thu Nov 17 16:20:33 2016 -0500

    Have scenario tests use ipv4

    The scenario tests currently use the first ip address (or in the
    case of clusters, all) that is found. Unfortunately some datastores
    don't support IPV6, so if a non-ipv4 ip is used, the test will fail.
    Until all datastores support IPV6 (or we can come up with a strategy
    to intelligently decide which to use) we should only use the IPV4 ips,
    so the tests have been changed to accomodate this.

    Closes-Bug: 1642741
    Depends-On: Ia4fc545a10c7c16532aefd73818dd7d90c9c271b
    Change-Id: I6aff776680c9c0632d8965c3ed70ed26db0a63f2

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/trove 7.0.0.0b2

This issue was fixed in the openstack/trove 7.0.0.0b2 development milestone.

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.