Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RabbitMQ integration tests fail when running in arm64 env #5926

Closed
dadjeibaah opened this issue Mar 18, 2021 · 1 comment · Fixed by #5927
Closed

RabbitMQ integration tests fail when running in arm64 env #5926

dadjeibaah opened this issue Mar 18, 2021 · 1 comment · Fixed by #5927

Comments

@dadjeibaah
Copy link
Contributor

It looks like we can't run the RabbitMQ integration tests in an arm64 environment.
We might need to update the rabbit-client image to one that has an arm64 build.

Run bin/tests --name deep --images skip --skip-cluster-create "$CMD"
Checking the linkerd binary...[ok]
Checking if there is a Kubernetes cluster available...[ok]
Checking if Linkerd resources exist on cluster...[ok]
Test script: [install_test.go] Params: []
ok  	command-line-arguments	177.041s
Test script: [edges] Params: []
ok  	github.com/linkerd/linkerd2/test/integration/edges	34.882s
Test script: [egress] Params: []
ok  	github.com/linkerd/linkerd2/test/integration/egress	14.349s
Test script: [endpoints] Params: []
ok  	github.com/linkerd/linkerd2/test/integration/endpoints	3.254s
Test script: [externalissuer] Params: []
ok  	github.com/linkerd/linkerd2/test/integration/externalissuer	0.080s
Test script: [externalresources] Params: []
Error: TestRabbitMQDeploy - CheckPods timed-out %s
Error: TestRabbitMQDeploy - CheckDeployment  timed-out
Error: TestRabbitMQDeploy - 'kubectl logs' command timed-out (50s)
--- FAIL: TestRabbitMQDeploy (494.04s)
    rabbitmq_test.go:61: Container [rabbitmq-client] in pod [rabbitmq-client-78d8cf5d68-bjhpm] in namespace [linkerd-rabbitmq-test] is not running
    rabbitmq_test.go:65: Error validating deployment [rabbitmq]: 
        Expected deployment [rabbitmq-client] in namespace [linkerd-rabbitmq-test] to have [1] replicas, but found [0]
    rabbitmq_test.go:82: received unexpected output
        Expected:
        [OK] Create message queue MQTestQueue
        [OK] Published message. Message count: 1
        [OK] Consumed message. Message count: 0
        
        Actual:
        standard_init_linux.go:211: exec user process caused "exec format error"
        
FAIL
FAIL	github.com/linkerd/linkerd2/test/integration/externalresources	494.130s
FAIL

It looks like the current rabbitmq client docker image does not have an arm64 build manifest

docker manifest inspect ghcr.io/barkardk/rabbitmq-client:1.0.0
{
        "schemaVersion": 2,
        "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
        "config": {
                "mediaType": "application/vnd.docker.container.image.v1+json",
                "size": 2423,
                "digest": "sha256:d86ff766104565b0e8841eca13d3d27e3d9d3d3bc0f2787fa1c18345005caa2c"
        },
        "layers": [
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 2811657,
                        "digest": "sha256:ba3557a56b150f9b813f9d02274d62914fd8fce120dd374d9ee17b87cf1d277d"
                },
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 1578487,
                        "digest": "sha256:6f03b9ee17a46cc071a2e3b524924d858f9172252a682c5628a4d8397c168f94"
                },
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 161,
                        "digest": "sha256:94b78c68c1fc4ba777a2550e4dfb5ce6698bb5ab559407e44cdf8d4ca79f8768"
                },
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 1578513,
                        "digest": "sha256:5beefafc3c8aeac8b74e35d86ac12beeaeb2fc3454f8a4c7f84f03cad96c8671"
                }
        ]
}

//cc @barkardk

@barkardk
Copy link
Contributor

@dadjeibaah Apologies, I missed that. Ill get right on it

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants