Bug #43846 Error when renaming replication group to a previous name

• Submitted: 25 Mar 2009 0:04
• Modified: 22 May 2009 11:06
• Reporter: Bill Weber
• Status: Closed
• Category: Monitoring: Server
• Severity: S3 (Non-critical)
• Version: 2.0.5.7153
• OS: Any
• Assigned to: Darren Oldag
• Target Version: 2.0.6

[25 Mar 2009 0:04] Bill Weber

Description:
Get an error when trying to rename a replication group to one that was previously
deleted.

How to repeat:
1. go to Manage Servers page in dashboard
2. start a couple agents monitoring 2 servers in a replication topology
3. wait for at least a minute and refresh the Manage Servers page - should see topology
"Replication 1"
4. using link, rename the group from "Replication 1" to "Test Me"
5. stop both agents
6. wait for 10 seconds and refresh Manage Servers page - should see agents down
7. delete both servers from the UI using links - the "Test Me" replication group is
automatically deleted after deleting the second server
8. start the agents again
9. wait for at least a minute and refresh the Manage Servers page - should see topology
"Replication 1" again
10. try to rename the group from "Replication 1" to "Test Me" - get error saying "Test
Me" already exists

[26 Mar 2009 1:49] Bill Weber

verified fixed in build 2.0.6.7157

[22 May 2009 11:06] Tony Bedford

An entry was added to the 2.0.6 changelog:

An error was generated when an attempt was made to rename a Replication Group to one that
had previously been deleted.