Mender server 2.3.0 ignores max device limit in prod.yml

General Discussions
1

Following this https://docs.mender.io/2.3/administration/production-installation#device-authentication-service-optional I changed DEVICEAUTH_MAX_DEVICES_LIMIT_DEFAULT.

    mender-device-auth:
        command: server --automigrate
        volumes:
            - ./production/keys-generated/keys/deviceauth/private.key:/etc/deviceauth/rsa/private.pem:ro
        logging:
            options:
                max-file: "10"
                max-size: "50m"
        environment:
            DEVICEAUTH_MAX_DEVICES_LIMIT_DEFAULT: 500000

With mender server 2.2.0 everything was ok, but after the upgrade to 2.3.0, this value seems ignored by mender. Because in the header of the front-end I see num/500 or num/1000000 as device limit and not num/500000.

Is this only a front-end issue, or is mender really ignoring DEVICEAUTH_MAX_DEVICES_LIMIT_DEFAULT value?

At the moment I removed DEVICEAUTH_MAX_DEVICES_LIMIT_DEFAULT to extend the limit to 1000000 by default and it’s ok for me, but I decided to report this to investigate a little bit.

PS: when I change this value in prod.yml should I run ./run down or a restart is enough?

2

Hi @Ks89 that is a known bug in 2.3 that will be fixed in the upcoming 2.4 release. https://tracker.mender.io/browse/MEN-3352

Basically, that option is removed for on-prem setups.

Drew

1 Like
3

ok thank you.