[
https://issues.apache.org/jira/browse/COUCHDB-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903189#comment-13903189
]
Darren Gibbard commented on COUCHDB-2064:
-----------------------------------------
For what it's worth - It appears that CouchDB writes the UUID to whatever
config file is last read in the startup process- so when i thought i'd be
clever and move my config items to "etc/couchdb/local.d/puppet.ini" it decided
to write the UUID config there instead.
So! A workaround is to do:
{code}
cat << EOF > etc/couchdb/local.d/uuid.ini
[couchdb]
EOF
{code}
Then, CouchDB puts the UUID config there, and leaves my actual config alone :)
> Move server uuid to separate file
> ---------------------------------
>
> Key: COUCHDB-2064
> URL: https://issues.apache.org/jira/browse/COUCHDB-2064
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Robert Newson
>
> Putting the uuid in local.ini causes issues for automatic provisioning
> systems.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
