MySQL Bugs: #117989: After upgrading to version 8.4.5 MySQL will throw database connection error in all sites

Bug #117989	After upgrading to version 8.4.5 MySQL will throw database connection error in all sites
Submitted:	15 Apr 14:58	Modified:	17 Apr 6:06
Reporter:	Peter Elsner	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	8.4.5	OS:	Any (AlmaLinux/CloudLinux/Rocky Linux)
Assigned to:		CPU Architecture:	x86

Description:
After a nightly update, MySQL and its components got upgraded, causing database connection errors and permission denied errors.

Seems the only solution is to downgrade back down to 8.4.4.

How to repeat:
Install a server with MySQL 8.4.4, create a few databases, users, etc...  Verify that the sites work just fine. Then update it to 8.4.5. Verify that the sites stopped working with "database connection errors".

Downgrade by running: 

Find the MySQL upgrade with yum history:

yum history

In order to check the transaction, copy the ID number and run:

yum history info $ID

With $ID being the copied transaction.
Once the MySQL upgrade its found, you can undo it with the following:

yum history undo $ID

Suggested fix:
Seems the MySQL Datadirectory has changed? Trying to set it within my.cnf file does NOT fix this either. So, downgrade is the only option.  

Also seems like mysql-server has been replaced with mysql-cloud-server. 

Not sure if that is relevant.

It looks like last nights upgrade removed the mysql-community packages in favor of mysql-cloud?

# rpm -qa | grep ^mysql
mysql-cloud-selinux-8.4.5-1.1.el8.x86_64
mysql-cloud-server-8.4.5-1.1.el8.x86_64
mysql-shell-8.4.4-1.el8.x86_64
mysql-cloud-client-8.4.5-1.1.el8.x86_64
mysql84-community-release-el8-1.noarch
mysql-cloud-icu-data-files-8.4.5-1.1.el8.x86_64
mysql-cloud-common-8.4.5-1.1.el8.x86_64
mysql-cloud-devel-8.4.5-1.1.el8.x86_64
mysql-community-icu-data-files-8.4.5-1.el8.x86_64
mysql-community-client-plugins-8.4.5-1.el8.x86_64
mysql-cloud-libs-8.4.5-1.1.el8.x86_64

Seems like the repo has changed from mysql-community-* to mysql-cloud-*

After downgrading back to 8.4.4, It's a good idea to version lock the package to prevent it from updating again during the next night (until this can be fixed)...

Also not sure why no one from Oracle/MySQL has responded yet??

Hello Peter Elsner,

Thank you for the bug report.
Discussed your issue internally with release team and they informed that cloud packages were available by mistake for a short while but should be removed now. So, this should not happen again. 
Can you please check it once and let us know if you are facing any issues?

Regards,
Ashwini Patil

Thank you for the update. I have not seen any further issues from our customers since yesterday afternoon, so I assume this issue is now resolved.

Thank you for informing.