- Jun 22, 2021
- Jun 21, 2021
-
-
Radosław Piliszek authored
The variable names are awful but this all agrees with the docs now. Closes-Bug: #1933122 Change-Id: Icd3d140473886ba3c4847859cddccdb3c1376818
-
Zuul authored
-
Radosław Piliszek authored
Following upstream which removed ZFSSA support in Ussuri [1]. [1] https://review.opendev.org/c/openstack/cinder/+/690137 Change-Id: Idb311e18b437fba696759ecb1cf2a6b4803aa5c5
-
- Jun 20, 2021
-
-
Radosław Piliszek authored
Kolla Ansible runs iscsid in the foreground (-f) and a recent change to iscsid in CentOS 8 (both Linux and Stream) caused it to reject setting pid file in such a case. PID file is irrelevant in this scenario so this commit removes its parameter. Closes-Bug: #1933033 Change-Id: Ic0c4beae0c812f3ca68a6ee5cc4daa2fee0f277d
-
Radosław Piliszek authored
This reverts commit c6259158. Reason for revert: cAdvisor fails with: invalid value "percpu,referenced_memory,cpu_topology,resctrl,udp,advtcp,sched,hugetlb,memory_numa,tcp,process" for flag -disable_metrics: unsupported metric "referenced_memory" specified in disable_metrics Change-Id: I1a0eea5c20f95f38c707401b56b7d2454484377d
-
Zuul authored
-
Zuul authored
-
Zuul authored
-
Zuul authored
-
Zuul authored
-
- Jun 18, 2021
-
-
Mark Goddard authored
Follow up fix for Ia7e923dddb77ff6db3c9160af931354a2b305e8d, which broke the cephadm jobs. Change-Id: Ieb39b41a6f493bd00c687610ba043a1b4e5945e7 Related-Bug: #1821696
-
Zuul authored
-
- Jun 17, 2021
- Jun 16, 2021
-
-
Piotr Parczewski authored
Adds support for passing extra runtime options to cAdvisor. By default new options disable exporting rarely useful metrics and labels by cAdvisor. This helps reducing the load on Prometheus and cAdvisor itself. Change-Id: Id0144e8fa518e3236cb94ba2e3961fb455d36443
-
wu.chunyang authored
Remove rally role as planned Change-Id: Ic898efe42b21b01c45d4621af2cf90ecd7afc398
-
- Jun 15, 2021
-
-
Zuul authored
-
Zuul authored
-
Radosław Piliszek authored
They are handled by Docker since at least 18.09 (tested). Backport to Wallaby at most to not introduce needless restarts in already stable branches. Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/792583 Change-Id: Ia95355c529f1b0222dc1de06632984b6d130b9ec
-
Mark Goddard authored
Follow up to I5129136c066489fdfaa4d93741c22e5010b7e89d, adding upgrade notes. Related-Bug: #1931615 Change-Id: I2f88b8fc2c6924de9f6bc1840b183ee024c5c1e9
-
- Jun 14, 2021
- Jun 11, 2021
-
-
Zuul authored
-
Matthias Runge authored
the project is deprecated and in the process of being removed from OpenStack upstream. Change-Id: I9d5ebed293a5fb25f4cd7daa473df152440e8b50
-
Zuul authored
-
- Jun 10, 2021
-
-
Radosław Piliszek authored
With the new default since Wallaby, starting Docker makes it enable forwarding and not filter it at all. This may pose a security risk and should be mitigated. Closes-Bug: #1931615 Change-Id: I5129136c066489fdfaa4d93741c22e5010b7e89d
-
Radosław Piliszek authored
Now that bifrost on Ubuntu focal is fully supported both upstream (bifrost, kolla) and downstream (kayobe), we should test it in kolla ansible CI. Change-Id: Id3c3b7aadb9cf19813ccf3a9d39858f68526d25a
-
- Jun 08, 2021
-
-
Zuul authored
-
Zuul authored
-
Mark Goddard authored
The host list order seen during Ansible handlers may differ to the usual play host list order, due to race conditions in notifying handlers. This means that restart_services.yml for RabbitMQ may be included in a different order than the rabbitmq group, resulting in a node other than the 'first' being restarted first. This can cause some nodes to fail to join the cluster. The include_tasks loop was introduced in [1]. This change fixes the issue by splitting the handler into two tasks, and restarting the first node before all others. [1] https://review.opendev.org/c/openstack/kolla-ansible/+/763137 Change-Id: I1823301d5889589bfd48326ed7de03c6061ea5ba Closes-Bug: #1930293
-
- Jun 07, 2021
-
-
Maksim Malchuk authored
Since I0474324b60a5f792ef5210ab336639edf7a8cd9e swift role uses the new service-cert-copy role introduced in the I6351147ddaff8b2ae629179a9bc3bae2ebac9519 but the swift role itself doesn't contain the handler used in the service-cert-copy. Right now, restarting the swift container isn't necessary, but the handler should exist. Also we should fix the name of the service used. Closes-Bug: #1931097 Change-Id: I2d0615ce6914e1f875a2647c8a95b86dd17eeb22 Signed-off-by:
Maksim Malchuk <maksim.malchuk@gmail.com>
-