84e016edb3
Fixing vbmc_setup.yaml for c8 scenario012-standalone job with this patch. vbmc_setup.yaml was originally written for c7 multinode[0] to install virtual BMC and a libvirt domain on the controller for ironic to manage. In scenario012 we are trying to test something close to ironic in overcloud(Blueprint[1]). In the past, We have moved scenario012 mutinode to standalone job and reused vbmc_setup.yaml. The shell script in vbmc_setup.yaml need following modification as its now a C8 standalone job:- * Added 'set -e' so that script exits immediately if a command exits with a non-zero status so it would result in deployment failure. Currently deployment is passing even if some commands in the bash script are failing. Addition of 'set -e' will correct this behavior. * Replaced yum with dnf as yum not present in Centos8. * No need to override resolv.conf entry as standalone job already configure necessary nameserver entries. * No need to install additional repos as as standalone job already configure necessary repos. * When vbmc_setup.yaml was introduced intention was to do non-kvm emulation[2] and that was the reason qemu-system-x86 and qemu-kvm-ev was pulled from epel, but for c8 these packages are no longer available in repos [3] including epel. We can use qemu-kvm package instead and we will no longer need epel repos. * create-node.sh command option to use qemu-system have to be removed as qemu-system-x86 package is missing and we are using qemu-kvm instead. * Temporary workaround[4] to upgrade ansible in the neutron container can be removed as ansible version in container is now v2.5.8+. Test patch for tripleo-ci-centos-8-scenario012-standalone is here[5]. [0] https://review.opendev.org/#/c/485261/ [1] https://blueprints.launchpad.net/tripleo/+spec/ironic-overcloud-ci [2] https://review.opendev.org/#/c/485261/29/ci/common/vbmc_setup.yaml [3] https://bugzilla.redhat.com/show_bug.cgi?id=1715806 [4] https://review.opendev.org/#/c/579603/ [5] https://review.opendev.org/#/c/724119/ Change-Id: I9e9d63a7ef2ef538f3c072e3f4a96ec25d7dc5f7 Closes-Bug: #1875681 |
||
---|---|---|
.. | ||
common | ||
environments | ||
scripts | ||
README.rst |
README.rst
TripleO CI environments
TripleO CI environments are exclusively used for Continuous Integration purpose or for development usage. They should not be used in production and we don't guarantee they work outside TripleO CI.
For more informations about TripleO CI, please look: https://github.com/openstack-infra/tripleo-ci