> Hi Laurent,
>
> Thanks for testing. Would you be able to test an install from scratch from
> -proposed without upgrading? Then we can verify this particular bug and get
> another bug opened for the upgrade issue.
I tested installing directly using cloud-archive:pike-proposed and the problem
persist. See screenshot attached.
The dashboard is loading a css file named 34f8a8f8d5e5.css[0], this file does
not contain the updated rule (color: #fff !important), but other one of the
files[1] available under /var/lib/openstack-dashboard/static/dashboard/css contains
the expected rule
Also I could verify as well that if you install the package from -proposed and
*then* you try to rollback to the version in -updates, the website css gets
totally broken as reported by Laurent.
> Hi Laurent,
>
> Thanks for testing. Would you be able to test an install from scratch from
> -proposed without upgrading? Then we can verify this particular bug and get
> another bug opened for the upgrade issue.
I tested installing directly using cloud-archive: pike-proposed and the problem
persist. See screenshot attached.
The dashboard is loading a css file named 34f8a8f8d5e5. css[0], this file does openstack- dashboard/ static/ dashboard/ css contains
not contain the updated rule (color: #fff !important), but other one of the
files[1] available under /var/lib/
the expected rule
The difference between both css can be found at paste.ubuntu. com/25636811/
http://
Also I could verify as well that if you install the package from -proposed and
*then* you try to rollback to the version in -updates, the website css gets
totally broken as reported by Laurent.
[0] http:// pastebin. ubuntu. com/25636789/ paste.ubuntu. com/25636802/
[1] http://