A change was made for development versions of Forums (edx/cs_comments_service) (e.g. on devstack) to use the mongo database name 'cs_comments_service' in place of 'cs_comments_service_development'. Hopefully no one is running Production and development from the same mongo instance. This change does not affect Ficus.
Longer
We've added configuration of additional authorization to mongo in ansible that required having the development database for cs_comments_service be more consistent with that of other environments (e.g. production).
If you update your cs_comments_service code, it will create the new database the next time you start it. This means all of your old data will go away in discussions on your devstack.
Again, these changes do not affect Ficus.
If you were building a recent devstack and saw the following error, you can try again***:
- ==> default: TASK [forum : update supervisor configuration] *********************************
- ==> default: skipping: [localhost]
- ==> default:
- ==> default: TASK [forum : initialize elasticsearch] ****************************************
- ==> default: fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["/edx/app/forum/cs_comments_service/bin/rake", "search:initialize"], "delta": "0:00:05.514543", "end": "2017-03-06 21:00:31.101816", "failed": true, "rc": 1, "start": "2017-03-06 21:00:25.587273", "stderr": "/edx/app/forum/cs_comments_service/lib/tasks/flags.rake:6: warning: already initialized constant ROOT\n/edx/app/forum/cs_comments_service/lib/tasks/kpis.rake:7: warning: already initialized constant ROOT\n/edx/app/forum/cs_comments_service/models/constants.rb:2: warning: already initialized constant COURSE_ID\nrake aborted!\nMongo::Error::OperationFailure: not authorized for query on cs_comments_service_development.blocked_hash (13)
*** Note that there are other issues on fresh devstacks of the master branch right now, so don't update until consulting the dev channel.
--