Some Tempest tests require booting multiple instances at once, but we only deploy 1 Ironic node

Bug #1334033 reported by Adam Gandelman on 2014-06-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
OpenStack Core Infrastructure

Bug Description

Some compute API tests require booting multiple instances during a single test or single test case, ie:


The current Ironic devstack-gate deployment sets up Ironic with a single VM enrolled as a single Ironic node. Once this has been provisioned, there are no more resources available for additional test instances.

Some solutions:

 -Tempest needs to have a configurable limit to the number of instances that can be spawned at once
 - Ironic+Devstack deployment should set quota limits based on IRONIC_VM_COUNT
 - Adjust IRONIC_VM_COUNT in the devstack-gate job to match needs of Tempest.. not sure how well the devstack slave nodes would handle deploying many Ironic instances. tempest.api.compute.servers.test_list_servers creates a total of 3 servers at once, which I believe is the max.

Dmitry Tantsur (divius) on 2014-06-25
Changed in ironic:
status: New → Triaged
importance: Undecided → Medium
tags: added: ironic-tempest
James E. Blair (corvus) on 2014-07-08
Changed in openstack-ci:
status: New → Triaged
importance: Undecided → Medium
David Kranz (david-kranz) wrote :

This issue should be solved on the ironic side. Tempest assumes a modest level of resources which should be met when using it. The multi-server tests can be skipped if running in a limited server environment.

Changed in tempest:
status: New → Won't Fix
Miles Gould (mgould) on 2016-09-14
Changed in ironic:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers