OpenStack Dashboard (Horizon)

Frontend version checking

Asked by Joe Harrison

I installed Horizon from the RDO havana-2 repository and was not able to log in through the web interface. The login silently failed. There was no error message displayed in either horizon logs or the browser.

It turns out that openstack-dashboard 2013.2 0.3b2 installed and django-openstack-auth 1.0.2 are incompatible versions, as specified in the requirements of Horizon.

This was permitted due to incorrect versions specified in the .spec file of the RPM. However, should Horizon not report either via logs or via the web browser that there are incompatible versions of packages/dependencies installed? It seems quite bad that Horizon wasn't checking the versions of the packages it was using at the time.

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Dashboard (Horizon) Edit question
Assignee:
Matthias Runge Edit question
Solved by:
Matthias Runge
Solved:
Last query:
Last reply:
Revision history for this message
Best Matthias Runge (mrunge) said : 		#1

Yeah, you got python-django-openstack-auth from EPEL. We added python-django-openstack-auth-1.0.11 to the havana repository.

Either
yum update && service httpd restart should fix your issue.

or
rpm -Uvh http://kojipkgs.fedoraproject.org/packages/python-django-openstack-auth/1.0.11/1.el6/noarch/python-django-openstack-auth-1.0.11-1.el6.noarch.rpm
service httpd restart

should fix your isue.

Revision history for this message
Joe Harrison (joehazzers) said : 		#2

I'm aware that it's now fixed, but my concern is that Horizon did not complain about (or maybe not even notice!) that the wrong version was being used. Is it worth Horizon doing version checks?

Revision history for this message
Matthias Runge (mrunge) said : 		#3

I don't think it's worth Horizon is doing such checks.
Here is why:
- if you want those checks, they need to get executed during each page visit.
- We're using packages and repositories. Thus should take care of putting compatible packages together
- often enough, requires in the projects are updated too aggressively, in this case, a version 1.0.7 should be sufficient.

We don't need to argue about horizons very limited feedback about issues at all. But this question is not about that.

Revision history for this message
Joe Harrison (joehazzers) said : 		#4

Thanks Matthias Runge, that solved my question.

Revision history for this message
Joe Harrison (joehazzers) said : 		#5

Also, one more comment:

"We're using packages and repositories. Thus should take care of putting compatible packages together"

Just so you know, it didn't, hence why this happened.

Revision history for this message
Matthias Runge (mrunge) said : 		#6

Yes, agreed, this shouldn't happen and it was corrected.