aboutsummaryrefslogtreecommitdiff
path: root/tests/check-logs.sh
AgeCommit message (Collapse)AuthorFilesLines
2026-04-27Drop zun and kuryrMichal Nasiadka1-3/+0
Zun is broken in 2026.1, it has been released broken and there are no reviews on the patch to fix it [1]. [1]: https://review.opendev.org/c/openstack/zun/+/982362 Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/986150 Change-Id: I8ced621754d03c44b7672dd94fc3d7d2173ac734 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2026-04-24Drop support for running WSGI under ApacheMichal Nasiadka1-0/+4
The migration to uWSGI has been successfully completed. All API services now run exclusively under uWSGI. The *_wsgi_provider variables have been removed from all affected roles along with leftover Apache wsgi config templates and fluentd Apache log handling. Rework Apache fluentd input configuration so it doesn't glob out whole /var/log/kolla/*/* and just include required services when enabled. Change-Id: I1475e629d033163a50a5c681c8fe2557a7b10bae Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
2025-12-30Remove glance-tls-proxy remnantsMichal Nasiadka1-1/+2
It has been omitted in the original Glance uWSGI patch Change-Id: Idaacd719846f7328bfcd77c4a271f417f7064c94 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-11-06Replace Redis with ValkeyGrzegorz Koper1-0/+1
This change replaces Redis with Valkey, which is non-existent on Rocky Linux 10 / CentOS Stream 10 due to licensing issues. Co-Authored-By: Bartosz Bezak <bartosz@stackhpc.com> Co-Authored-By: Michal Nasiadka <mnasiadka@gmail.com> Change-Id: Ifcc6ec6e943c20867d969b0bdb0e4cbac53eea1e Signed-off-by: Grzegorz Koper <grzegorzk@stackhpc.com> Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com> Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-10-28Drop venusMichal Nasiadka1-3/+0
It has been marked as inactive and venus dashboard plugin is breaking Horizon Kolla builds. Change-Id: I78cf7a33bf1025f5c8e4b76ecfeef7d8a3126d61 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-10-13Drop support for DB Loadbalancing with HAProxy + clustercheckSeunghun Lee1-3/+0
MariaDB Clustercheck has not been updated for a long time and ProxySQL has been working well as the default. Dropped DB Loadbalancing with HAProxy and MariaDB clustercheck support and ProxySQL now gets enabled automatically when MariaDB is enabled. Replaced MariaDB container healthcheck method with healthcheck.sh from official MariaDB docker images. Performing service upgrade with this patch will remove remaining mariadb_clustercheck container. Depends-on: https://review.opendev.org/c/openstack/kolla/+/962657 Change-Id: Ib655eae79ba73f4582b29fef82c2d882a474329b Signed-off-by: Seunghun Lee <seunghun@stackhpc.com>
2025-09-23CI: check-logs.sh add wait for OpenSearch connectionMichal Nasiadka1-0/+16
Change-Id: Ib8a93336e41f7fa326d3a4be53f757fee3923643 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-09-03CI: Add exception for venus to check-logs.shMichal Nasiadka1-0/+3
We're not handling it in fluentd Change-Id: Iff11ae1e75907790780e41059d94c873e93ec32f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-08-23CI: Check for OOM in check-logs.shMichal Nasiadka1-0/+10
Change-Id: I1c2e48a2a7de150697d11b8e0de2bd5a5a88c40f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-08-18neutron: Switch to uWSGIMichal Nasiadka1-1/+2
Also split services into: - api - rpc-worker (only for ML2/OVS) - periodic-worker - ovn-maintenance-worker (only for ML2/OVN) Remove neutron-tls-proxy since it's not needed anymore Change-Id: Iac99be59139eeb232dd3b00ec90fae0a4ea7547d Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-07-28Merge "Remove egrep usage from scripts"Zuul1-3/+3
2025-07-21Remove egrep usage from scriptsMichal Nasiadka1-3/+3
egrep: warning: egrep is obsolescent; using grep -E Change-Id: I4df0d520546da141cafc15e9464149059fdc06a6 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-07-14CI: Exclude hacluster logs in fluentd checksMichal Nasiadka1-0/+3
We're not parsing those and masakari jobs fail on this Change-Id: I201008d73c5a9a6404a8e386a281bd3bf378f65a Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-07-11Merge "CI: Add tenks logs to check-logs.sh exception list"Zuul1-0/+3
2025-07-11Merge "gnocchi: Remove from openstack fluentd services"Zuul1-0/+3
2025-07-11CI: Add tenks logs to check-logs.sh exception listMichal Nasiadka1-0/+3
Change-Id: Ib99d38fa881c1e49c5dc5690f370ae723b63cdb3 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-07-09gnocchi: Remove from openstack fluentd servicesMichal Nasiadka1-0/+3
gnocchi is not using oslo_log anymore, which means it doesn't match our regex [1]. Remove it for now. [1]: https://github.com/gnocchixyz/gnocchi/commit/ad2484d61cab955cdd6f8ae5740ea4049b710ba0 Change-Id: I2c47ac30dd8adb1baf78af7a66b0cc0c4b037173 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-07-04CI: add zun to check-log exception listBartosz Bezak1-0/+3
Change-Id: I892357e7c4d03c5ae3a9ec90eabd0e8eb95ab8be Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
2025-06-25CI: Fix check-logs.sh routine for finding missing fluentd logsMichal Nasiadka1-3/+6
Change-Id: Ie5afd40ffb5517cd0d77c46b55a304ad0c7d4007
2025-06-23CI: Test for log files missing in fluentd configMichal Nasiadka1-17/+95
Change-Id: I7f9bea3fd3e733345778c59798e5a92fd66d7947
2025-03-27Adding new placement error to expected critical msgsGrzegorz Koper1-1/+2
It's expected during upgrade jobs. Change-Id: I51aca294d256c33ae52eaab4dcc67860cfc876af
2025-01-13CI: Add unreadable files to check-logs.shMichal Nasiadka1-3/+3
fluentd emits a warn message when it can't read a file "unreadable. It is excluded and would be examined next time." Depends-On: https://review.opendev.org/c/openstack/kolla/+/939055 Depends-On: https://review.opendev.org/c/openstack/kolla/+/939088 Change-Id: I4313b6918c381ec5e79e78df2f9a0cbaf25df53e
2025-01-07CI: Remove OpenSearch connectivity check in fluentd logsMichal Nasiadka1-1/+1
It broke OpenSearch CI jobs because we restart OpenSearch in there. Also add check-logs.sh and get_logs.sh to files that trigger all jobs run so we don't break anything again. Change-Id: I6fe4b106853fd253ea28111409370e01cb678fe9
2024-12-30CI: Fix fluentd log checkMichal Nasiadka1-1/+1
Change-Id: I31969eaac40c4de985be8d9d05befa930b788800
2024-11-29Merge "CI: add a message for fluentd string match function"Zuul1-0/+1
2024-10-24CI: Add ProxySQL exception to check-logs.shMichal Nasiadka1-1/+2
After switching to ProxySQL as default we see following logs: CRITICAL neutron [None req-c214fdae-5da7-402d-92b0-0572c278a5b5 - - - - - -] Unhandled error: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (9001, 'Max connect timeout reached while reaching hostgroup 0 after 10150ms') Mainly in upgrade jobs, which otherwise pass successfuly - just fail on this check. Change-Id: I4336ec62a0a2dfbe815842f1bacb02135bcf4c0e
2024-01-04CI: add a message for fluentd string match functionMichal Nasiadka1-0/+1
Change-Id: Ie3ddf7819934d2b100867f29ac9a9395c854d9f7
2023-11-29CI: Fail on fluentd log parsing errorsMichal Nasiadka1-1/+17
Change-Id: Ie3963f5ed20f7fb61ef2e03f0cf12a4ea1c87c9c
2023-11-29CI: Add oslo_db.exception.DBConnectionError to check-logs.shMichal Nasiadka1-0/+1
Change-Id: Ia1de6d9452e2c900169e9b4ccb7dfc1280283909
2023-08-17systemd: handle running container without systemd unitMichal Nasiadka1-0/+8
MariaDB bootstrap has a phase where the first MariaDB container is running with Galera bootstrap - after a check that WSREP is synced is successful - we restart the container. The bootstrap container is named mariadb and running with docker_restart_policy: "no" - the restarted container should be running in systemd. Before this patch the code created a systemd unit but it was initially stopped - so stopping was always a success - and the container would be killed with SIGKILL on removal (which obviously breaks MariaDB). This patch also improves docker/systemd stops by waiting for real unit/container stop and adds failing CI for containers that are killed with signal 9. Closes-Bug: #2029613 Change-Id: I0a03e509ce228a50e081fcab44d2b4831251190c
2022-05-21[CI] Restore token critical error filterRadosław Piliszek1-5/+6
It was removed as part of improvements in [1]. But it seems it's a different type/class of errors and should still be filtered out here. This time for all the services to avoid extra copies. [1] Ie6a95c3ca84df82ca8463cf76054e125cb1ffff1 Change-Id: If7c5b938dc7417831a90f360d6e3655d1ad4084e
2022-05-10[CI] Raise [keystone_authtoken]http_request_max_retriesRadosław Piliszek1-5/+0
This is in the hope to avoid random "Unable to validate token" in AIO upgrade jobs which restart the Keystone container while other services are trying to use it (most notably Placement but also Nova and Neutron). Change-Id: Ie6a95c3ca84df82ca8463cf76054e125cb1ffff1
2022-02-09[CI] Filter fluentd errors moreRadosław Piliszek1-1/+1
Make it less likely to fail on false positives. Change-Id: I493430e255c76bf2a30818b63913ecabb40c5afc
2022-01-27Merge "[CI] Check fluentd errors"Zuul1-5/+23
2021-12-29[CI] Check fluentd errorsRadosław Piliszek1-5/+23
We consider them critical and prefer to fail the jobs. Change-Id: I3c2475522f8f37e3b608d3c321aee27277fc9dee
2021-11-26CI: check-logs - add another exceptionMichal Nasiadka1-0/+1
It was seen in [1] and some other occassions, possibly neutron was trying to fetch token while keystone was being upgraded. [1]: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_ec2/665117/12/check/kolla-ansible-ubuntu-source-upgrade/ec2fc04/primary/logs/kolla/all-CRITICAL.txt Change-Id: If8c569e1f7815520c84627671e3cbf275bed8ff9
2020-03-16CI: Ignore neutron-server CRITICAL about WSREPRadosław Piliszek1-0/+5
We are getting this randomly on neutron-server shutdown for upgrade. As it does not affect real operations (and if it did, we would definitely see it now), let's ignore it. Change-Id: Ibe561517d44a1108e8223442a71fab36b69c2258 Related-bug: #1863579
2019-12-08CI: Don't fail on expected critical log messagesMark Goddard1-1/+22
There is a number of critical log messages that we see in CI from time to time. While these should be fixed, let's not fail jobs unnecessarily. This change introduces one expected critical message in placement-api.log: Failed to fetch token data from identity server Co-authored-by: Radosław Piliszek <radoslaw.piliszek@gmail.com> Related-bug: #1847727 Change-Id: I92ad0be70ed05925612f0c709907ab62280326b8
2019-10-23CI: run check-logs in post tooRadosław Piliszek1-0/+2
Also makes check-logs clear the aggregate files to prevent duplicates due to upgrade and post. Change-Id: I72377b6ac48e29dc5e24d1e3bd343e87b74a7a71
2019-09-20CI: Fix check-logs.shMark Goddard1-3/+11
This script has a few issues: * It catches false positives, due to log levels in config options. * It doesn't fail on CRITICAL logs, due to variable reset issue. This change fixes these. Change-Id: I50c859eb2991e498eeb64bca45daf1e6f237761f
2019-08-16Check for CRITICAL, WARNING and ERROR log messages in CIMark Goddard1-0/+35
At the end of a CI run, check all log files. Change-Id: I99afc1c5207757e35beabf7daebd86c56151c96d
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 15:47:28 +0000