CnetOS 9 packages were already released in the puppetlabs repo.
This removes the workaround to use RDO packages, which was earlier
added to run integration jobs on CentOS Stream 9 before the packages
CentOS has published the official mirror for CentOS Stream 9 . In RDO,
we are working to get ready for it ASAP and we have the required repos
to run p-o-i on CS9 .
This patch is adding support to CS9 in p-o-i repo with the required
fixes. Also is adding integrations jobs for scenarios 0-4 and adding
them as non-voting. Note that we don't have promotion pipeline working
so i think it's better to not make it voting yet.
With  epel-next-release added as weak dep
to epel-release, so now epel-release cannot
be removed alone due to below error, so let's
used dnf/yum for removal as that will clean
the deps too.
epel-release = 8-11.el8 is needed by (installed)
We already disable for CentOS8, let's do for CentOS9
too for same reasons.
Removed VERSION_ID check as both supported C8 and C9
need to be ignored, and same should be there for future
We already have OpenStack Victoria releae available in cloud archive
so let's switch our master tests to that latest version.
Since Victoria release is only available in Focal this change also
switch base Ubuntu version from Bionic to Focal.
We randomly see issues while running sealert
in RDO puppet promotion pipeline, sealert fails with:-
"SELinux is disabled or we can't open a policy file"
As per logs selinux is enabled and selinuxfs is mounted
so seems it's some filesystem issue.
Locally was able to reproduce only with selinux disabled
or umount /sys/fs/selinux. Adding retries in hope to
fix these random failures.
Since the modules are git cloned when installed via r10k and
clones may fail due to some network glich, adding retries should
help in these cases.
We randomly hit failures during git clone in RDO promotion
jobs running on ci.centos.org, adding retries to r10k
installation to handle those random failures.
Added function 'retry_cmd' which can also be used
with other commands.
r10k commands where updated in , and file name in install_all was
wrongly changed to Puppetfile1 instead of Puppetfile.
The environment parameters, PUPPETFILE_DIR and PUPPETFILE is no longer
valid in r10k command, so should be replaced by options, --moduledir
mariadb has been updated in RDO CentOS7 for Ussuri so we can bump
puppet-mysql and use the same Puppetfile for all cases, no more
exceptions for CentOS8 are needed.
I98fc088cd87c1412544f9590ce7a925b413297e2 broke unit 5.5 for
puppet-tripleo and probably puppet-pacemaker, since it can't find the
Puppetfile by default anymore.
- scenario001 and 004 will be running without ceph
until ceph repos get available for CentOS8
- scenario003 will run not run with linuxbridge until next CentOS
minor version as it has issues:-
- Add Puppetfile_centos7 to have different puppet modules
as compared to other distros. Currently only puppet-mysql
needs to be kept pinned for centos7 as newere mariadb version
is required to remove the pin, CentOS8 and ubuntu have required
mariadb version so pin is removed. So automatic updates of puppet
modules will not be applied for CentOS7 as those jobs are going to
be removed in coming months.
- check for rdo_dlrn url existence only for RedHat distros.
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
Disable SSL as currently there are known issues in services
to work with python3 + SSL on Fedora.
Also fixed following:-
- watcher to work without SSL
- Handle source /etc/bashrc for users don't have .bashrc created
- Install python3-rbd in Fedora and RedHat > 7
In puppet 6 they have moved out a lot of builtin
resources to their owns modules since they didn't
belong in the Puppet core however in deb/rpm packaging
they are still bundled in but not when installing from
So we must add them in here so that they are available
in our unit tests.
Add puppet6 testing and run all those on Ubuntu Bionic.
Change from Xenial to Bionic for all other default jobs.
Run libraries unit for 6.0 on Ubuntu Bionic.
We now have support to Mimic and can select that version
and this patch fixes Puppet 5 for Bionic we can add it to CI.
When this is fixed the only thing left is to add beaker acceptance
testing for Bionic.
Bionic only has Puppet 5 and can currently only use Ceph Mimic.
Also modify provision manifest to skip provisioning
The new scenario will be used for testing py3 services
starting with keystone and glance.
Also update puppet-apache reference to the required commit,
this can be updated once a new tag is released with the commit.
We are closing in on adding Ceph Mimic support and
want to ensure we can select either Luminous or Mimic
for running our tests.
For example Ubuntu 18.04 must run Ceph Mimic because
Luminous is not available (yet), Debian doesn't have
Ceph Mimic packages so we must run Luminous there.
This change makes sure the latest puppet5 version
is used when running integration jobs for puppet5.
The puppetlabs yum mirror is ready to be used and
has the proper packages and is mirrored, example:
For the puppetlabs apt mirror the puppet5 pool is
needed before this will work. A patch has been fixed
for that here . Therefore this change cannot be
merged until  is merged.
At first, I thought this would go in puppet-ceph, but in fact,
every compute node needs a librados dependency which is in the
Ceph repo. So at then end, all nodes need GPG-KEY-ceph, so it
is a good idea to install the repository key there.
Nodepool images no longer have Puppet in them anymore so there
is no point in removing files and packages which are not there
anymore in the first place.
It appears that the puppetlabs Debian repository is set to always
install a repository for Xenial (instead of using lsb_release to
find the OS), and that the Puppetlabs repo GPG key is outdated. This
patch fixes that.
This patch moves in the Puppet OpenStack integration
jobs as well as the module tests in-repo.
The command "r10k puppetfile install -v" fails with:
Unrecognized options: verbose.
Rework the command to be compatible with the r10k 1.1.4.
Signed-off-by: Bogdan Dobrelya <email@example.com>