collectstatic and compress are not producing consistent results

[Eric Peterson]

I have 3 identical machines (host names are different), and I have an ansible script to deploy horizon. As part of the script we run collectstatic and compress by hand (offline compression).

Each machine's static contents looks slightly different.

This causes horizon to fail when behind a load balancer, specifically when round robin or least conn policies are in place.

[Eric Peterson (ericpeterson-l)]

If I rerun these steps on the same machine, it's always consistent / the same / produces the same results.

On two machines with the same code I get:

ls -al static/dashboard/js/
-rw-rw-r-- 1 horizon horizon 494887 Jul 20 20:22 76adef98ad14.js
-rw-rw-r-- 1 horizon horizon 1095117 Jul 20 20:22 9f5a794ddce8.js
-rw-rw-r-- 1 horizon horizon 1029 Jul 20 20:22 d1540ac79bc7.js

ls -al static/dashboard/js/
-rw-rw-r-- 1 horizon horizon 494887 Jul 20 20:25 76adef98ad14.js
-rw-rw-r-- 1 horizon horizon 1095117 Jul 20 20:25 81e54d551c21.js
-rw-rw-r-- 1 horizon horizon 1029 Jul 20 20:25 d1540ac79bc7.js

[Eric Peterson (ericpeterson-l)]

update: The order of the entries of HORIZON_CONFIG['js_files'] is different, on each machine

[Eric Peterson (ericpeterson-l)]

I can confirm after doing a HORIZON_CONFIG['js_files'].sort() -> it works correctly

[Eric Peterson (ericpeterson-l)]

Scratch the above comment, after sorting it produces reliable compression artifacts. However, the js is not in the correct order and it fails horribly for other reasons.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/204197

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/204197
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b6399c69048761584824597b9af38f3c9db4a483
Submitter: Jenkins
Branch: master

commit b6399c69048761584824597b9af38f3c9db4a483
Author: Shaoquan Chen <email address hidden>
Date: Tue Jul 21 12:18:53 2015 -0600

    Proving JS source files in consistent order

    In some deployment environment, the JS source files need to be listed
    in consistent order so that they will have the same cache key value for
    the compressed JS file.

    Change-Id: Ib187a85b7a1fca03c0eb78b411cf121017d40890
    Closes-Bug: #1476383