[DOCS-4237] MMS Automation: Document how to make changes when previous deploy is stuck Created: 25/Oct/14 Updated: 16/Mar/15 Resolved: 03/Feb/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.18 |
| Type: | Task | Priority: | Blocker - P1 |
| Reporter: | Cailin Nelson | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 2 weeks, 1 day ago | ||||||||
| Description |
|
In some circumstances, making a second change to a configuration while it is trying to deploy the first change is not advisable. Therefore, we tried to make this something that users would not do "by accident". However, it seems that users have trouble figuring out to make a change, in the case where they need to correct their deployment configuration. To make a change the user needs to 1. Click the EDIT CONFIGURATION link |
| Comments |
| Comment by Githook User [ 03/Feb/15 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |