This happens in camel-quarkus-2.2.1-product after upgrading to Quarkus 2.2.5.Final-redhat-00002:

[ERROR] Failed to execute goal on project camel-quarkus-integration-test-nsq: Could not resolve dependencies for project org.apache.camel.quarkus:camel-quarkus-integration-test-nsq:jar:2.2.1-SNAPSHOT: Could not find artifact io.netty:netty-transport-native-epoll:jar:linux-aarch_64:4.1.69.Final-redhat-00001 in nexus.corp.redhat.com (https://nexus.corp.redhat.com/repository/ads/) -> [Help 1]

The same problem exists with NSQ, HDFS and Spark. None of them is supported.

The issue seems to be primarily caused by the fact that the native epoll libs are not productized. However, those are not needed for NSQ to work properly. The right way to solve this issue is to ban netty-all that brings these unneeded netty artifacts, as we did in the community main branch: https://github.com/apache/camel-quarkus/pull/3465

For 2.2.1 we will just workaround the issue by excluding netty-all in affected tests and document it in a release note for end users, something like

The reason for this behavior is that the native epoll libraries are not included in the camel-quarkus-2.2.1-product build. However, as these libraries are not required for NSQ, HDFS or Spark components, the recommended workaround is to exclude netty-all from your applications and include quarkus-netty as a dependency.

For example, you can update your application’s pom.xml for the hdfs component as follows:

<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-hdfs</artifactId>
    <exclusions>
        <exclusion>
            <groupId>io.netty</groupId>
            <artifactId>netty-all</artifactId>
        </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-netty</artifactId>
</dependency>