Correct service failure of asserting ACL_PROXY_USER when skip-name-resolve=1 and there is a Proxy user

$ dbdeployer deploy single /opt/percona_server/5.7.28 --force
Overwriting directory /home/juan.arruti/sandboxes/msb_5_7_28
Database installed in $HOME/sandboxes/msb_5_7_28
run 'dbdeployer usage single' for basic instructions'
. sandbox server started

$ ./use -uroot

mysql [localhost:5728] {root} ((none)) > INSTALL PLUGIN auth_pam SONAME 'auth_pam.so';
Query OK, 0 rows affected (0.00 sec)

mysql [localhost:5728] {root} ((none)) > CREATE USER IF NOT EXISTS ''@'' IDENTIFIED WITH auth_pam as 'mysqld,gcpusers=dba';
Query OK, 0 rows affected (0.00 sec)

mysql [localhost:5728] {root} ((none)) > CREATE USER IF NOT EXISTS dba@'localhost' IDENTIFIED BY 'xxxxxx';
Query OK, 0 rows affected (0.00 sec)

mysql [localhost:5728] {root} ((none)) > GRANT ALL PRIVILEGES ON *.* TO dba@'localhost' with grant option;
Query OK, 0 rows affected (0.00 sec)

mysql [localhost:5728] {root} ((none)) > GRANT PROXY ON dba@'localhost' TO ''@'';
Query OK, 0 rows affected (0.00 sec)

mysql [localhost:5728] {root} ((none)) > exit
Bye

$ echo "skip-name-resolve" >> my.sandbox.cnf

$ ./restart 
stop /home/juan.arruti/sandboxes/msb_5_7_28
. sandbox server started

# MySQL error log

20:04:03 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=152
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68337 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f2067f1e000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fff449f5fc0 thread_stack 0x40000
/opt/percona_server/5.7.28/bin/mysqld(my_print_stacktrace+0x2c)[0xee1c1c]
/opt/percona_server/5.7.28/bin/mysqld(handle_fatal_signal+0x461)[0xd21c81]
/lib64/libpthread.so.0(+0xf5d0)[0x7f20871f25d0]
/opt/percona_server/5.7.28/bin/mysqld(_ZN14ACL_PROXY_USER14check_validityEb+0x3a)[0xd6392a]
/opt/percona_server/5.7.28/bin/mysqld(_Z10acl_reloadP3THD+0x29b1)[0xd6bf01]
/opt/percona_server/5.7.28/bin/mysqld(_Z8acl_initb+0x1ff)[0xd6c93f]
/opt/percona_server/5.7.28/bin/mysqld(_Z11mysqld_mainiPPc+0x208e)[0xd1da6e]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f20852dd3d5]
/opt/percona_server/5.7.28/bin/mysqld[0x799db5]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED