[DOCS-8510] Migrating config servers with different names must include a step for changing the SSL certificates Created: 05/Aug/16 Updated: 16/Aug/16 Resolved: 15/Aug/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Blocker - P1 |
| Reporter: | Ricardo Lorenzo | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 26 weeks, 2 days ago | ||||
| Story Points: | 0.25 | ||||
| Description |
|
There must by a warning or an additional step in the procedure for migrating config servers with different names. Otherwise, the user will find SSL invalid hostname messages when attempting to start the mongos processes. |
| Comments |
| Comment by Githook User [ 16/Aug/16 ] |
|
Author: {u'username': u'rkumar-mongo', u'name': u'ravind', u'email': u'ravind.kumar@10gen.com'}Message: For each new config server, users must update the auth mechanism Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Ravind Kumar (Inactive) [ 15/Aug/16 ] |
| Comment by Emily Hall [ 05/Aug/16 ] |
|
Noted. We have assigned this to ravind.kumar and scheduled it into our current sprint. |