| Age | Commit message (Collapse) | Author | Files | Lines |
|
According to recent IRC discussions is could be useful for haclient.
Partial-Bug: #1934753
Change-Id: I670fa84476e35e55cbed2d22e48836ed5e28495f
|
|
As a project we never built RHEL based images so support for them
was not tested.
Change-Id: I27dfe34ade088228d71f6857ec4f3ab28ee63915
|
|
* Use distribution based dumb-init package.
Change-Id: I75927b6016bdb7577fbff354632bdab6407f359c
Related-Bug: #19311980
|
|
- install all 'centos-release-*' packages we need
- disable all repos in one place
- do not import CentOS keys - they are trusted by default
Change-Id: I97308c74406d2af0e39b77eddef2693554381ab6
|
|
We do not test support for ppc64le on CI or other systems.
In previous cycles it was used by TripleO and now they have own way.
Change-Id: Ibd955869a6f9485dfa4d08a8ad2f4b28b7d59c15
|
|
Change-Id: I320d0795ce11ca00398cec6183ed140d31d3fd80
|
|
We allow users to use own image as base one and then we check is it
proper distribution version one. And this check is done in different way
for CentOS and different for Debian/Ubuntu systems.
This patchset uses PRETTY_NAME from /etc/os-release for check. And it is
done before anything gets installed so if wrong distribution is used
then build process breaks as soon as possible.
Change-Id: I22db3cd4cb608332261824626e3b8768821b8dd0
|
|
It was missed previously.
CI did not detect it because it ignores apt security issues.
That gets fixed in Ic5abc4b87fd76f87aba383abf43e95ba70629fcb
Change-Id: I11256c674c42e35496146ff64fee1e8e04c30d2c
|
|
Bullseye is now in hard freeze cycle and goes for release.
https://release.debian.org/bullseye/freeze_policy.html
Co-Authored-By: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I543965a2741cebfa759576a4c75669a7bacd4208
|
|
bintray is being shut down 1st of May 2021, rabbitmq docs direct
users to packagecloud - so let's move.
Change-Id: I499251d13ca77aea2215f8a879b7bb8dd51f1c9f
|
|
With RDO use we did not disabled some repositories. This patch disable
them and enable where needed.
Change-Id: Ia9d537fe9c1ad54789d2bfb4027254fbb3defe7e
|
|
|
|
We want to have all uses of curl behave the same so we ship config file
for it in all images.
So do it at start of image so 'base' makes use of config too.
Change-Id: I95aa64f0b292cd020574dbedd320ef90529cc7a4
|
|
Change-Id: I50e5355bd7dd96a5eeaa004c5fc230d1cb8e8fd2
|
|
|
|
|
|
healthcheck_socket script requires lsof to check pids of processes
using that socket - that's needed for octavia-driver-agent healthchecks
in Kolla-Ansible.
Change-Id: I0f14c0f67fd81f13c58f231f800829ad759cc54c
|
|
We use official CentOS 8 Stream image as a base.
So far Stream does not have own SIG repos
RDO Wallaby packages will be built against Stream
Kolla CI jobs are renamed to centos8s. Kolla-Ansible ones will follow
in later patch.
Change-Id: Ibb23c9d0caf115fcbba7bd322ecebe8d80b6821a
|
|
This reverts commit 61def281d077f88051d1b1a14dfdbfabac036c8c.
Reason for revert: --location was already in curlrc and it was unified in change I46b77978926fc2b578a68d1aaa944b2198af0685
Change-Id: I066d747400ede30037ff324ad55430af7c35dc18
|
|
-L for curl: If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place
It fixes build error for me:
INFO:kolla.common.utils.prometheus-v2-server: ---> Running in 693fd4095c77
INFO:kolla.common.utils.prometheus-v2-server:curl (https://github.com/prometheus/prometheus/releases/download/v2.23.0/prometheus-2.23.0.linux-amd64.tar.gz): response: 302, time: 0.166583, size: 640
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:gzip: stdin: not in gzip format
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:tar: Child returned status 1
INFO:kolla.common.utils.prometheus-v2-server:tar: Error is not recoverable: exiting now
Change-Id: I095ca6f34cc7c7bca485e9ec019cc52aeb8e3ff4
|
|
User may provide own base image but it needs to be supported one. If it
is not then we print info and error out.
So provide user with info which release is present in their image.
Change-Id: I0d8417fdeb2f02138d03cc57bd3b7b95bc43fc8f
|
|
Debian still needs it but it is enabled for all architectures.
Change-Id: I6a3ba599af3deedd450b4ffff6b86a0c04628340
|
|
This repo is only needed for source openstack-base.
Change-Id: I835c18424153f8529a37fc78e16d2becacb71263
|
|
Backport this until Train.
CentOS 8.3 renamed system repos. [1]
This caused failures when disabling and enabling.
More details in the referenced bug report.
Notice CentOS 8.2 and below will no longer work.
[1] https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2011#Yum_repo_file_and_repoid_changes
Change-Id: I2d67b3ed7b7c521bc755ec9a87365c9962a9eeff
Closes-Bug: #1907213
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
Depends-On: https://review.opendev.org/766211
|
|
Currently we use couple of curl options throughout Dockerfiles, this change
adds all common options to curlrc (-sSLf) and removes usage of those in
Dockerfiles.
Change-Id: I46b77978926fc2b578a68d1aaa944b2198af0685
|
|
There is small subset of images where we need to know which install_type
or install_metatype is used. So add them only there (and their
children).
Change-Id: Ib7d5e36b958d6c8daf2989df32e29fa24b46c62a
Implements: blueprint infra-images
|
|
* "Use distribution-provided pip"
* "Use python's pip module invocation method"
* "Install pip earlier in order to avoid multiple installation"
* "Remove pip_version variable requirement and call"
Change-Id: Id0e738044a1931f9d611a7281a48ea4a593f1cf1
Closes-bug: #1893204
|
|
|
|
td-agent 4 got released for all distributions we support. For both
x86-64 and aarch64 architectures.
Change-Id: I86ecdc1ac45dfd76b94a34d1b837f7c0bc975dcd
|
|
|
|
Elasticsearch and Kibana 6 are used on all distros, but Logstash
is still pinned at 2 which is not compatible. See the product
compatibility matrix [1].
[1] https://www.elastic.co/support/matrix#matrix_compatibility
Partial-Bug: #1884090
Change-Id: I1579e762bcfb07f0baa73507eb9955ae2f83c4ec
|
|
It has been deprecated in Ussuri cycle.
Change-Id: I6d3174e8b52cb4d1f2eca4d85d506665dafe2406
|
|
A bit like we did for I3e0e86026f5a4a78473bed824cd1682d3a020cd5 we
should remove the nss-systemd lookup from containers. The reasons for
this are as follows:
1) Just like for I3e0e86026f5a4a78473bed824cd1682d3a020cd5
when this nss module is triggered it tries to talk to dbus.
It triggers a bunch of selinux denials and it makes little sense
to open all containers to talk to dbus.
In particular, if a container is run as non-privileged and bind-mounts
/run from the host, we will hit selinux denials like the following:
type=USER_AVC msg=audit(1592337775.860:74119): pid=1284 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_call interface=org.freedesktop.DBus member=Hello dest=org.freedesktop.DBus spid=406228 scontext=system_u:system_r:container_t:s0:c162,c886 tcontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'UID="dbus" AUID="unset" SAUID="dbus"
2) It just makes little sense in a kolla-world to have containers
talk to dbus/systemd and it saves us some time when a lookup triggers
the systemd module for whatever reason. Especially because the
nss-systemd module does a few things which are not useful in a container
(ensures that the root and nobody users and groups remain resolvable,
SystemD's DynamicUser= feature, provide Lookup API via Varlink)
The sed regex gives us the wanted results:
$ diff -u /etc/nsswitch.conf.orig /etc/nsswitch.conf
--- /etc/nsswitch.conf.orig 2020-06-19 07:18:10.974580755 +0000
+++ /etc/nsswitch.conf 2020-06-19 07:20:12.260230103 +0000
@@ -53,9 +53,9 @@
# group: db files
# In order of likelihood of use to accelerate lookup.
-passwd: sss files systemd
+passwd: sss files
shadow: files sss
-group: sss files systemd
+group: sss files
hosts: files dns myhostname
services: files sss
netgroup: sss
Related-Bug: #1883849
Change-Id: I81e5b7abf4571fece13a029e25911e9e4dece673
|
|
|
|
|
|
CentOS 8.2 has Erlang and RabbitMQ available in 'messaging/rabbitmq-38'
repository. We use it to grab Erlang while RabbitMQ comes from upstream
(like on x86-64).
Change-Id: I2559267d120081f2e5eabc9d966b019517a5ad5d
|
|
|
|
Fix offline installation of language pack packages.
Change-Id: I9f4a21bbf1c8383e21e59350206aba3424602270
Closes-bug: #1883233
|
|
It's still using temporary mirror in RDO infra, but now that packages
are properly synced to CentOS mirrors, let's switch to use it.
Change-Id: I913efffe6a1d8a0210b1158261c77d0d45ac3147
|
|
Let's get rid of this warning:
Change-Id: I121e2ecb30ec6e8d1b6d88d9b921894438c3e094
INFO:kolla.common.utils.base:ESC[91m[WARNING]: Empty continuation line found in:
INFO:kolla.common.utils.base: RUN dnf -y install centos-release-opstools epel-release dnf-plugins-core && dnf config-manager --enable PowerTools && dnf config-manager --disable centos-ceph-nautilus && dnf config-manager --disable centos-nfs-ganesha28 && dnf config-manager --disable influxdb && rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-OpsTools && dnf -y distro-sync --security --sec-severity=Important --sec-severity=Critical
INFO:kolla.common.utils.base:[WARNING]: Empty continuation lines will become errors in a future release.
INFO:kolla.common.utils.base:ESC[0m
INFO:kolla.common.utils.base:Step 1/39 : FROM centos:8
|
|
'messaging-rabbitmq' and 'opstools' are enabled by RDO
delorean-deps.repo file
'influxdb' was also enabled
Depends-On: https://review.opendev.org/728687
Change-Id: Ibb0a7edc9e5632c1b89a7d52601f55a223b49dfb
|
|
There is a repo with binary packages for Ussuri. Let us use them instead
of Train ones.
amd64 only
Change-Id: I071eebc4f60094d881a68e201e8c3bb6e6742ff5
|
|
|
|
Change-Id: I31e9742793cfb1abff9749083c9ce86000dae1af
Partially-Implements: blueprint centos-rhel-8
|
|
This is a follow up to I8b52b2630a72393bf4b9c7095fc67db6c36c27fa, which
upgraded elasticsearch and kibana to 6.x. It did not enable the
repositories or images for CentOS 8 however.
This change enables elasticsearch and kibana images for CentOS 8.
Change-Id: I7b375e493380c4e3d6b8c7b6f5ebc57c1b73043f
Related: blueprint elasticsearch-kibana-version-upgrade
|
|
With the move to RHEL/CentOS 8 we no longer have Python 2 in our images
so there is no need for checking which Python version (2.x or 3.x) is
used inside of containers.
We also no longer have to support yum as a value for
distro_package_manager.
Partially-Implements: blueprint centos-rhel-8
Change-Id: Ie45cf3465fedddbde7856961527421883ba3d5c9
|
|
Change-Id: I98147939ccfeeb7b3e86b5e33c427372663ecf9b
|
|
Upgrade and pin RabbitMQ to 3.8.
Upgrade Erlang to 22 to meet requirements:
https://www.rabbitmq.com/which-erlang.html
Start using bintray repository provided by RabbitMQ.
Linaro builds will be used for aarch64.
Implements: blueprint rabbitmq-version-upgrade
Closes-Bug: #1848452
Change-Id: I3d775fd832f2603181da89009cebc1370a61a023
|
|
Adds collectd-dpdk_telemetry and collectd-logparser packages
to collectd RHEL-based image. dpdk_telemetry plugin collects DPDK
ethernet device metrics via dpdk_telemetry library. Logparser is
plugin for filtering and parsing log messages.
Change-Id: I0c7c94e9fae9d11660f938b8d7d6be0f270c972f
|
|
Upstream kibana package contains NodeJS x86-64 binaries so can not be
used directly on non-x86 architectures. I took upstream packages,
removed NodeJS binary from it and added 'nodejs' dependency.
Package is present in my Linaro OBS repository where I keep other
packages needed for aarch64 kolla run. Via APT pinning I mark them as
not wanted so they are not used on any architecture with two exceptions:
1. libvirt - we need fixed version to be able to use ThunderX servers
2. kibana - to be able to run it at all
For x86-64 upstream kibana package is used.
Closes-bug: #1867365
Change-Id: I456402849022100bde1fffdfbf6292b35690f0f2
|