MySQL Bugs: #95228: Error loading schema content after 8.0.16 upgrade

Bug #95228	Error loading schema content after 8.0.16 upgrade
Submitted:	2 May 2019 20:17	Modified:	9 Sep 2019 5:01
Reporter:	Scott Coldwell	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	8.0.16	OS:	MacOS (10.14.4)
Assigned to:		CPU Architecture:	Any

Description:
After upgrading MySQL Workbench 8.0.15 to 8.0.16 anytime I connect to a database, the following error shows up in the Output pane:

16:10:26	Error loading schema content	Error Code: 1142 SELECT command denied to user 'xxxxxxxxxxx' for table 'user_variables_by_thread'

In addition, each item in the schemas pane (Tables/Views/Stored Procedures/Functions) has  "could not be fetched" next to it.

Oddly enough, the tables and other items are actually listed and function normally.

Nothing else changed other than the Workbench upgrade.

How to repeat:
See description

Screenshot

Attachment: Screen Shot 2019-05-02 at 4.22.02 PM.png (image/png, text), 1.16 MiB.

Schemas

Attachment: 95228.png (image/png, text), 1.10 MiB.

Thank you for the bug report. I did the upgrade from MySQL Server 8.0.15 to 8.0.16 and Workbench from 8.0.15 and 8.0.16 and I couldne't the issue.

I think what may be the differentiator is that this was a connection to a MySQL 5.7 database.

I have exactly the same issue on win10 64bit.

Same behaviour as Scott described. 

Connecting to MySQL 5.6.34 and the Workbench is running on an up-to-date Gentoo install.

I have same problem.
Client: Windows 10 64bits - remote SQL-server: 5.7.25-28 release 28
The provider explains that they have disabeled the performance schema, and it's the reason for this error.

Me too, also Win10 x64  8.0.16

Connecting as 'root' works fine, but not another user.

Manually granting 'SELECT' rights on performance_schema for the user in question gets rid of the error.

I would post a command for doing that, except I'm not sure how I achieved it.  All attempts to do so reported errors, but something must have worked.

In my case to repeat the bug:
Make a user with Full rights to random schema.
Connect to workbench -> see above errors.
Add this permission, error goes away.

Probably users should not need this permission to load the view error-free. Or it should be automatically granted when the user is created.

working state

Attachment: workaround.png (image/png, text), 68.88 KiB.

Only affects users who don't have select permissions on performance_schema.  Apparently fixed (see https://bugs.mysql.com/bug.php?id=95335) for 8.0.17.  For now, roll back to 8.0.15 ...if you can find the download to do so.

Older version (8.0.15) can be downloaded at https://downloads.mysql.com/archives/workbench/.  You have to uninstall the 8.0.16 before installing 8.0.15, but it seems to maintain all settings, connections and configurations when you do install 8.0.15.

It seems this issue remains in v 8.0.17 - connecting to server v 5.7.26 with performance_schema disabled

I also experience this issue after upgrading to 8.0.17. MySQL version I'm connecting to is 5.7.23

I'm also still experiencing this in 8.0.17 (connecting to 5.7.27). As noted above, a workaround is to grant select privileges on performace_schema; the SQL for this is:

grant select on performance_schema.* to 'user'@'host';

Please change the status of this issue.  How to repeat has been mentioned in the comments by numerous people

In addition to changinge the status (as mentioned, many have shown how to repeat) also please update the version affected since it also applies to 8.0.17, the severity to S2 (this is a severe loss of service as it renders MySQL workbench virtually unusable unless a fix is applied), and the OS since it affects Windows as well as MAC.

I don't get the impression anyone from MySQL reads bugs that are filed with such low impact scores like 'Can't repeat, Mac OS X and S3'.  I therefore suggest the original reporter creates a new bug with a summary of all that is now known about it (for instance it affects Windows as well as Mac so it's probably better to say All OS, and it is most certainly repeatable), and just puts a comment on this bug with the new bug ID.

Since this has not been reopened, I opened new issue at https://bugs.mysql.com/bug.php?id=96793 and referenced both this and https://bugs.mysql.com/bug.php?id=95335.