[DOCS-6073] When resuming automation for a repl set in OpsManager / CloudManager, nodes in rs.conf() should be in the same order as before Created: 21/Aug/15  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Anthony Sansone (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 7 years, 29 weeks ago
Epic Link: C/OM Automation
Story Points: 1

 Description   

When automation for a replica set is suspended, OpsManager/CloudManager remembers the old replica set config. If manual replica set configuration amendments were made prior to resuming the automation, users need to make sure that the new rs.conf() has nodes in the same order as before (i.e. nodes _id's are the same).



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:51:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.