Magnum

Functional tests should support DNS nameserver config

Bug #1570543 reported by Dane LeBlanc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Dane LeBlanc

Bug Description

The Magnum functional tests currently use a DNS server setting of 8.8.8.8 when configuring nodes in a cluster. In some environments, this DNS server setting doesn't work. When this is the case, and functional tests are run locally, bay creation times out and the functional tests fail.

The functional tests should be enhanced to allow configuration of DNS nameserver to be used in baymodels that are created in functional tests.

Dane LeBlanc (leblancd)
Changed in magnum:
assignee: nobody → Dane LeBlanc (leblancd)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

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

Reviewed: https://review.openstack.org/306063
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=9712370357365edd467b6701e6a7817363340647
Submitter: Jenkins
Branch: master

commit 9712370357365edd467b6701e6a7817363340647
Author: Dane LeBlanc <email address hidden>
Date: Thu Apr 14 15:49:50 2016 -0400

    Functional tests should support DNS nameserver config

    The Magnum functional tests currently use a DNS server setting of
    8.8.8.8 when configuring nodes in a cluster. In some environments,
    this DNS server setting doesn't work. When this is the case, and
    functional tests are run locally, bay creation times out and the
    functional tests fail.

    This patch enhances the functional tests to allow configuration of
    DNS nameserver to be used in baymodels that are created in
    functional tests.

    Change-Id: I958d199565ae5741dd6f4b8764e51ea16a8d505b
    Closes-Bug: #1570543

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

This issue was fixed in the openstack/magnum 3.0.0 release.

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.