This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch 3.40.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/3.40.x by this push:
new 1f0799a353 Fixes #9251. Use SQL Server 2022 image on FIPS
1f0799a353 is described below
commit 1f0799a353a75106570bbea356c22abf660c7338
Author: James Netherton <[email protected]>
AuthorDate: Wed Sep 30 11:32:21 2026 +0100
Fixes #9251. Use SQL Server 2022 image on FIPS
The SQL Server 2025 container image crashes on FIPS enabled hosts during
TLS initialization (errors 49946/49947, exit code 151), see
https://github.com/microsoft/mssql-docker/issues/958. The container never
starts, so CamelMssqlJdbcTest and other MS SQL based tests fail.
- root pom: `fips` profile overrides sql-server.container.image with
mcr.microsoft.com/mssql/server:2022-latest (the last image that starts
on FIPS)
- jdbc/mssql: honour sql-server.container.image via the dev service
image-name, like the mysql/oracle/postgresql modules already do (it was
falling back to the Quarkus default before)
- debezium-grouped README: fix the stale MS SQL EULA image tag
(2022-latest -> 2025-latest) to match the current default image
Regular (non-FIPS) runs keep using 2025-latest.
(cherry picked from commit 652d777baf1f7549afd2acc222ad2ce01c0c46bb)
Co-authored-by: Jiří Ondrušek <[email protected]>
Co-authored-by: Claude Opus 4.8 <[email protected]>
---
.../jdbc/mssql/src/main/resources/application.properties | 1 +
integration-tests/debezium-grouped/README.adoc | 4 ++--
pom.xml | 14 ++++++++++++++
3 files changed, 17 insertions(+), 2 deletions(-)
diff --git
a/integration-test-groups/jdbc/mssql/src/main/resources/application.properties
b/integration-test-groups/jdbc/mssql/src/main/resources/application.properties
index 57c1fb13e7..e6bb2bba26 100644
---
a/integration-test-groups/jdbc/mssql/src/main/resources/application.properties
+++
b/integration-test-groups/jdbc/mssql/src/main/resources/application.properties
@@ -21,6 +21,7 @@
quarkus.datasource.mssql.db-kind=mssql
quarkus.datasource.mssql.jdbc.max-size=8
+quarkus.datasource.mssql.devservices.image-name=${sql-server.container.image}
# Accept the MS SQL Server EULA via the container environment instead of a
container-license-acceptance.txt file,
# because the file is not reliably visible on the classpath when the tests are
executed from the published
# test-jar, e.g. in the Quarkus Platform. See
https://github.com/apache/camel-quarkus/issues/9048
diff --git a/integration-tests/debezium-grouped/README.adoc
b/integration-tests/debezium-grouped/README.adoc
index 207497686f..f2e1cc6944 100644
--- a/integration-tests/debezium-grouped/README.adoc
+++ b/integration-tests/debezium-grouped/README.adoc
@@ -12,14 +12,14 @@ consent with its EULA by placing a specific file on a
specific location. The Apa
prevents us of doing it unconditionally for anybody who clones this repository.
Therefore, to execute the MS SQL Server integration tests you need to accept
the
-https://go.microsoft.com/fwlink/?linkid=857698[EULA] by creating file
`integration-tests/debezium-grouped/src/test/resources/container-license-acceptance.txt`
with content `mcr.microsoft.com/mssql/server:2022-latest`
+https://go.microsoft.com/fwlink/?linkid=857698[EULA] by creating file
`integration-tests/debezium-grouped/src/test/resources/container-license-acceptance.txt`
with content `mcr.microsoft.com/mssql/server:2025-latest`
in the current Maven module.
On a Unix-like system, you can run.
[source,shell]
----
-echo "mcr.microsoft.com/mssql/server:2022-latest" >
integration-tests/debezium-grouped/src/test/resources/container-license-acceptance.txt
+echo "mcr.microsoft.com/mssql/server:2025-latest" >
integration-tests/debezium-grouped/src/test/resources/container-license-acceptance.txt
----
For more details see
https://www.testcontainers.org/modules/databases/mssqlserver/
diff --git a/pom.xml b/pom.xml
index 0bdb3b77ac..c0f34fbcf7 100644
--- a/pom.xml
+++ b/pom.xml
@@ -284,6 +284,8 @@
<solr.container.image>mirror.gcr.io/solr:9.10.1-slim</solr.container.image>
<splunk.container.image>mirror.gcr.io/splunk/splunk:9.4.7</splunk.container.image>
<sql-server.container.image>mcr.microsoft.com/mssql/server:2025-latest</sql-server.container.image>
+ <!-- SQL Server 2025 does not start on FIPS hosts, see
https://github.com/microsoft/mssql-docker/issues/958. The fips profile switches
to this image. -->
+
<sql-server.container.image.fips>mcr.microsoft.com/mssql/server:2022-latest</sql-server.container.image.fips>
<weaviate.container.image>mirror.gcr.io/semitechnologies/weaviate:1.37.4</weaviate.container.image>
<!-- Plugin configuration through properties -->
@@ -1735,6 +1737,18 @@
</plugins>
</build>
</profile>
+ <profile>
+ <!-- FIPS host support: switch test container images that do not
start on FIPS-enabled kernels. Activate with -Dfips -->
+ <id>fips</id>
+ <activation>
+ <property>
+ <name>fips</name>
+ </property>
+ </activation>
+ <properties>
+
<sql-server.container.image>${sql-server.container.image.fips}</sql-server.container.image>
+ </properties>
+ </profile>
</profiles>
</project>
