You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the relx extension script contract, extension scripts should exit with an appropriate result code.
riak/rel/files/riak-chkconfig does not do this (the two other extension scripts do), and therefore picks up the non-zero exit provided by the relx-generated bin/riak script.
The solution is to add the following (or something like it) to the end of the rel/files/riak-chkconfig file:
--- a/rel/files/riak-chkconfig
+++ b/rel/files/riak-chkconfig
@@ ...
echo $CUTTLE_CONF
+
+# No explicit exit from within script or tools, assumed to have succeeded.
+exit 0
The text was updated successfully, but these errors were encountered:
* planned combination for 3.0.13
basho/eleveldb#269 to be added once issues are resolved
* Release preparation - 3.0.13
* For testing of fix to KV1847
* Update with reference to conditional PUT changes
* Update riak-chkconfig
As per #1125
* Update following merge
* Tags for release
* planned combination for 3.0.13
basho/eleveldb#269 to be added once issues are resolved
* Release preparation - 3.0.13
* For testing of fix to KV1847
* Update with reference to conditional PUT changes
* Update riak-chkconfig
As per #1125
* Update following merge
* Tags for release
Per the
relx
extension script contract, extension scripts should exit with an appropriate result code.riak/rel/files/riak-chkconfig
does not do this (the two other extension scripts do), and therefore picks up the non-zero exit provided by therelx
-generatedbin/riak
script.The solution is to add the following (or something like it) to the end of the
rel/files/riak-chkconfig
file:The text was updated successfully, but these errors were encountered: