MySQL Bugs: #103512: Failed case auth_sec.atomic_rename

Bug #103512	Failed case auth_sec.atomic_rename_user
Submitted:	28 Apr 2021 4:43	Modified:	30 May 2021 11:54
Reporter:	zhai weixiang (OCA)	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	8.0.24	OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
compile and run test case auth_sec.atomic_rename_user:

CURRENT_TEST: auth_sec.atomic_rename_user
--- /root/mysql-server/mysql-test/suite/auth_sec/r/atomic_rename_user.result    2021-03-04 06:14:16.721403000 +0300
+++ /root/mysql-server/mysql-test/var/log/atomic_rename_user.reject     2021-04-28 07:39:52.985403000 +0300
@@ -168,11 +168,11 @@
 GRANT CREATE USER ON *.* TO ''@'localhost';
 SELECT user(), current_user();
 user() current_user()
-CONNECTED_USER @localhost
+CONNECTED_USER root@localhost
 RENAME USER ''@'localhost' TO a;
 SELECT user(), current_user();
 user() current_user()
-CONNECTED_USER a@%
+CONNECTED_USER root@localhost
 DROP USER a;
 # End : Tests for RENAME USER
 # -----------------------------------------------------------------------

How to repeat:
above

Suggested fix:
correct the case

Hello Zhai,

Thank you for the report and feedback.
I quickly tried with release/debug builds but not seeing any issues. Is there anything I'm missing here? Please let me know.

./mtr auth_sec.atomic_rename_user
Logging: ./mtr  auth_sec.atomic_rename_user
MySQL Version 8.0.24
Checking supported features
Using 'all' suites
Collecting tests
Checking leftover processes
Removing old var directory
Creating var directory '/home/umshastr/work/binaries/ga/mysql-8.0.24/mysql-test/var'
Installing system database
Using parallel: 1

==============================================================================
                  TEST NAME                       RESULT  TIME (ms) COMMENT
------------------------------------------------------------------------------
[ 50%] auth_sec.atomic_rename_user               [ pass ]   1188
[100%] shutdown_report                           [ pass ]
------------------------------------------------------------------------------
The servers were restarted 0 times
The servers were reinitialized 0 times
Spent 1.188 of 60 seconds executing testcases

Completed: All 2 tests were successful.

 ./mtr  auth_sec.atomic_rename_user --check-testcases
Logging: ./mtr  auth_sec.atomic_rename_user --check-testcases
MySQL Version 8.0.24
Checking supported features
 - Binaries are debug compiled
Using 'all' suites
Collecting tests
Checking leftover processes
Removing old var directory
 - WARNING: Using the 'mysql-test/var' symlink
Creating var directory '/home/umshastr/work/src/8024_103477/mysql-test/var'
Installing system database
Using parallel: 1

==============================================================================
                  TEST NAME                       RESULT  TIME (ms) COMMENT
------------------------------------------------------------------------------
[ 50%] auth_sec.atomic_rename_user               [ pass ]   1424
[100%] shutdown_report                           [ pass ]
------------------------------------------------------------------------------
The servers were restarted 0 times
The servers were reinitialized 0 times
Spent 1.424 of 37 seconds executing testcases

Completed: All 2 tests were successful.

regards,
Umesh

Thank you for the requested details.
Let me try on the identical box with the build script.

regards,
Umesh

Thank you zhai for the build script.
I tried your build script on two different hosts to reproduce but still not seeing any issues(only diff being that I'm om using OL7 instead of CentOS). 
I'll join he build log and test results shortly. Are you seeing this failure on just your machine or everywhere? Thank you!

regards,
Umesh

MySQL Server 8.0.24 build and test results

Attachment: 103512_8.0.24.results.txt (text/plain), 379.61 KiB.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".