Bug #44991 deleting a new server not present prior to migration starting causes NPE

• Submitted: 20 May 2009 18:22
• Modified: 21 Sep 2009 14:59
• Reporter: Sloan Childers
• Status: Closed
• Category: MySQL Enterprise Monitor: Server
• Severity: S3 (Non-critical)
• Version: 2.0.x, 2.1.x
• OS: Any
• Assigned to: Sloan Childers
• CPU Architecture: Any

[20 May 2009 18:22] Sloan Childers

Description:
If you migrate from 1.3 to 2.0 and create a new server during the migration, then decide to delete it before migration is finished the new server delete operation will fail with an NPE.

How to repeat:
Start a long migration from 1.3 to 2.0 and create a new server during the migration, then delete it before migration is finished.

Suggested fix:
Add a null check in the migration server delete code.

[20 May 2009 18:48] Sloan Childers

fixed in 2.0.x and 2.1.x trees

[21 May 2009 16:50] Keith Russell

Patch installed in versions => 2.1.0.1048.

[30 May 2009 0:45] Marcos Palacios

Verified fixed in build 2.1.0.1049.

[21 Jul 2009 15:44] Tony Bedford

An entry was added to the 2.1.0 changelog:

If a migration from 1.3 to 2.0 was initiated and a new server created during the migration, but then deleted before migration was finished, the new server delete operation failed with an Null Pointer Exception (NPE).

[31 Jul 2009 3:51] Enterprise Tools JIRA Robot

Keith Russell writes: 
Patch installed in versions => 2.0.6.7159.

[26 Aug 2009 18:44] Enterprise Tools JIRA Robot

Bill Weber writes: 
verified fixed in build 2.0.6.7159

[21 Sep 2009 14:59] Tony Bedford

Updated changelog to reflect also fixed for 2.0.6.