Fresh installation of Mender Server 3.6.2 fails

General Discussions
1

I’m trying to perform a fresh installation (using Amazon EKS) of Mender 3.6.2 according to the documentation, however, installation fails:

client.go:486: [debug] Starting delete for "mender-redis" ServiceAccount
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-configuration" ConfigMap
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-headless" Service
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-health" ConfigMap
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-master" Service
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-master" StatefulSet
client.go:490: [debug] Ignoring delete failure for "mender-redis-master" apps/v1, Kind=StatefulSet: statefulsets.apps "mender-redis-master" not found
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-replicas" Service
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-replicas" StatefulSet
client.go:490: [debug] Ignoring delete failure for "mender-redis-replicas" apps/v1, Kind=StatefulSet: statefulsets.apps "mender-redis-replicas" not found
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-redis-scripts" ConfigMap
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mongodb-common-prerelease" Secret
client.go:142: [debug] creating 1 resource(s)
client.go:486: [debug] Starting delete for "mender-db-data-migration" Job
client.go:142: [debug] creating 1 resource(s)
client.go:712: [debug] Watching for changes to Job mender-db-data-migration with timeout of 5m0s
client.go:740: [debug] Add/Modify event for mender-db-data-migration: ADDED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 1, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 1, jobs failed: 1, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 1, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 2, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 1, jobs failed: 2, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 2, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 3, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 1, jobs failed: 3, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 3, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 4, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 1, jobs failed: 4, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 4, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for mender-db-data-migration: MODIFIED
client.go:779: [debug] mender-db-data-migration: Jobs active: 0, jobs failed: 5, jobs succeeded: 0
Error: INSTALLATION FAILED: failed pre-install: 1 error occurred:
	* timed out waiting for the condition
2

Hello @PaterSantyago ,
it seems a issue with Mongo. Could you please share the migration logs and the values file that you used (without any secret in it)?

Thanks!

3

I’m using the following file:

global:
  enterprise: false
  image:
    tag: mender-3.6.2
  mongodb:
    URL: "mongodb+srv://<DB_USER>:<DB_PASSWORD>@<CLOUD_MONGO_HOST>/<DB_NAME>?retryWrites=true&w=majority"
  nats:
    URL: ""
  s3:
    AWS_URI: "<AWS_URI>"
    AWS_BUCKET: "<AWS_BUCKET>"
    AWS_ACCESS_KEY_ID: "<AWS_ACCESS_KEY_ID>"
    AWS_SECRET_ACCESS_KEY: "<AWS_SECRET_ACCESS_KEY>"
  url: "<URL>"

nats:
  enabled: true

api_gateway:
  env:
    SSL: false

device_auth:
  certs:
    key: |-
      -----BEGIN PRIVATE KEY-----
      -----END PRIVATE KEY-----

useradm:
  certs:
    key: |-
      -----BEGIN PRIVATE KEY-----
      -----END PRIVATE KEY-----

can you please advise, on how I can extract migration logs?

P.s. I checked MongoDB connectivity from the cluster using mongosh, there were no problems with data insertion/collection creation

4

With kubectl describe <migration pod> you can get the failing containers, then issue:

kubectl logs <migration pod> -c container_name
5

It seems that I found the issue: underlying EC2 machine was using Arm architecture instead of x86 :frowning:

exec /usr/bin/deployments: exec format error
6

Yes, Mender 3.6 only supports x86_64 architecture.