[
https://issues.apache.org/jira/browse/CAMEL-23677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107257#comment-18107257
]
Aurélien Pupier commented on CAMEL-23677:
-----------------------------------------
failing on CI due to missing access to the container image:
{noformat}
org.testcontainers.containers.ContainerFetchException: Can't get Docker image:
RemoteDockerImage(imageName=icr.io/s390x-oss/activemq-artemis-broker-s390x:2.0.2,
imagePullPolicy=DefaultPullPolicy(),
imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@328e0f54)
at
org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1308)
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:346)
at
org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
at
org.apache.camel.component.sjms.SjmsConnectionRecoveryTest.startBroker(SjmsConnectionRecoveryTest.java:68)
Caused by: com.github.dockerjava.api.exception.UnauthorizedException: Status
401: {"message":"Head
\"https://icr.io/v2/s390x-oss/activemq-artemis-broker-s390x/manifests/2.0.2\":
unauthorized:
{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"Authorization required.
See
https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-auth-req\",\"detail\":\"Authorization
required. See
https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-auth-req\"}]}\n"}
at
org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:239)
at
org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269)
at java.base/java.lang.Thread.run(Thread.java:1583) {noformat}
> Investigate SjmsConnectionRecoveryTest, skipped on s390x
> --------------------------------------------------------
>
> Key: CAMEL-23677
> URL: https://issues.apache.org/jira/browse/CAMEL-23677
> Project: Camel
> Issue Type: Task
> Components: camel-sjms
> Reporter: Federico Mariani
> Priority: Minor
>
> The test _SjmsConnectionRecoveryTest_ was skipped on *s390x* due to non
> working infrastructure. Such test uses a different approach compared to the
> others, in particular, to test a reconnect scenario it need a *tcp:*
> connection, unlike all the other tests that uses *vm:*.
> Most probably the issue is not in Camel itself, but in the artemis
> configuration. It would be nice to investigate it and try to fix it on s390x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
