tempest

  1. Bug #1250866
  2. Comment #22

Comment 22 for bug 1250866

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

Reviewed: https://review.openstack.org/159776
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=9ce97dfa353e3659aa0ec0a7f62ed3a7e54c4bdf
Submitter: Jenkins
Branch: master

commit 9ce97dfa353e3659aa0ec0a7f62ed3a7e54c4bdf
Author: Rohan Kanade <email address hidden>
Date: Tue Dec 10 18:59:35 2013 +0530

    Start instances using fixed network when possible

    Uses the fixed_network_name option to select which network
    to boot test instances on. This allows Tempest to be run
    in environments where there are multiple networks available.

    This problem does not apply to nova-network environments because
    it will happily start instances with multiple networks attached,
    so the behavior is left as before in that case.

    Co-Authored-By: Ben Nemec <email address hidden>
    Co-Authored-By: Vincent Untz <email address hidden>
    Co-Authored-By: git-harry <email address hidden>

    Change-Id: Ib5b84b59e3d182d8b9cc83954537c32f3eb9e388
    Closes-Bug: #1250866