192.168.202.103 = public controller iface
192.168.203.103 = private controller iface
anyway, I still get the login problem using any of those values
Le 20/02/2013 06:59, Kieran Spear a écrit :
On 20 February 2013 03:40, Michaël Van de Borne
michael.vandebo...@cetic.be
Also, on quick think to look is the apache error log while you access the
horizon.
look at the log as, tail -f /var/log/apache/error.log.
On Wed, Feb 20, 2013 at 5:07 PM, Michaël Van de Borne
michael.vandebo...@cetic.be wrote:
192.168.202.103 = public controller iface
192.168.203.103 =
I solved the problem by downgrading the horizon for packages below
apt-get install \
openstack-dashboard=2012.1.3+stable~20120815-691dd2-0ubuntu1.1 \
openstack-dashboard-ubuntu-theme=2012.1.3+stable~20120815-691dd2-0ubuntu1.1
\
python-django-horizon=2012.1.3+stable~20120815-691dd2-0ubuntu1.1
att
I did the update of all services (new, cinder, glance, horizon, keystone),
and let all the options of the * default. conf, just changing the filter
and sql session: authtoken.
And now it works again
0.2-1ubuntu1~cloud0 - python-jsonschema
0.6-1ubuntu1~cloud0 - python-prettytable
Same problem here. Running Grizzly.
Dashboard keeps prompting me for my credentials. Pretty sure
dashboard sends wrong tenant name to keystone. Here is the
keystone.log entry:
2013-02-19 16:55:06 WARNING [keystone.common.wsgi] Authorization
failed. The
I checked /etc/nova/api-paste.ini.
Here's the relevant section in it:
[filter:authtoken]
paste.filter_factory =
keystone.middleware.auth_token:filter_factory
auth_host = 192.168.203.103
auth_port = 35357
auth_protocol = http
Moreover (sorry for spamming), this
command works fine:
root@leonard:/etc/init.d# keystone --os-username nova
--os-password openstack --os-tenant-name service --os-auth-url
http://192.168.203.103:5000/v2.0/ token-get
On 20 February 2013 03:40, Michaël Van de Borne michael.vandebo...@cetic.be
wrote:
Same problem here. Running Grizzly. Dashboard keeps prompting me for my
credentials. Pretty sure dashboard sends wrong tenant name to keystone.
Here's the relevant section in
Hi Stackers-
I have successfully installed folsom in my test setup.
But when I browse Horison, with admin/password as credentials, I get this
error.
[Tue Feb 12 10:03:16 2013] [error] unable to retrieve service catalog with
token
[Tue Feb 12 10:03:16 2013] [error] Traceback (most recent call
I've had this problem before, in my experience it's not a problem with
keystone, it's a problem with nova (by the looks of the traceback). I
believe it's a bug in Horizon because you'll find a lot of people with this
issue if you Google it. I don't have an answer on how to fix it, other than
don't
10 matches
Mail list logo