Follows the same configuration that was used on
tripleo-quickstart-extras and documented use on tripleo-docs.
Change-Id: Iba8a2db92137f9f6ad28f498627eb1b87039d99f
Story: https://tree.taiga.io/project/tripleo-ci-board/task/381
Debug unbound DNS queries in job for investigation of
DNS failures.
Dump unbound DNS cache server cache..
Depends-On: Ia76ac9b20d6b8402060b71e11e00e515bc74077d
Related-Bug: #1730931
Change-Id: Ic8b9e33067141366655fad1b99dee1adb40dfba3
- Collecting /etc/machine-id is useful to make sure we have it in our CI jobs.
- Verify file size is not zero otherwise create the machine-id again
Change-Id: I5403337e735b6a4967bfff2173ab681517404a24
We rightfully import the remove-machine-id element during the instack
bootstrap, but with multinode job it can create a vm without
/etc/machine-id as it's not restarted. This can cause issue with nova
not finding any valid host due to this missing file.
Change-Id: Ieb5ad6ad429c8388a1cbbd650339b6eecd9b7997
Closes-Bug: #1718387
Co-Authored-By: Michele Baldessari <michele@redhat.com>
requests-2.16.5 has added urllib3 package as dependency. Requests is
being installed using pip as dependency for git-review in DIB.
This parch removes urllib in node preparation for puppet jobs as it
will be installed as requirement for requests rpm package.
This patch should be a workaround until git-review is removed from
nodepool images.
See comments on https://review.openstack.org/#/c/468823.
Change-Id: Ia839cac125e2a749fc9ce40894e5900237ec3ae1
We shouldn't be using packages from any of these, and they can cause
package conflicts with the delorean repos we do want to use.
For some reason centos-release-* also matches the base centos-release
package, so we need to explicitly match only packages where the
following characters are a-z.
Change-Id: I928a0efc9d75e584889967e262155e576452632d
Closes-Bug: 1685814
These are various improvements to tripleo-ci (squashed into a single
commit to save CI resources) that enable running the tripleo-ci entry
point script which is now toci_gate_test-oooq.sh locally in a standalone
environment of vm's not spawned by nodepool.
This is useful to developers trying to reproduce CI locally for
development and testing.
The changes are:
- Default $REMAINING_TIME in common_vars.bash
- Don't hardcode the jenkins user everywhere
- Improved initial package handling:
Before blindly yum installing the packages needed by these scripts in a
few spots, check if the packages are already installed with just the rpm
command. This can end up saving a decent amount of time when iterating
on running these scripts locally. Also installs wget.
- Reinstall python-requests
When locally running toci_gate_test.sh, python-requests needs to be
reinstalled since toci_gate_test.sh removes the python module as it
was pip installed on the infra provided image. Also updates the
logic to handle the python-requests -> python2-requests transition.
Change-Id: I48cd1e5f53b86455992b83248d57f5338c29a7ca
Currently, tripleo-ci scrips clean up repos removing rdo-release
rpm, but https://review.openstack.org/#/c/453325 moved base image to
use centos openstack release rpm instead of rdo-release.
This patch removes all centos-release-openstack packages in addition
to rdo-release. Note that yum returns 0 even if no matching packages
are found so this should be ok.
Change-Id: I825038eeb134590fe9bb68697a193e5c6626f991
Closes-Bug: #1685418
OpenStack Infra provides images with rdo-release and puppet packages,
which is something we don't want in TripleO CI because we already have
our own packages from local mirror, depending of the version of
OpenStack that we want to test.
This patch makes consistent the cleanup on both OVB & multinode jobs to
remove puppet & rdo-release packages.
Closes-Bug: #1670015
Change-Id: I5f6b6be6f07dfd7d27189547db9daf1594db8c85
We no longer use anything from openstack-heat-templates so having
this included is just preventing us from dropping the dependency.
Change-Id: I94bd0c203e3d6dbfab5c24fffde56b9cf34af7e1
An use case for TripleO CI can be to test changes on an
specific feature branch. In that case, the packages need to be
consumed for that specific branch, instead of master.
This change enables the detection of a feature branch in the
current change, and enables the related repositories (they will
default to master if the feature branch for a repo does not exist)
Also update ELEMENTS_PATH properly to consune latest
features from diskimage-builder
Change-Id: I701c01dd18023c0c05aede9d06b6b1380b6f2386
Needed-By: I0ca6a4ae3a2684d473b44e5f332ee4225ee30f8c
This script is meant to be able to be used standalone as well as from
tripleo-ci. The $STABLE_RELEASE variable needs to be defaulted to an
empty string otherwise the script will fail since it is set -u.
Change-Id: I6aa8bd3b01b1147de9b45f40ded8318fb46dcaf8
Use the new --image-name argument to tripleo-build-images to get just
the overcloud-full image, simplifying the jq expression.
Change-Id: Ia60fe3643efe6a0b4010172717e43bc69cc513be
Depends-On: I5644656bbdc534f54c254edc7e939ae36f1f98ca
Commit Ia1a3fa071c07d8a60c69f32375ac6b0aa92cff7b changed the name of the
images in the yaml definition files from overcloud to overcloud-full.
This updates the bootstrap script accordingly.
Change-Id: I35954ff424b945f1ba4f4ef2bbd29f404e292f9a
python-requests needs to be reinstalled in bootstrap-overcloud-full.sh
if it was already installed in order to make this script idempotent.
Otherwise, yum sees the package as already installed and does not
reinstall it again after we have rm'd the files (which we do to clean up
the previous pip install).
Change-Id: I6dd6676ae9a53a31afeaec43d242a33e072b4a94
Currently we always build from source, but the latest master is now
available via delorean-current since o-p-m was broken into per-module
packages.
This should reduce the time taken to install everything from source,
and also provide a better path wnen upgrading as a simple
openstack undercloud install or yum update will update to the latest
puppet modules (currently failures happen if you forget to run via
tripleo.sh because the puppet modules aren't upgraded but things
that depend on the puppet modules are).
Also disable usage of the overcloud image cache as I have no idea what
will happen if we mix an image with puppet modules deployed from source
with ci scripts trying to install packaged modules.
Change-Id: Ie4cae6b884b2e539545371b9f716903b8fe5cf1f
Closes-Bug: #1597438
Temporarily remove epel-release, and don't enable epel via tripleo.sh.
Also remove nodejs and nodejs-devel. This is a quick fix for:
https://bugs.launchpad.net/tripleo/+bug/1606685
We have a CI dependency on EPEL too with moreutils, so that needs
to be installed before we remove epel. Since everything is running
on the Jenkins slave that should be okay for now.
The proper fix will be to remove epel more completely going forward:
https://review.openstack.org/347499https://review.openstack.org/347513
Co-Authored-By: Ben Nemec <bnemec@redhat.com>
Change-Id: I91eff35586547dd278e8a32668f06efb840fc8c6
Partial-Bug: #1606685
This would allow using multinode jobs spawned by nodepool, but that is
not the only use case. Any cloud provider could be used by this setup,
including a 3rd party CI setup.
The scripts here are modified to support installing the undercloud
directly on the node running the toci_gate_test.sh script, which is
often the jenkins slave. When deploying an all in one Overcloud this
results in needing 2 nodes total to do the basic TripleO deployment.
There is a new script named toci_instack_multinode.sh to run the
multinode setup.
Change-Id: Icc67a289df207348536c0a2419b3fc81f03fe758
Sagi Shnaidman