Re: [Openstack] Horizon - Internal Server Error when hitting /nova/instances_and_volumes/
On May 8, 2013, at 2:48 PM, Gabriel Hurley wrote: > If you have "Instances & Volumes" then you're not running Grizzly Horizon. > Those two were split apart in Grizzly. Prior to Grizzly the Volume Service > was required. In Grizzly Horizon it's not. > > As such you have two choices: run Cinder like you are but don't use it, or > upgrade so you're actually running Grizzly Horizon and don't run Cinder. Yep, I just figured that out. I was running Horizon in a VM and hadn't added the grizzly.list to /etc/apt/sources.list.d/. When I installed, it grabbed the older version of Horizon. That caused a few headaches. :) Thanks for your input! If I hadn't figured it out, your suggestion would have put me on the right track. Daniel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Horizon - Internal Server Error when hitting /nova/instances_and_volumes/
If you have "Instances & Volumes" then you're not running Grizzly Horizon. Those two were split apart in Grizzly. Prior to Grizzly the Volume Service was required. In Grizzly Horizon it's not. As such you have two choices: run Cinder like you are but don't use it, or upgrade so you're actually running Grizzly Horizon and don't run Cinder. All the best, - Gabriel > -Original Message- > From: Openstack [mailto:openstack- > bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of > Daniel Ellison > Sent: Tuesday, May 07, 2013 11:01 AM > To: OpenStack Users > Subject: [Openstack] Horizon - Internal Server Error when hitting > /nova/instances_and_volumes/ > > As the subject says, I'm having issues getting at "Instances & Volumes" (also > "Images & Snapshots") in Horizon. I'm running grizzly on precise. Everything > else works fine; the entire "Admin" tab works as expected. The "Overview" > and "Access & Security" also work fine. > > Is there any way to see what calls are being made from horizon to nova? I > debugged some previous issues by using --debug on some python client > calls. But I don't think there's an equivalent in this case. > > The Apache log on my horizon machine (a VM under nova) shows the 500 > error, then has a bunch of 404s when trying to retrieve media and other > resources, e.g. /nova/images_and_snapshots/dashboard/css/style.css. For > all other calls there are no 404 errors (and no 500 errors, needless to say). > > I'm only using Nova, Keystone and Glance for the moment. So no Cinder to > consider, and no attached volumes. Does any of this sound familiar to > anyone? > > Thanks, > Daniel > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Horizon - Internal Server Error when hitting /nova/instances_and_volumes/
On May 8, 2013, at 7:27 AM, Daniel Ellison wrote: > On May 7, 2013, at 2:01 PM, Daniel Ellison wrote: > I think I know the source of the problem. I first had to add a logging > section for "openstack_dashboard" in local_settings.py despite the fact that > there was already a section for "horizon". Then I was able to see the > exception that was happening: > >ServiceCatalogException: Invalid service catalog service: volume > > I don't have Cinder installed, but it looks like Horizon is expecting it to > be there. I don't have a volume endpoint, as far as I can tell. "nova > endpoints" only lists glance nova, ec2 and keystone. > > Is there a way to disable this behaviour in Horizon? Or is there a setting > I'm missing? I ended up installing Cinder anyway, and now I can get at both instances_and_volumes and images_and_snapshots. I didn't want to have to install something I'm not planning on using, but it was the only way I could think of to get past the sticking point. The reason I'm not using Cinder is that I created a 6TB LVM volume from two 3TB drives on my server long before I started testing OpenStack, and resizing it now would be a real pain. I don't have easy physical access to the machine itself, so making changes that big is dangerous at best. This whole OpenStack install is for a proof-of-concept anyway, so I can live without Cinder. Or at least, I thought I could :) Daniel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Horizon - Internal Server Error when hitting /nova/instances_and_volumes/
On May 7, 2013, at 2:01 PM, Daniel Ellison wrote: > As the subject says, I'm having issues getting at "Instances & Volumes" (also > "Images & Snapshots") in Horizon. I'm running grizzly on precise. Everything > else works fine; the entire "Admin" tab works as expected. The "Overview" and > "Access & Security" also work fine. > > Is there any way to see what calls are being made from horizon to nova? I > debugged some previous issues by using --debug on some python client calls. > But I don't think there's an equivalent in this case. > > The Apache log on my horizon machine (a VM under nova) shows the 500 error, > then has a bunch of 404s when trying to retrieve media and other resources, > e.g. /nova/images_and_snapshots/dashboard/css/style.css. For all other calls > there are no 404 errors (and no 500 errors, needless to say). > > I'm only using Nova, Keystone and Glance for the moment. So no Cinder to > consider, and no attached volumes. Does any of this sound familiar to anyone? I think I know the source of the problem. I first had to add a logging section for "openstack_dashboard" in local_settings.py despite the fact that there was already a section for "horizon". Then I was able to see the exception that was happening: ServiceCatalogException: Invalid service catalog service: volume I don't have Cinder installed, but it looks like Horizon is expecting it to be there. I don't have a volume endpoint, as far as I can tell. "nova endpoints" only lists glance nova, ec2 and keystone. Is there a way to disable this behaviour in Horizon? Or is there a setting I'm missing? Thanks, Daniel ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
