9.1: install fails due to mail.use-tls setting

[acdha]

I spun up a fresh install of a custom onbuild deployment of 9.1 and it's failing with this exception:

AssertionError: u'mail.use-tls' cannot be changed at runtime because it is configured on disk

Changing the value of SENTRY_EMAIL_USE_TLS does not appear to have an effect. This is almost the verbatim onbuild module except that it adds a wrapper which populates the environment from AWS SSM values (working around FarGate design limitations).

[ei-grad]

The similar issue, but with 'mail.from' field. The docker sentry installation procedure is broken.

[mattrobenolt]

Thanks for bringing his up. I’m going to look into this.

[ei-grad]

Checked the same process for 9.0 - all working as expected.

[acdha]

I was able to work around it by using the regular image now that AWS has shipped secrets management in Fargate but it seems like this should work either way.

[mafredri]

I had the mail.from issue as well. I can only reproduce the issue when creating a superuser account, and upon login Sentry asks to define base url / mail (from) and some other settings. It's not possible to get past this due to the mail.from being configured on disk.

Removing the following lines solved the issue:

docker-sentry/9.1/sentry.conf.py

Lines 258 to 266 in 4b3fad4

	email = env('SENTRY_EMAIL_HOST') or (env('SMTP_PORT_25_TCP_ADDR') and 'smtp')
	if email:
	SENTRY_OPTIONS['mail.backend'] = 'smtp'
	SENTRY_OPTIONS['mail.host'] = email
	SENTRY_OPTIONS['mail.password'] = env('SENTRY_EMAIL_PASSWORD') or ''
	SENTRY_OPTIONS['mail.username'] = env('SENTRY_EMAIL_USER') or ''
	SENTRY_OPTIONS['mail.port'] = int(env('SENTRY_EMAIL_PORT') or 25)
	SENTRY_OPTIONS['mail.use-tls'] = env('SENTRY_EMAIL_USE_TLS', False)
	else:

docker-sentry/9.1/sentry.conf.py

Line 270 in 4b3fad4

SENTRY_OPTIONS['mail.from'] = env('SENTRY_SERVER_EMAIL') or 'root@localhost'

Not sure if all of it was necessary. It's possible only line 270 needed to be removed.

[dcramer]

I wonder why we're binding default values in docker vs forcing you to configure it via the UI when it's not setup from the environment.. seems backwards from any other way we'd suggest to install it.

[dcramer]

Will be fixed in 9.1.1 which we're hoping to get out later today.

[rbtellis]

Can this fix be uploaded to Dockerhub please? I am trying to use the onpremise docker scripts, but this bug is preventing me from installing. I attempted to build the new docker image, but got a gpg failure.
gpg: Can't check signature: No public key

Thanks!

[dcramer]

We do not control the speed at which Docker publishes new version:

docker-library/official-images#5772

[rbtellis]

Ok, thanks for the info!