Stackato 2.10.4 kato reporting fix

Posted by lorned on 2013-05-10 10:12
OS: All / Any | Product: Stackato | tags: 2.10.4 kato patch stackato status

Why does kato status report individual issues with different roles as issues of both roles?


A minor bug with stackato occurs when, for example, the postgres portion of the primary role and the postgres portion of the postgresql role are both in error. In this case, 'kato status' will display both the primary and postgresql node in the ISSUE# section for both roles. Removing one of the issues will correct this output, but for more clear reporting we have generated a patch.

You can download the patch at This patch will need to be applied to every node in your cluster. After uploading the patch, you can run it with the command 'sh'. After applying the patch you should restart the controller role on any nodes running it via 'kato restart controller'.

Note this is a fairly minor patch and the patch process is somewhat onerous for large clusters, and that restarting your controller process will cause the webUI to issue 500 errors temporarily.