12:18 p.m.
Hi!
I made a clean install of Havana on a machine and by the time it finished installing, I
was unable to use the dashboard as a message saying:
Something went wrong!
An unexpected error has occurred. Try refreshing the page. If that doesn't help,
contact your local administrator.
I'm now trying to find what the problem is and I found the status of the dashboard in
openstack-status is 500 and that neutron-dhcp-agent failed to start with this relevant
part of the dhcp-agent.log:
2013-10-25 18:00:15.550 2165 INFO neutron.common.config [-] Logging
enabled!
2013-10-25 18:00:15.551 2165 ERROR neutron.common.legacy [-] Skipping unknown group key:
firewall_driver
2013-10-25 18:00:15.585 2165 WARNING neutron.agent.linux.dhcp [-] Unable to determine
dnsmasq version. Please ensure that its version is 2.59 or above!
2013-10-25 18:00:15.658 2165 ERROR neutron.openstack.common.threadgroup [-] [Errno 22]
Invalid argument
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup Traceback (most
recent call last):
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/threadgroup.py", line
117, in wait
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup x.wait()
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/threadgroup.py", line
49, in wait
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup return
self.thread.wait()
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 168, in wait
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup return
self._exit_event.wait()
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/eventlet/event.py", line 116, in wait
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup return
hubs.get_hub().switch()
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 187, in switch
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup return
self.greenlet.switch()
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 238, in run
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup self.wait(0)
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/eventlet/hubs/poll.py", line 84, in wait
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup presult =
self.do_poll(seconds)
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup File
"/usr/lib/python2.7/site-packages/eventlet/hubs/epolls.py", line 61, in do_poll
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup return
self.poll.poll(seconds)
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup IOError: [Errno
22] Invalid argument
2013-10-25 18:00:15.658 2165 TRACE neutron.openstack.common.threadgroup
2013-10-25 18:00:15.665 2165 ERROR neutron.agent.dhcp_agent [-] Failed reporting state!
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent Traceback (most recent call
last):
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/agent/dhcp_agent.py", line 555, in
_report_state
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
self.state_rpc.report_state(ctx, self.agent_state, self.use_call)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/agent/rpc.py", line 72, in
report_state
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent return self.call(context,
msg, topic=self.topic)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/proxy.py", line
126, in call
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent result =
rpc.call(context, real_topic, msg, timeout)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/__init__.py",
line 140, in call
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent return
_get_impl().call(CONF, context, topic, msg, timeout)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_qpid.py",
line 767, in call
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
rpc_amqp.get_connection_pool(conf, Connection))
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/amqp.py", line
549, in call
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent rv = multicall(conf,
context, topic, msg, timeout, connection_pool)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/amqp.py", line
539, in multicall
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
connection_pool.reply_proxy = ReplyProxy(conf, connection_pool)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/amqp.py", line
192, in __init__
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent super(ReplyProxy,
self).__init__(conf, connection_pool, pooled=False)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/amqp.py", line
126, in __init__
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
server_params=server_params)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_qpid.py",
line 458, in __init__
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self.reconnect()
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_qpid.py",
line 499, in reconnect
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self.connection.open()
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"<string>", line 6, in open
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 273, in
open
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
self.attach(timeout=timeout)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"<string>", line 6, in attach
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 291, in
attach
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent if not
self._ewait(lambda: self._transport_connected and not self._unlinked(), timeout=timeout):
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 224, in
_ewait
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self.check_error()
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 217, in
check_error
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent raise e
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent InternalError: Traceback
(most recent call last):
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/driver.py", line 495, in
dispatch
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self.connect()
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/driver.py", line 522, in
connect
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self._transport =
trans(self.connection, host, port)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/messaging/transports.py", line 28, in
__init__
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self.socket =
connect(host, port)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/qpid/util.py", line 68, in connect
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent sock.connect(sa)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/eventlet/greenio.py", line 180, in connect
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent trampoline(fd,
write=True)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/eventlet/hubs/__init__.py", line 119, in
trampoline
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent listener =
hub.add(hub.WRITE, fileno, current.switch)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/eventlet/hubs/epolls.py", line 52, in add
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent self.register(fileno,
new=True)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent File
"/usr/lib/python2.7/site-packages/eventlet/hubs/poll.py", line 44, in register
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
self.poll.register(fileno, mask)
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent IOError: [Errno 22] Invalid
argument
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
2013-10-25 18:00:15.665 2165 TRACE neutron.agent.dhcp_agent
I seem to have read somewhere that a 500 status in horizon may be caused by one of the
others components failing. So I'm assuming this could be my problem.
Furthermore, I found that snippet may be the relevant part of the logs because I found
some bug reports indicating that this could be a problem with dnsmasq. The problem is that
I have version 2.66 of dnsmasq installed in the system.
Can someone help me?
Thank you very much in advance,
Diogo Vieira
12:26 p.m.
On 10/25/2013 06:18 PM, Diogo Vieira wrote:
Hi!
I made a clean install of Havana on a machine and by the time it finished installing, I
was unable to use the dashboard as a message saying:
> Something went wrong!
>
> An unexpected error has occurred. Try refreshing the page. If that doesn't help,
contact your local administrator.
I'm now trying to find what the problem is and I found the status of the dashboard in
openstack-status is 500 and that neutron-dhcp-agent failed to start with this relevant
part of the dhcp-agent.log:
> 2013-10-25 18:00:15.550 2165 INFO neutron.common.config [-] Logging enabled!
> 2013-10-25 18:00:15.551 2165 ERROR neutron.common.legacy [-] Skipping unknown group
key: firewall_driver
> 2013-10-25 18:00:15.585 2165 WARNING neutron.agent.linux.dhcp [-] Unable to determine
dnsmasq version. Please ensure that its version is 2.59 or above!
> 2013-10-25 18:00:15.658 2165 ERROR neutron.openstack.common.threadgroup [-] [Errno
22] Invalid argument
I seem to have read somewhere that a 500 status in horizon may be
caused by one of the others components failing. So I'm assuming this could be my
problem.
Furthermore, I found that snippet may be the relevant part of the logs because I found
some bug reports indicating that this could be a problem with dnsmasq. The problem is that
I have version 2.66 of dnsmasq installed in the system.
Right http://pad.lv/1212401
That weird error happens when dnsmasq is not installed.
Where did you get dnsmasq 2.66 from?
Is the dnsmasq service running?
Note dnsmasq-2.48 may seem too old giben the above message,
but is patched to have the required functionality.
thanks,
Pádraig.
12:36 p.m.
On Oct 25, 2013, at 6:26 PM, Pádraig Brady <pbrady(a)redhat.com> wrote:
On 10/25/2013 06:18 PM, Diogo Vieira wrote:
> Hi!
>
> I made a clean install of Havana on a machine and by the time it finished installing,
I was unable to use the dashboard as a message saying:
>
>> Something went wrong!
>>
>> An unexpected error has occurred. Try refreshing the page. If that doesn't
help, contact your local administrator.
>
> I'm now trying to find what the problem is and I found the status of the
dashboard in openstack-status is 500 and that neutron-dhcp-agent failed to start with this
relevant part of the dhcp-agent.log:
>
>> 2013-10-25 18:00:15.550 2165 INFO neutron.common.config [-] Logging enabled!
>> 2013-10-25 18:00:15.551 2165 ERROR neutron.common.legacy [-] Skipping unknown
group key: firewall_driver
>> 2013-10-25 18:00:15.585 2165 WARNING neutron.agent.linux.dhcp [-] Unable to
determine dnsmasq version. Please ensure that its version is 2.59 or above!
>> 2013-10-25 18:00:15.658 2165 ERROR neutron.openstack.common.threadgroup [-]
[Errno 22] Invalid argument
> I seem to have read somewhere that a 500 status in horizon may be caused by one of
the others components failing. So I'm assuming this could be my problem.
>
> Furthermore, I found that snippet may be the relevant part of the logs because I
found some bug reports indicating that this could be a problem with dnsmasq. The problem
is that I have version 2.66 of dnsmasq installed in the system.
Right http://pad.lv/1212401
That weird error happens when dnsmasq is not installed.
Where did you get dnsmasq 2.66 from?
Is the dnsmasq service running?
Note dnsmasq-2.48 may seem too old giben the above message,
but is patched to have the required functionality.
thanks,
Pádraig.
I got dnsmasq from the repositories (running on a Fedora 19)
[root@openstack ~(keystone_admin)]# dnsmasq -v
Dnsmasq version 2.66 Copyright (c) 2000-2013 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP
no-conntrack ipset auth
This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
And it is running:
[root@openstack ~(keystone_admin)]# service dnsmasq status
Redirecting to /bin/systemctl status dnsmasq.service
dnsmasq.service - DNS caching server.
Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled)
Active: active (running) since Fri 2013-10-25 18:31:43 WEST; 2min 41s ago
Main PID: 8389 (dnsmasq)
CGroup: name=systemd:/system/dnsmasq.service
└─8389 /usr/sbin/dnsmasq -k
(..)
Thank you,
Diogo Vieira
12:37 p.m.
On Oct 25, 2013, at 6:28 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
> I seem to have read somewhere that a 500 status in horizon may
be caused by one of the others components failing. So I'm assuming this could be my
problem.
Please, run
# rpm -qa | grep python-django
Sure:
[root@openstack ~(keystone_admin)]# rpm -qa | grep python-django
python-django-appconf-0.6-1.fc19.noarch
python-django-1.5.4-1.fc19.noarch
python-django-openstack-auth-1.1.2-1.fc21.noarch
python-django-compressor-1.3-1.fc19.noarch
python-django-horizon-2013.2-1.fc20.noarch
Thank you,
Diogo Vieira
12:49 p.m.
PLease, run
$ sudo yum -y remove python-django
$ sudo yum -y install python-django14
If it won't help , then rerun
$ sudo packstack --answer-file=/home/../answer-file-name
one more time.
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
From: dfv(a)eurotux.com
Date: Fri, 25 Oct 2013 18:37:43 +0100
CC: rdo-list(a)redhat.com
To: bderzhavets(a)hotmail.com
On Oct 25, 2013, at 6:28 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:> I
seem to have read somewhere that a 500 status in horizon may be caused by one of the
others components failing. So I'm assuming this could be my problem.
Please, run
# rpm -qa | grep python-django Sure:
[root@openstack ~(keystone_admin)]# rpm -qa | grep python-django
python-django-appconf-0.6-1.fc19.noarchpython-django-1.5.4-1.fc19.noarchpython-django-openstack-auth-1.1.2-1.fc21.noarchpython-django-compressor-1.3-1.fc19.noarchpython-django-horizon-2013.2-1.fc20.noarch
Thank you,Diogo Vieira
1:10 p.m.
On Oct 25, 2013, at 6:49 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
PLease, run
$ sudo yum -y remove python-django
$ sudo yum -y install python-django14
If it won't help , then rerun
$ sudo packstack --answer-file=/home/../answer-file-name
one more time.
>
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
From: dfv(a)eurotux.com
Date: Fri, 25 Oct 2013 18:37:43 +0100
CC: rdo-list(a)redhat.com
To: bderzhavets(a)hotmail.com
On Oct 25, 2013, at 6:28 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
> I seem to have read somewhere that a 500 status in horizon may be caused by one of
the others components failing. So I'm assuming this could be my problem.
Please, run
# rpm -qa | grep python-django
Sure:
[root@openstack ~(keystone_admin)]# rpm -qa | grep python-django
python-django-appconf-0.6-1.fc19.noarch
python-django-1.5.4-1.fc19.noarch
python-django-openstack-auth-1.1.2-1.fc21.noarch
python-django-compressor-1.3-1.fc19.noarch
python-django-horizon-2013.2-1.fc20.noarch
Thank you,
Diogo Vieira
Uninstalling python-django and re-running packstack seems to have worked. Thank you very
much!
Thanks,
Diogo Vieira
1:27 p.m.
That's known bug on F19 . Previous version of installer gave packages conflict and
failed,
what is actually much better then it happens in meantime.
New version completes OK, but service openstack-horizon shows up status 500.
Dashboard doesn't work.
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
From: dfv(a)eurotux.com
Date: Fri, 25 Oct 2013 19:10:37 +0100
CC: rdo-list(a)redhat.com
To: bderzhavets(a)hotmail.com
On Oct 25, 2013, at 6:49 PM, Boris Derzhavets <bderzhavets(a)hotmail.com>
wrote:PLease, run
$ sudo yum -y remove python-django
$ sudo yum -y install python-django14
If it won't help , then rerun
$ sudo packstack --answer-file=/home/../answer-file-name
one more time.
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
From: dfv(a)eurotux.com
Date: Fri, 25 Oct 2013 18:37:43 +0100
CC: rdo-list(a)redhat.com
To: bderzhavets(a)hotmail.com
On Oct 25, 2013, at 6:28 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:> I
seem to have read somewhere that a 500 status in horizon may be caused by one of the
others components failing. So I'm assuming this could be my problem.
Please, run
# rpm -qa | grep python-django Sure:
[root@openstack ~(keystone_admin)]# rpm -qa | grep python-django
python-django-appconf-0.6-1.fc19.noarchpython-django-1.5.4-1.fc19.noarchpython-django-openstack-auth-1.1.2-1.fc21.noarchpython-django-compressor-1.3-1.fc19.noarchpython-django-horizon-2013.2-1.fc20.noarch
Thank you,Diogo Vieira
Uninstalling python-django and re-running packstack seems to have worked. Thank you very
much!
Thanks,Diogo Vieira
1:46 p.m.
On 25/10/13 20:27, Boris Derzhavets wrote:
That's known bug on F19 . Previous version of installer gave
packages
conflict and failed,
what is actually much better then it happens in meantime.
New version completes OK, but service openstack-horizon shows up
status 500.
Dashboard doesn't work.
What? Where did you get that?
So basically you're saying, Django-1.4 works, Django-1.5 does not work,
is that correct?
If that's the case, please verify that ALLOWED_HOSTS in
/etc/openstack-dashboard/local_settings contains your domainname part.
I assume, there is a mis-configuration of ALLOWED_HOSTS in
/etc/openstack-dashboard/local_settings.
Matthias
2:27 p.m.
So basically you're saying, Django-1.4 works, Django-1.5 does not
work,
is that correct?
No python-django14 works, python-django-1.5 doesn't
View also :-
Install OpenStack Grizzly on Fedora 19 with Quantum Networking (Linux
Today)http://funwithlinux.net/2013/08/install-openstack-grizzly-on-fedora...
Quote :
Next, the openstack-dashboard won’t install due to dependency problem. The fix is to
install python-django14 manually. yum install python-django14
end quote.
Boris.
> Date: Fri, 25 Oct 2013 20:46:22 +0200
> From: mrunge(a)redhat.com
> To: rdo-list(a)redhat.com
> Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
>
> On 25/10/13 20:27, Boris Derzhavets wrote:
> > That's known bug on F19 . Previous version of installer gave packages
> > conflict and failed,
> > what is actually much better then it happens in meantime.
> >
> > New version completes OK, but service openstack-horizon shows up
> > status 500.
> > Dashboard doesn't work.
> >
> What? Where did you get that?
>
So basically you're saying, Django-1.4 works, Django-1.5 does not
work,
is that correct?
> If that's the case, please verify that ALLOWED_HOSTS in
> /etc/openstack-dashboard/local_settings contains your domainname part.
>
> I assume, there is a mis-configuration of ALLOWED_HOSTS in
> /etc/openstack-dashboard/local_settings.
>
> Matthias
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
3:32 p.m.
Please, view https://bugzilla.redhat.com/show_bug.cgi?id=978647
In meantime
# rpm -qa | grep python-django-horizon
python-django-horizon-2013.2-1.fc20.noarch
still not fixed
From: bderzhavets(a)hotmail.com
To: mrunge(a)redhat.com; rdo-list(a)redhat.com
Date: Fri, 25 Oct 2013 15:27:01 -0400
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
So basically you're saying, Django-1.4 works, Django-1.5 does not
work,
is that correct?
No python-django14 works, python-django-1.5 doesn't
View also :-
Install OpenStack Grizzly on Fedora 19 with Quantum Networking (Linux
Today)http://funwithlinux.net/2013/08/install-openstack-grizzly-on-fedora...
Quote :
Next, the openstack-dashboard won’t install due to dependency problem. The fix is to
install python-django14 manually. yum install python-django14
end quote.
Boris.
> Date: Fri, 25 Oct 2013 20:46:22 +0200
> From: mrunge(a)redhat.com
> To: rdo-list(a)redhat.com
> Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
>
> On 25/10/13 20:27, Boris Derzhavets wrote:
> > That's known bug on F19 . Previous version of installer gave packages
> > conflict and failed,
> > what is actually much better then it happens in meantime.
> >
> > New version completes OK, but service openstack-horizon shows up
> > status 500.
> > Dashboard doesn't work.
> >
> What? Where did you get that?
>
So basically you're saying, Django-1.4 works, Django-1.5 does not
work,
is that correct?
> If that's the case, please verify that ALLOWED_HOSTS in
> /etc/openstack-dashboard/local_settings contains your domainname part.
>
> I assume, there is a mis-configuration of ALLOWED_HOSTS in
> /etc/openstack-dashboard/local_settings.
>
> Matthias
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
9:17 p.m.
On 10/25/2013 09:32 PM, Boris Derzhavets wrote:
Please, view https://bugzilla.redhat.com/show_bug.cgi?id=978647
In meantime
# rpm -qa | grep python-django-horizon
python-django-horizon-2013.2-1.fc20.noarch
Note Fedora 19 official has grizzly (2013.1) which is
what the above bug pertains to. I.E. that version
requires django 1.4, which currently requires the work around
described in the bug.
Your issue is actually with the havana (2013.2) version
copied from Fedora 20 to a Fedora 19 in the RDO specific
repositories for convenience. That version is supposedly
compatible with django 1.5 (hence why it installed with
django 1.5 without any dependency issues). By forcing
django 1.4 with a similar method used in bug 978647,
you avoided the issue. So this is a separate bug (with django 1.5),
which may be related to ALLOWED_HOSTS setting.
thanks,
Pádraig.
5:17 a.m.
Just to close this issue, the problem with the neutron-dhcp-agent was not the dnsmasq
version but SELinux policies. The command 'setenforce 0' seems to have fixed the
problem and the agent started normally.
Should I open a bug about this (because it seems that some policies have not been set
correctly)?
Thank you,
Diogo Vieira
On Oct 25, 2013, at 7:27 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
That's known bug on F19 . Previous version of installer gave
packages conflict and failed,
what is actually much better then it happens in meantime.
New version completes OK, but service openstack-horizon shows up status 500.
Dashboard doesn't work.
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
From: dfv(a)eurotux.com
Date: Fri, 25 Oct 2013 19:10:37 +0100
CC: rdo-list(a)redhat.com
To: bderzhavets(a)hotmail.com
On Oct 25, 2013, at 6:49 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
PLease, run
$ sudo yum -y remove python-django
$ sudo yum -y install python-django14
If it won't help , then rerun
$ sudo packstack --answer-file=/home/../answer-file-name
one more time.
>
Subject: Re: [Rdo-list] Horizon in fresh install of Havana not working
From: dfv(a)eurotux.com
Date: Fri, 25 Oct 2013 18:37:43 +0100
CC: rdo-list(a)redhat.com
To: bderzhavets(a)hotmail.com
On Oct 25, 2013, at 6:28 PM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
> I seem to have read somewhere that a 500 status in horizon may be caused by one of
the others components failing. So I'm assuming this could be my problem.
Please, run
# rpm -qa | grep python-django
Sure:
[root@openstack ~(keystone_admin)]# rpm -qa | grep python-django
python-django-appconf-0.6-1.fc19.noarch
python-django-1.5.4-1.fc19.noarch
python-django-openstack-auth-1.1.2-1.fc21.noarch
python-django-compressor-1.3-1.fc19.noarch
python-django-horizon-2013.2-1.fc20.noarch
Thank you,
Diogo Vieira
Uninstalling python-django and re-running packstack seems to have worked. Thank you very
much!
Thanks,
Diogo Vieira
6:52 a.m.
On 10/29/2013 06:17 AM, Diogo Vieira wrote:
Just to close this issue, the problem with the neutron-dhcp-agent
was
not the dnsmasq version but SELinux policies. The command 'setenforce 0'
seems to have fixed the problem and the agent started normally.
Should I open a bug about this (because it seems that some policies have
not been set correctly)?
Can you get a list of avc messages? If SELinux is the issue, there
should be some avc errors in the logs that you can retrieve with:
sudo audit2allow -a
sudo audit2why -a
(In Fedora these commands are in the policycoreutils-python package)
But yes, file a bug with the avc messages that look like they are
interfering with Neutron DHCP agent and we can work to fix the policies.
Also, please let us know which version of selinux-policy and
selinux-policy-targeted are installed on your machine.
Perry
7:22 a.m.
Opened the bug here[1] with the info you requested.
Thank you,
Diogo Vieira
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1024330
On Oct 29, 2013, at 11:52 AM, Perry Myers <pmyers(a)redhat.com> wrote:
On 10/29/2013 06:17 AM, Diogo Vieira wrote:
> Just to close this issue, the problem with the neutron-dhcp-agent was
> not the dnsmasq version but SELinux policies. The command 'setenforce 0'
> seems to have fixed the problem and the agent started normally.
>
> Should I open a bug about this (because it seems that some policies have
> not been set correctly)?
Can you get a list of avc messages? If SELinux is the issue, there
should be some avc errors in the logs that you can retrieve with:
sudo audit2allow -a
sudo audit2why -a
(In Fedora these commands are in the policycoreutils-python package)
But yes, file a bug with the avc messages that look like they are
interfering with Neutron DHCP agent and we can work to fix the policies.
Also, please let us know which version of selinux-policy and
selinux-policy-targeted are installed on your machine.
Perry
1:49 p.m.
On 25/10/13 20:10, Diogo Vieira wrote:
Uninstalling python-django and re-running packstack seems to have
worked. Thank you very much!
Glad it worked for you.
Uninstalling python-django will have removed python-django-horizon,
openstack-dashboard and every other dependency here.
Re-running packstack has probably overwritten all configs. In that case,
we will never found out, what went wrong here.
Matthias
3832
days inactive
3836
days old
15 comments
5 participants
participants (5)
-
Boris Derzhavets -
Diogo Vieira -
Matthias Runge -
Perry Myers -
Pádraig Brady