The change needs to be reviewed and merged into the stable/essex branch
upstream before it will be updated in Ubuntu. The review you linked
expired and the change was never merged. Perhaps re-submit it and ping
someone on the stable maintenance team for the required approval?
--
You received
The change needs to be reviewed and merged into the stable/essex branch
upstream before it will be updated in Ubuntu. The review you linked
expired and the change was never merged. Perhaps re-submit it and ping
someone on the stable maintenance team for the required approval?
--
You received
Any idea when the fix in https://review.openstack.org/#/c/14801/ will be
packaged for the Essex release running on Ubuntu Precise?
Thank you,
George
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
Any idea when the fix in https://review.openstack.org/#/c/14801/ will be
packaged for the Essex release running on Ubuntu Precise?
Thank you,
George
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has been fixed in folsom.
** Changed in: horizon (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Internal server
This has been fixed in folsom.
** Changed in: horizon (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Internal server error when
It looks like the fix was released for Essex in Debian (as per
https://bugs.launchpad.net/horizon/+bug/1053488).
Any chance this can be packaged for Ubuntu Precise?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon
It looks like the fix was released for Essex in Debian (as per
https://bugs.launchpad.net/horizon/+bug/1053488).
Any chance this can be packaged for Ubuntu Precise?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm experiencing similar symptoms. After a little debugging, this is
what I think is happening:
As Admin user, in get_volumes_data of IndexView, 2 lists are created:
'volumes' and 'instances'. 'Volumes' appears to have a global scope,
but 'instances' is tenant-specific. The view attempts to
The same issue was reported in
https://bugs.launchpad.net/horizon/+bug/1053488
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Internal server error when accessing
I'm experiencing similar symptoms. After a little debugging, this is
what I think is happening:
As Admin user, in get_volumes_data of IndexView, 2 lists are created:
'volumes' and 'instances'. 'Volumes' appears to have a global scope,
but 'instances' is tenant-specific. The view attempts to
The same issue was reported in
https://bugs.launchpad.net/horizon/+bug/1053488
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Internal server error when accessing
Same problem here.
Instances and snapshots list can be retrieved with API and with command
line tools but horizon shows the Internal Server Error message.
VM snapshot from horizon is still working but when it comes to show the
snapshot page, the dashboard crashes.
--
You received this bug
Solved (at least in my case): I've got glance running on https and in
the horizon glance-client code the URI scheme was ignored.
I guess in the previos version of python-django-horizon package that
code was different...
Please find attached a (very trivial) patch for this issue.
** Patch added:
The attachment horizon-api-glance-uri-scheme-ignored.patch of this bug
report has been identified as being a patch. The ubuntu-reviewers team
has been subscribed to the bug report so that they can review the patch.
In the event that this is in fact not a patch you can resolve this
situation by
Same problem here.
Instances and snapshots list can be retrieved with API and with command
line tools but horizon shows the Internal Server Error message.
VM snapshot from horizon is still working but when it comes to show the
snapshot page, the dashboard crashes.
--
You received this bug
Solved (at least in my case): I've got glance running on https and in
the horizon glance-client code the URI scheme was ignored.
I guess in the previos version of python-django-horizon package that
code was different...
Please find attached a (very trivial) patch for this issue.
** Patch added:
The attachment horizon-api-glance-uri-scheme-ignored.patch of this bug
report has been identified as being a patch. The ubuntu-reviewers team
has been subscribed to the bug report so that they can review the patch.
In the event that this is in fact not a patch you can resolve this
situation by
** Package changed: nova (Ubuntu) = horizon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Internal server error when accessing nova/instances_and_volumes/
** Package changed: nova (Ubuntu) = horizon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Internal server error when accessing nova/instances_and_volumes/ via
horizon
To
I can confirm that this is as Jaroslav Henner describes. When you make a
new project and try to view it, if there is a disk attached from the
original project you get the internal server error, until you detach the
disks then you can view instances and volumes in the new project OK.
--
You
I can confirm that this is as Jaroslav Henner describes. When you make a
new project and try to view it, if there is a disk attached from the
original project you get the internal server error, until you detach the
disks then you can view instances and volumes in the new project OK.
--
You
Internal server error happens when some user has attached disk to some
server and another user (Admin) displays the instances and volumes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Internal server error happens when some user has attached disk to some
server and another user (Admin) displays the instances and volumes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/995079
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995079
Title:
I've rebuilt my environment. An important thing is that openstack-
dashboard package, on ubuntu, uses a configuration file in /etc
/openstack-dashboard/local_settings.py. In this file there is an
indication of what role the Dashboard will use.
OPENSTACK_HOST = 127.0.0.1
OPENSTACK_KEYSTONE_URL =
Same problem here! I was using the hastexo guide to configure keystone,
using a file catalog. So, I was having some problems. I dropped the
databases, rebuild all them, including the keystone. Now, I'm using the
guide from docs.openstack.org. I followed it step by step, creating the
tenant, all
I too had this issue, however it seems to be related to Keystone
endpoints. As a test I switched from using the MySQL DB for the
endpoints to using the template file.
Change /etc/keystone/keystone.conf:
[catalog]
#driver = keystone.catalog.backends.sql.Catalog
driver =
Same problem here! I was using the hastexo guide to configure keystone,
using a file catalog. So, I was having some problems. I dropped the
databases, rebuild all them, including the keystone. Now, I'm using the
guide from docs.openstack.org. I followed it step by step, creating the
tenant, all
I too had this issue, however it seems to be related to Keystone
endpoints. As a test I switched from using the MySQL DB for the
endpoints to using the template file.
Change /etc/keystone/keystone.conf:
[catalog]
#driver = keystone.catalog.backends.sql.Catalog
driver =
31 matches
Mail list logo
