This repository was archived by the owner on Dec 16, 2025. It is now read-only.
Update fork#3
Open
fdobrovolny wants to merge 2046 commits into
Open
Conversation
9a45b3d to
920ebc7
Compare
Change-Id: I418a0e3f712697a3181c95e0e80433052bc31b9d Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I01df5f8dbf25f8af42fececd8c32db7c0dc4aefe Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Removing influxdb from ignore since it was added before it's drop. Change-Id: I857d64f201fdc510979fb23351837a75c6342abe Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I8a8c7e5106187ec0e68402114350a71b005ba42e Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: Ica6e1cf5e9a3994cdc510b61fa5ddec54bf10fe7 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I37fab87536e882541ef675449265bef9599d79b1 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Presently, if a single iterable container is 'changed', for example, due to a single instance being deleted, then all iterable containers for the service will be restarted. This patch changes the handler to loop over only changed containers Closes-Bug: #2144917 Change-Id: I011e7adb8990023f94d93c3b48de507110d45510 Signed-off-by: Doug Szumski <doug@stackhpc.com>
Change-Id: Iaf33e0fec67eaee026dc4da7d32be164a7f717b1 Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
Change-Id: I137a6b4de493c0284116eda2c148bc97b13df5ee Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I06ab1615e662b9fed3a87191d97d9a61d0b62a87 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I11628472f73269ce17058c4b659e1d80922283b3 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: Ieda9de2716b0f4da48d9cf218fa9f3d6b92c6a7c Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: Iab0c2a1e09971a83047db7d7f48ee85eac0d72c9 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I57b6ce1eefafbeceaeb1a7a02063e47c09770ad0 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I1d918203cec028e6be17925044ce2a0d9e040276 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: I9839a9b10d8caf31066d5d309ae163abed186e83 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: Ie257d123f0b249ede97169536f68a8bf9387f67b Signed-off-by: Bertrand Lanson <bertrand.lanson@infomaniak.com>
This introduces a proper skip list to avoid checking idempotence for containers that are not kolla-managed. It allows to extend the list by adding more matching patterns in the future. Change-Id: I0595964e6dec3958d939a7bf7c12c4a8d7be82bc Signed-off-by: Bertrand Lanson <bertrand.lanson@infomaniak.com>
The project[1] has received no commit for 4 years. Its latest commit still uses upper constraints from the old, abandoned Wallaby branch. [1] https://opendev.org/x/networking-infoblox Change-Id: I0e9291654c2973e29310d8f91f2b86237e840b06 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
When enabling cpuset_cpus or cpuset_mems on existing Docker containers, Docker may report the current value as an empty string when no cpuset constraint is configured. These dimensions are cpuset-list strings, not numeric resource values. Compare them as strings in the Docker worker instead of passing them through the numeric dimension comparison logic. Closes-Bug: 2143874 Change-Id: I1b8cd72846b28f556c8f9a0ba114a8af9221e85a Signed-off-by: Loan Harrouin <loan.harrouin@gmail.com>
Change-Id: Ib82e708137679ae85f645c448cc8aa3cf583cf6d Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
The nova_spice_require_secure configuration option requires clients to connect to SPICE consoles using channels secured by TLS. The default is `no` to match the previous behaviour of allowing insecure channels. Note that nova_spice_require_secure implies that qemu is configured to support TLS, and that TLS certificates have been configured in the nova_libvirt container. Partial-Bug: #2131793 (spice-direct consoles) Change-Id: I4306725fb8433860baec8e01c51e9eae2beb3cc9 Signed-off-by: Michael Still <mikal@stillhq.com>
There is a possibility that the ansible-runner in kolla_toolbox is executed with the wrong environment variables if run in a specific way. The cause is not super clear, but the solution is to simply force it to use the correct HOME value. Closes-Bug: #2153544 Change-Id: Ibad84e358f21564c570161f7e4f21b117398df3b Signed-off-by: Bertrand Lanson <bertrand.lanson@infomaniak.com>
Template is no longer used as kolla-toolbox is deployed in kolla_toolbox role now. This removes obsolete and unused file. Change-Id: I3c0ea709cd5478257649b7db77c9c97be4874cb2 Signed-off-by: Michal Arbet <michal.arbet@ultimum.io>
Change-Id: Ie8554e0114f1aed584396c27476d2159425621de Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Support architecture-specific IPA images and iPXE bootloaders. Depends-On: https://review.opendev.org/c/openstack/tenks/+/989768 Change-Id: I96b977d358929c28f37c61333be0ff385b94edb4 Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
Change-Id: If31a5ff7c715f39fd7d74131745eed5d00bf0975 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
The check_alive_proxysql.sh script piped raw ASCII text
("show info\n") directly into the admin socket via socat, bypassing
the MySQL handshake.
ProxySQL's MySQL_Data_Stream interprets the first 3 bytes of "show"
as a little-endian packet length (7301235), which has always been
semantically wrong - the check only appeared to work because socat
received ProxySQL's binary handshake greeting back and exited 0.
ProxySQL 3.0.9 introduced a pre-authentication bounds check
(GHSA-58ww-865x-grpr) that explicitly rejects first packets whose
declared length exceeds the 32 KB input queue capacity and closes
the connection.
This causes socat to exit non-zero, making keepalived mark ProxySQL
as unhealthy on every check interval.
Replace the raw socat probe with a mariadb client connection that
speaks proper MySQL protocol against the admin socket.
Closes-Bug: #2155865
Depends-On: https://review.opendev.org/c/openstack/kolla/+/992239
Change-Id: Ic090916509cbb1bd98c96e8beb32ec9e90bfc6aa
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Add the missing register statement required by the until condition when waiting for the toolbox container to become ready. Fixing https://review.opendev.org/c/openstack/kolla-ansible/+/985324 Signed-off-by: Michal Arbet <michal.arbet@ultimum.io> Change-Id: I5a3dddc7743ea6f0e261708baec8e396ca93abc8
These were overlooked in the previous attempt. Remove neutron_ipam_driver since the only option would be left supported is the default one [1]. [1]: https://docs.openstack.org/neutron/latest/configuration/neutron.html#DEFAULT.ipam_driver Change-Id: I780851ba15871627bae6ebf2ea003bd945605964 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com> Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
OpenDev does not have enough aarch64 node capacity at this point to run these jobs on every change. Move them from the check-arm64 pipeline to the experimental pipeline, so they can still be run on demand by commenting "check experimental" on a change. Change-Id: I2522bb1bba7f704fe73bbff75f94bd4477acc615 Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.