When we use devstack + tempest to test baremetal, specially w/ real hardware, we expect to use DEFAULT_INSTANCE_TYPE=baremetal to allow us to use an appropriate baremetal flavor which is created at lib/ironic.
If you take a closer look into the devstack.log file from a recent run of dsvm-ironic-pxe_ssh (like http://logs.openstack.org/04/280204/4/check/gate-tempest-dsvm-ironic-pxe_ssh/87a21ff/logs/devstacklog.txt.gz ) and look for the string "awk '/ baremetal / { print $2 }'", which is the point where lib/tempest looks for a flavor with the name specified by DEFAULT_INSTANCE_TYPE, you'll note it never finds the 'baremetal' flavor. If you look for the moment the 'baremetal' flavor is created you'll also notice that is way later in the stack process and thus we have not used 'baremetal' flavor on any of our upstream tests but the generic flavor_ref=1 and flavor_ref_alt=2 (see tempest.conf file from a recent run) which are fine for upstream integration tests since it's made using guests and a small image like cirros fitting in the default flavor capacity. For real hardware though that flavor is not enough, for instance I caught this bug cause cirros doesn't support ppc64 hardware and thus I opted to use fedora as target image, requiring therefore a bigger root_gb than 1gb as flavor_id 1 offers.
Why is this happening? before we move into a devstack plugin, ironic's phases were executed before tempest's cause the files were named 50-ironic and 80-tempest, now devstack's in-tree services are executed before (tempest included) and then the plugins.
Fix proposed to branch: master
Review: https:/