Bug #89584 5.7->8.0 upgrade crash with default-time-zone set
Submitted: 8 Feb 2018 8:39 Modified: 2 Mar 2018 19:57
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Data Dictionary Severity:S1 (Critical)
Version:8.0.4 OS:Any
Assigned to: CPU Architecture:Any

[8 Feb 2018 8:39] Shane Bester 
Description:
Affects debug/release builds of 8.0

[System] mysqld.exe (mysqld 8.0.4-rc-log) starting as process 10004 ...
mysqld.exe!Field_timestampf::get_date_internal()[field.cc:6007]
mysqld.exe!Field_temporal_with_date_and_timef::val_int()[field.cc:5675]
mysqld.exe!dd::Abstract_table_impl::restore_attributes()[abstract_table_impl.cc:141]
mysqld.exe!dd::View_impl::restore_attributes()[view_impl.cc:191]
mysqld.exe!dd::Entity_object_table_impl::restore_object_from_record()[entity_object_table_impl.cc:68]
mysqld.exe!dd::cache::Storage_adapter::get<dd::Primary_id_key,dd::Abstract_table>()[storage_adapter.cc:187]
mysqld.exe!dd::cache::Dictionary_client::acquire_uncached<dd::View>()[dictionary_client.cc:1170]
mysqld.exe!dd::cache::fetch<dd::View>()[dictionary_client.cc:2107]
mysqld.exe!dd::cache::Dictionary_client::fetch_schema_components<dd::View>()[dictionary_client.cc:2137]
mysqld.exe!`anonymous namespace'::update_plugins_I_S_metadata()[metadata.cc:428]
mysqld.exe!dd::info_schema::update_I_S_metadata()[metadata.cc:676]
mysqld.exe!handle_bootstrap()[bootstrap.cc:344]
mysqld.exe!pfs_spawn_thread()[pfs.cc:2997]
mysqld.exe!win_thread_start()[my_thread.cc:55]

Also crashed on:
 Ver 8.0.5-debug-log for Win64 on x86_64 ((Built on 2018/02/05))

How to repeat:
Put default-time-zone="+00:00"  into [mysqld] section of my.cnf.
Startup 8.0.4 on a clean 5.7.20 data directory.
Crashes on first attempt to start.
[2 Mar 2018 19:57] Daniel Price 
Posted by developer:
 
Fixed as of the upcoming 8.0.5 release, and here's the changelog entry:

After upgrading from MySQL 5.7 to MySQL 8.0, the first attempt to start
the server on a MySQL 5.7 data directory with --default-time-zone set to a
specific time value such as "+00:00" caused the server to exit.
[19 Mar 2018 12:39] Daniel Price 
Posted by developer:
 
The changelog entry now appears in the 8.0.11 release notes.
[29 Aug 2018 13:55] Daniel Price 
Posted by developer:
 
Test-related post fix changed. No changes to the 8.0.11 changelog entry.