[Starlingx-discuss] [Containers] Sanity Test - ISO 20190522
Lemus Contreras, Cristopher J
cristopher.j.lemus.contreras at intel.com
Thu May 23 20:48:54 UTC 2019
Hi Cindy,
I ran those steps and we were able to do the resize on AIO. I think that it has been discussed multiple times, but, will this be enabled by default in the near future? Will it remain disabled?
Thanks & Regards
Cristopher Lemus
From: "Xie, Cindy" <cindy.xie at intel.com>
Date: Wednesday, May 22, 2019 at 7:33 PM
To: "Perez Ibarra, Maria G" <maria.g.perez.ibarra at intel.com>, "starlingx-discuss at lists.starlingx.io" <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190522
Maria,
Nice to see that sanity is much better today. For the only bugs you were hitting and causes your ~30 cases fail:
https://bugs.launchpad.net/starlingx/+bug/1824412
can you please follow Gerry Kopec’s comments in 5/7:
You should be able to change the config option and retest.
system helm-override-update nova openstack --set conf.nova.DEFAULT.allow_resize_to_same_host=true
system application-apply stx-openstack
Once the nova pods are restarted you should be able to see the conf option set inside one of the nova pods and can retry the test:
kubectl exec -it -n openstack <nova-api-osapi pod name> cat /etc/nova/nova.conf
I think overall we'd want to turn this to true in all environments as that was the behaviour before in the non-containerized setup.
According to Zhipeng, who tried the method in SH side, it works. Please help to verify.
Thx. - cindy
From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com]
Sent: Thursday, May 23, 2019 8:15 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190522
Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-MAY-22 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190522T013000Z/>)
Status: YELLOW
======================
Bare Metal environment
======================
AIO - Simplex:
Setup 03 TCs
Provision-Containers 01 TCs
Sanity-OpenStack 49 TCs | 3 TCs FAIL
Sanity-Platform 11 TCs | 3 TCs FAIL
------------------------------
TOTAL: 64 TCs
AIO - Duplex:
Setup 03 TCs
Provision-Containers 01 TCs
Sanity-OpenStack 52 TCs | 3 TCs FAIL
Sanity-Platform 09 TCs | 5 TCs FAIL
------------------------------
TOTAL: 65 TCs
Standard - Local Storage (2+2):
Setup 03 TCs
Provision-Containers 01 TCs
Sanity-OpenStack 52 TCs
Sanity-Platform 09 TCs
------------------------------
TOTAL: 65 TCs
Standard - External Storage (2+2+2):
Setup 03 TCs
Provision-Containers 01 TCs
Sanity-OpenStack 52 TCs
Sanity-Platform 05 TCs | 2 TCs FAIL
------------------------------
TOTAL: 61 TCs
===================
Virtual Environment
===================
AIO - Simplex
Setup 03 TCs
Provisioning 01 TCs
Sanity OpenStack 49 TCs | 3 TCs FAIL
Sanity Platform 07 TCs | 2 TCs FAIL
------------------------------
TOTAL: 60 TCs
AIO - Duplex
Setup 03 TCs
Provisioning 01 TCs
Sanity OpenStack 51 TCs
Sanity Platform 05 TCs | 4 TCs FAIL
------------------------------
TOTAL: [ 61 TCs PASS ]
Standard – Local Storage
Setup 03 TCs
Provisioning 01 TCs
Sanity OpenStack 52 TCs | 1 TCs FAIL
Sanity Platform 05 TCs | 4 TCs FAIL
------------------------------
TOTAL: [ 61 TCs PASS ]
---------------------------------------------------------------
VM resize failed by "No valid host was found" https://bugs.launchpad.net/starlingx/+bug/1824412
Some pods are failing, tomorrow we’ll perform double check to determine if it is a suite's problem.
For more detail of the tests: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests#Sanity-OpenStack
Regards!
Maria G.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190523/92c2daa5/attachment.html>
More information about the Starlingx-discuss
mailing list