Comment 4 for bug 1387345

I checked this issue together with https://bugs.launchpad.net/fuel/+bug/1386318 .
So for successful Heat HA work first of all need to fix mentioned earlier bug.

Now if we have wrong auth_encryption_keys then complex templates will fail.

For example I verified this bug using heat_autoscaling OSTF test (firstly I unskipped this test ).
Expected result:
1) heat-engines on all controllers are running and have the same auth_encryption_key
2) during autoscaling_test one of engines (on primary controller) completed stack creation, autoscaling and transfer control to another engine that execute stack deletion

Observed result:
1) heat-engines on all controllers are running(after a manual start ) and have the different auth_encryption_keys
2) during autoscaling_test one of engines (on primary controller) completed stack creation, autoscaling and stop its execution and transfer control to another engine that can't delete stack that was created by first engine because of database access problem (different encryption keys).

So need to fix mechanism of keys generation to avoid such problems.