Which version and edition of Flyway are you using?

5.2.4 Pro

If this is not the latest version, can you reproduce the issue with the latest one as well?

(Many bugs are fixed in newer releases and upgrading will often resolve the issue)

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Command-line

Which database are you using (type & version)?

MSSQL 2017 Linux Docker Container:latest

Which operating system are you using?

Linux Alpine:5.2.4-alpine

What did you do?

(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
flyway migrate with a migration containing EXECUTE AS USER = '[SOME DOMAIN USER]' with the following errorOverrides:

 flyway.errorOverrides=S0001:15151:I,S0001:15401:I,S0011:15404:I
# S0001 - 15151: Cannot alter the login '', because it does not exist or you do not have permission.
# S0001 - 15401: Windows NT user or group '' not found. Check the name again.
# S00011 - 15404: Could not obtain information about Windows NT group/user '', error code 0x4bc.

What did you expect to see?

An informational message in regard to S0011:15404.

What did you see instead?

ERROR: Invalid error override (should look like STATE:12345:W ): S00011:15404:I

If I remove that error override I get that following

ERROR: Migration of schema [dbo] with repeatable migration [MIGRATION_NAME] failed! Changes successfully rolled back.
ERROR: 
Migration [MIGRATION_FILE] failed
-----------------------------------------------------------------------
SQL State  : S00011
Error Code : 15404
Message    : Could not obtain information about Windows NT group/user '[USER_NAME]', error code 0x4bc.
Location   : /flyway/sql/test/stored-procedures/R__z_dbo.[MIGRATION_FILE] (/flyway/sql/test/stored-procedures/[MIGRATION_FILE])
Line       : 1
Statement  : EXECUTE AS USER = '[USER_NAME]'

Domain users are not yet supported on Linux SQL so we are on a trial for PRO only to take advantage of this feature locally to see if it will allow us to ignore these errors locally. For whatever reason, Flyway doesn't like this one.