Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 10.0.10
-
Fix Version/s: 10.0
-
Component/s: None
-
Labels:None
Description
Test case for this bug (disabled_replication.test) fails in 10.0. Please check if we're affected by this problem.
revno: 3690.1.74 committer: Alfranio Correia <alfranio.correia@oracle.com> branch nick: mysql-trunk timestamp: Wed 2012-03-14 09:52:49 +0000 message: BUG#13504281 - FOLLOW UP 'LIVE UPGRADE FAILS BETWEEN 5.5 -> 5.6.4 (BUG#13427444) Replication objects are always created so repositories are checked in the initialization routine even when --server-id is equal to "0" (i.e. default value), although a valid --server-id (i.e. not equal to the default value) is a requirement to use either a master or slave. This may cause confusion in live upgrades when an user tries to migrate from 5.5 to 5.6 because the operation stops with an error and asking users to provide --skip-slave-start in order to avoid the problem. To avoid this scenario, we only create the replication objects when a valid --server-id is provided.
Gliffy Diagrams
Attachments
Issue Links
- is part of
-
MDEV-4784 merge test cases from 5.6
-
- Stalled
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
This test verifies that with --server-id=0 replication commands from the list below fail with an error: