Above workaroud is not going to work as in upgrade job we run tempest twice and here http://logs.openstack.org/67/656967/4/check/tripleo-ci-centos-7-standalone-upgrade/7a25341/logs/undercloud/var/log/extra/rpm-list.txt.gz -> python2-tempestconf-2.1.1-0.20190424160311.e0d5dd6.el7.noarch is used.
On first run tempest is passing and that time flavor with disk =1 is getting created but on second time, python-tempestconf looks for the flavor by name (remember two flavor with same quote might exists), so it might be tempestconf discovering the flavor with disk < 1 http://logs.openstack.org/67/656967/4/check/tripleo-ci-centos-7-standalone-upgrade/7a25341/logs/undercloud/home/zuul/tempest.log.txt.gz#_2019-05-04_22_36_50 which is leading to failure.
It might be a bug in tempestconf as we need to find the flavour differently here making sure it's disk> 0.
Above workaroud is not going to work as in upgrade job we run tempest twice and here http:// logs.openstack. org/67/ 656967/ 4/check/ tripleo- ci-centos- 7-standalone- upgrade/ 7a25341/ logs/undercloud /var/log/ extra/rpm- list.txt. gz -> python2- tempestconf- 2.1.1-0. 20190424160311. e0d5dd6. el7.noarch is used.
On first run tempest is passing and that time flavor with disk =1 is getting created but on second time, python-tempestconf looks for the flavor by name (remember two flavor with same quote might exists), so it might be tempestconf discovering the flavor with disk < 1 logs.openstack. org/67/ 656967/ 4/check/ tripleo- ci-centos- 7-standalone- upgrade/ 7a25341/ logs/undercloud /home/zuul/ tempest. log.txt. gz#_2019- 05-04_22_ 36_50 which is leading to failure.
http://
It might be a bug in tempestconf as we need to find the flavour differently here making sure it's disk> 0.