Tempest tests fail on standalone ironic job scenario012

Bug #1844989 reported by Sagi (Sergey) Shnaidman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Dmitry Tantsur

Bug Description

scenario 012 job fails on tempest run:

2019-09-23 09:10:14 | + openstack baremetal node set --property memory_mb=4096 --property cpus=4 --property local_gb=10 --property cpu_arch=x86_64 56ae5009-69af-4f1c-9f54-32003173351c
2019-09-23 09:10:18 | + openstack baremetal node manage 56ae5009-69af-4f1c-9f54-32003173351c --wait
2019-09-23 09:14:38 | Node 56ae5009-69af-4f1c-9f54-32003173351c failed to reach state manageable. It's in unexpected stable state enroll
2019-09-23 09:14:38 | Waiting for provision state manageable on node 56ae5009-69af-4f1c-9f54-32003173351c

https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_bbe/683848/1/check/tripleo-ci-centos-7-scenario012-standalone/bbee5fe/logs/undercloud/home/zuul/tempest.log.txt.gz

+ /tmp/ironic/devstack/tools/ironic/scripts/create-node.sh::L114: grep -q node1.qcow2
error: failed to get pool 'default'
error: Storage pool not found: no storage pool with matching name 'default'
+ /tmp/ironic/devstack/tools/ironic/scripts/create-node.sh::L116: virsh vol-create-as default node1.qcow2 11G --format qcow2
error: failed to get pool 'default'
error: Storage pool not found: no storage pool with matching name 'default'

https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_bbe/683848/1/check/tripleo-ci-centos-7-scenario012-standalone/bbee5fe/logs/undercloud/home/zuul/create-node-1.log.txt.gz

Changed in tripleo:
assignee: nobody → Dmitry Tantsur (divius)
wes hayutin (weshayutin)
tags: added: alert tempest
Changed in tripleo:
milestone: train-rc1 → ussuri-1
Revision history for this message
Sagi (Sergey) Shnaidman (sshnaidm) wrote :
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
Revision history for this message
wes hayutin (weshayutin) wrote :

This is blocked by failing standalone deployment for this scenario

wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
Revision history for this message
wes hayutin (weshayutin) wrote :
Revision history for this message
wes hayutin (weshayutin) wrote :

moved to centos-8 in periodic, we'll pick it up there.

Changed in tripleo:
status: Triaged → Incomplete
Revision history for this message
Soniya Murlidhar Vyas (svyas) wrote :

Can I know the status of this bug?

Revision history for this message
Soniya Murlidhar Vyas (svyas) wrote :

Logs are dead, so I am not able to understand the bug, Can I have more information?

wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
milestone: victoria-1 → victoria-3
Changed in tripleo:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.