CI: Discern between Ironic client and grep failure

Pipe hid an issue that Ironic client was not available in CI,
making it look as if fake-hardware driver was not usable.

This commit applies separation of concerns to easily discern
between the two failures and provide better debugging experience.

Change-Id: Iac3d84b7d707b84a8426c8d787b29a368ff7ae85
Related-Bug: #1872481
This commit is contained in:
Radosław Piliszek 2020-04-26 16:02:43 +02:00
parent b1db4f5c3b
commit 1243337a1c

View File

@ -99,12 +99,16 @@ function test_ironic_logged {
. ~/openstackclient-venv/bin/activate . ~/openstackclient-venv/bin/activate
# Smoke test ironic API. # Smoke test ironic API.
if ! openstack baremetal driver list | grep fake-hardware; then local baremetal_driver_list
baremetal_driver_list=$(openstack baremetal driver list)
openstack baremetal node list
openstack baremetal port list
# Sanity check.
if ! echo "$baremetal_driver_list" | grep fake-hardware; then
echo "No active conductors with fake-hardware driver" echo "No active conductors with fake-hardware driver"
exit 1 exit 1
fi fi
openstack baremetal node list
openstack baremetal port list
create_resources create_resources
wait_for_placement_resources wait_for_placement_resources