| Age | Commit message (Collapse) | Author | Files | Lines |
|
Added the --local_cell argument to nova db sync commands during
bootstrap and upgrade.
This was previously thought to have no effect [1], but has since been
discovered to fail when rotating the nova database password.
[1] https://opendev.org/openstack/kolla-ansible/src/branch/master/ansible/roles/nova/tasks/bootstrap_service.yml#L2-L3
Closes-Bug: #2045558
Change-Id: Ic64eb51325b3503a14ebab9b9ff2f4d9caec734a
(cherry picked from commit de1487f05187387aea3f113dcbb6926734b1ce6b)
|
|
The grafana opensearch datasource was missing from the docker image.
This commit installs the datasource plugin.
Change-Id: Ia3a39c975abf815a66765f2f98c4789d6cec33d7
(cherry picked from commit a97a561bab1573b0ed19d91f827a8bbde9ed8165)
|
|
* Use structure that allow for custom package version and base URL.
Change-Id: I169e51c0f5c691518ada1837990b5bdd2a3d1481
Closes-bug: #2020761
(cherry picked from commit 7f38e1df71eafb250b14c4e125c7313bd9218f7d)
|
|
When adding a dashboard to grafana the containers aren't restarted when
they should be. This is due to a bug in Kolla where the logic to
determine whether or the container needs to be restarted fails in the
case where the file does not exist in the container. This patch adds
more comprehensive checks for container restarts in the set_configs.py
file. This patch also adds a test to ensure that the functions work as
expected.
Closes-Bug: #1997984
Co-Authored-By: Will Szumski <will@stackhpc.com>
Change-Id: I67f5f12700d7b55f26bff81e9b54559303da6d83
(cherry picked from commit d9a6c5f3901e078a30d341397ac57d867d8191cc)
|
|
Calls to `ovs-vsctl` in `ovs_ensure_configured.sh` did not get checked
for errors.
This can cause false success statuses when
the script is run by automation tools such as ansible.
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/870540
Closes-bug: #1999778
Change-Id: Iad83132b61efadbf09aa9aa2edf96235085764c6
(cherry picked from commit a840ac0d7c8777a8198ae40cbb79b65c5fffd7e1)
|
|
Change-Id: I7f0c1a5abeab0143aa103b742319cfef863f9aa9
(cherry picked from commit 9e06e70ebb7f4afb07a5fa5c193e2a9c04e577db)
|
|
- fixed amount of quotes to make them work
- fixed Debian/Ubuntu rabbitmq/erlang info
- fixed syntax in Ansible update
Change-Id: I2730c6336ca3029c411e497b0851109eaec0e249
|
|
|
|
Support has been dropped in kolla-ansible, the upgrade path is opensearch.
Change-Id: I6f32aacb4e0b7dd1eb7206e02425b16f5beae4f0
|
|
Monasca, kafka, storm and zookeeper have been removed in kolla-ansible [1],[2].
[1]: https://review.opendev.org/c/openstack/kolla-ansible/+/861392
[2]: https://review.opendev.org/c/openstack/kolla-ansible/+/865029
Change-Id: I0958a9353bc4585c4f65a1d316328a0e80b0b8b7
|
|
Change-Id: I1dd9651e1c8ac199cf8ef27de3338e5d3ebec24d
|
|
Handles x86-64 and aarch64 targets.
Change-Id: I70e2bb1d2744d38e08f5a9a79ab6a7265ebf24c9
|
|
Change-Id: I947a0b9155fea18a7781f694dbeafc49033fef8e
|
|
Fixes a hypothetical security issue related to privilege escalation via
rootwrap/privsep. A potential vulnerable service could previously allow
writes to its rootwrap/privsep config and thus allow for more commands
to be run with root privileges via rootwrap/privsep. For a succesful
attack, this would also require the service to allow to run arbitrary
commands via rootwrap/privsep. Thus far, no such vulnerabilities have
been reported and thus this fix is simply strengthening the container
images against such an issue in the future.
Change-Id: I92c81c77e6a16570a108cde8031f7977930fb02a
Closes-Bug: #1874298
|
|
Swift deployment is broken since CVE-2022-38060 fixed sudoers file in
the I66476a2b396e2cbe41e68ac51f57aae1806b2ed8. The kolla-toolbox
container have their own virtualenv path differs from all other
containers. This change adds the correct sudoers secure_path
configuration needed only for kolla-toolbox conainer.
Related-Bug: #1985784
Change-Id: I3651576ee354364d639c187ff750491667ecab56
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
|
|
Adds a deprecation notice for Monasca service in Kolla with its
dependencies: Kafka, Storm and Zookeeper.
Change-Id: I8f08abb1722e558e3874fd7d92322598d55de563
|
|
Change-Id: I13e3cf5a02dadcedd1ebbd54d56f7f633e6e3d68
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/859570
Change-Id: I7af51d07b8a939c908aa072294061def57dd67de
|
|
The goal of the swtpm project is to provide a TPM emulator (TPM 1.2 &
TPM 2) that can be integrated into virtualized environments, such as
virtual machines and containers.
Nova supports it for quite a while:
https://review.opendev.org/c/openstack/nova/+/631363
Change-Id: Ifb7e0f1632805807851720873a70179218bdf372
|
|
OpenStack 'zed' requires Python 3.8+ so RHEL 8 family has to go.
This changeset moves to CentOS Stream 9 while move to RockyLinux 9 is
planned as final solution.
CI moved to CentOS Stream 9 nodes.
Depends-on: https://review.opendev.org/c/openstack/kolla-ansible/+/839715
Change-Id: I113b9984294cf8663d3fc0c8840320e1d40ea731
|
|
|
|
|
|
|
|
|
|
blackbox_exporter -> 0.22.0
prometheus_cadvisor -> 0.45.0
elasticsearch_exporter -> 1.5.0
haproxy_exporter -> 0.13.0
prometheus_libvirt_exporter -> 2.3.2
memcached_exporter_version -> 0.10.0
prometheus_msteams -> 1.5.1
prometheus_mtail -> v3.0.0-rc50
mysqld_exporter -> 0.14.0
node_exporter -> 1.3.1
prometheus -> 2.38.0
Change-Id: I3452e8904992bfb977dcae4084a0d98aab82e221
|
|
|
|
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: If7955df1073adadad2d306c3d9b74d1479cd334a
|
|
Closes-Bug: #1985784
Change-Id: I66476a2b396e2cbe41e68ac51f57aae1806b2ed8
|
|
Change-Id: I2a1d97421f53e63bb2e8d93dcdbc9b738e39670d
|
|
Change default 0 retries to 5, that should help for transient
errors (timeouts, HTTP 408, 429, 500, 502, 503 or 504).
Change-Id: Iad3c7270579ffb38299269481ac64d5582abaa22
|
|
3.10 comes with quorum queues support, Erlang 25 is the recommended series.
Change-Id: I67f8df66b4896a9b223c02ed09f68f3f43693849
|
|
|
|
Removes a dependency on RDO for install etcd in CentOS images.
Aligns version of etcd across all distributions, see below:
```
(venv-kolla) [will@juno kolla]$ docker run --rm -it kolla/ubuntu-source-etcd:yoga bash
()[etcd@730a011b670a /]$ etcd --version
etcd Version: 3.2.26
Git SHA: Not provided (use ./build instead of go build)
Go Version: go1.13.7
Go OS/Arch: linux/amd64
```
```
(venv-kolla) [will@juno kolla]$ sudo docker run -it kolla/centos-source-etcd:yoga bash
()[etcd@9aa486c9e94f /]$ etcd --version
etcd Version: 3.2.21
Git SHA: 3ac81f3
Go Version: go1.12.8
Go OS/Arch: linux/amd64
```
```
(venv-kolla) [will@juno kolla]$ docker run --rm -it kolla/debian-source-etcd:yoga bash
()[etcd@b49cb5fcdf87 /]$ etcd --version
etcd Version: 3.3.25
Git SHA: Not provided (use ./build instead of go build)
Go Version: go1.15.9
Go OS/Arch: linux/amd64
```
This will also allow us to update to a more recent version in the
future. We have to be careful not to jump by more than one point release
to ensure compatibility:
https://etcd.io/docs/v3.5/upgrades/upgrading-etcd/#upgrading-an-etcd-v3x-cluster
Change-Id: I62a34256fb7395d0448af169ac3cf036f60cd290
|
|
|
|
Change-Id: I4bd581c3ea422e1c9a075a71721413d47fdbdfe4
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/828902
|
|
Downstream users are often building their own
custom images from their own forked git.
Reasoning can be various - added fixes not merged yet,
some customizations and etc.
Because of this, it's very usefull to have information
about git commit in images, and this is exactly what
that patch does.
If images are built from pip source, kolla_version
LABEL contains kolla version.
Change-Id: If81989603185528dae86df52e8f8d0f94cdca85d
|
|
Skydive versions prior to 0.28.0 panic on newer versions of libc.
Fixed upstream in 0.28, see: https://github.com/skydive-project/skydive/issues/2329
This should be backported to at least xena and yoga, as skydive is
currently not working with centos 8 on these releases.
Closes-Bug: #1940862
Change-Id: I177949b9319a977c9cd9121eb28b710256b72a5a
|
|
This change fixes an issue with 'apt-get update' command and stop
container building with erroneous source repositories.
Change-Id: I5ce2eb66a647e1805f086aa37942bf5d13eb4106
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
Several people use Kolla behind firewall/proxy. Internal mirrors are
often in use then. We do not provide a way to replace repos.yaml file in
an easy way which may lead to complicated solutions or template
overrides.
This patch adds a way to provide own copy of repos.yaml file.
Change-Id: I0b07da22fea27e0ff4e90aaad19e50d84ff9a121
|
|
Adds a relevant reno to inform users about the change and the
possibility to customise the prefix.
Additionally, this patch includes the fix to Ubuntu image builds
regarding rabbitmq and erlang.
Both the changes are required to fix master CI.
Change-Id: I6bc8b489a810849744c8bead6b9e350c5d3e36b7
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/843752
|
|
Change-Id: I793e35ef347c9d44b4e870cd3ca1bd459e557623
|
|
We have 'quiet' mode where only minimal data is printed to the console.
But there were no logs at all then.
This change generates log files (if 'logs-dir' argument is used) during
quiet build.
Also enables 'quiet' mode for CI so Zuul will not have to parse 29MB
JSON file each time.
Change-Id: If7d5c2807f0947a8bbbc1ceb8531c9b9c9287c1f
|
|
The only place where it stays is argument parsing where it gets ignored.
Hardcoded to 'source' to make merging both kolla and kolla-ansible
changes easier.
Change-Id: I6890a7ec7baf507f8acd75b42bbd0fb17c2e4511
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/837620
|
|
A recent change to git [1] introduced a new behaviour to work around a
CVE [2] that disallows any git operations in directories not owned by
the current user.
This may seem unrelated to installation, but it plays havoc with PBR,
which calls out to git to get to get revision history. So if you are
"pip install"-ing from a source tree you don't own, the PBR git calls
in that tree now fail and the install blows up.
When using type=source, kolla clones the repository, then creates a
tarball from it, which is ADDed to the image. The ownership of the files
in the tarball is preserved, which in this case will be the user running
kolla-build. Since the Docker build runs as root, we hit the PBR issue.
Our solution is to make sure that any tarball we generate from git
sources have all files owned by root:root so that the root user is able
to use git commands when building container images.
[1] https://github.com/git/git/commit/8959555cee7ec045958f9b6dd62e541affb7e7d9
[2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24765.
Closes-Bug: #1969096
Related-Bug: #1968877
Co-Authored-By: Mark Goddard <mark@stackhpc.com>
Change-Id: I2cbf1f539880d512aa223c3ef3a4b19ee18854ac
|
|
It is not used in k-a and has never been.
Change-Id: I600cc276ba67d88928e6c2c87810459435b92650
|
|
It was marked deprecated in Yoga.
Change-Id: Iea1cf9c539a73da625e335d6c1adb6cd71ec93d4
|
|
Change-Id: I86d64e6348a7deed67f9271aeca59c599feb57a6
|
|
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: Id9ff668719c6b7510eaf83dd68449d2c84da4054
|
|
|