Bug 1012046

Summary: internal server error when glanceclient called from nova or horizon
Product: Red Hat OpenStack Reporter: Dan Yocum <dyocum>
Component: python-glanceclientAssignee: Jakub Ruzicka <jruzicka>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.0CC: apevec, dyocum, eglynn, fpercoco, hateya, jruzicka, yeylon
Target Milestone: ---   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-08 15:00:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
stack trace from nova api.log
none
controller.pp puppet node file none

Description Dan Yocum 2013-09-25 15:27:54 UTC 
Description of problem:

When trying to launch a VM or perform a 'nova image-list' an internal server error is produced (500).  The trace from api.log is attached.

Version-Release number of selected component (if applicable):

rhel-x86_64-server-6-ost-3

How reproducible:



Steps to Reproduce:
1. Fresh RHEL 6.4 install, updated.
2. puppet install of RHOSv3 using stackforge modules including the openstack module - controller.pp node file is attached.
3.

Actual results:

see attached trace dump


Expected results:

no error 500

Additional info:
Comment 1 Dan Yocum 2013-09-25 15:28:39 UTC 
Created attachment 802923 [details]
stack trace from nova api.log
Comment 2 Dan Yocum 2013-09-25 15:29:56 UTC 
Created attachment 802925 [details]
controller.pp puppet node file
Comment 4 Jakub Ruzicka 2013-11-07 15:51:08 UTC 
How did you get these stackforge modules? Only those from packstack-modules-puppet package are supported AFAIK.

Please provide details on howto reproduce this including obtaining the modules and installing them.
Comment 5 Dan Yocum 2013-11-07 18:55:27 UTC 
I had installed RHOSv2, Folsom, removed all the Folsom packages, then installed RHOSv3, Grizzly, and these errors were showing up.  

Only after I wiped the system clean - rekicked from scratch - did the errors go away.  

That's not very encouraging if anyone is every planning on trying to do an upgrade from RHOSv2 to RHOSv3.  Something was getting left around from the Folsom install.

The stackforge puppet modules we're using are from github...
Comment 6 Jakub Ruzicka 2013-11-08 15:00:04 UTC 
OK, so this was an environment problem rather than client bug.

I don't think this scenario (wiping Folsom, installing Grizzly) is very relevant, especially now with Havana out.

Also, I think you should use RHOS puppet modules when reporting a bug against RHOS.
Comment 7 Dan Yocum 2013-11-08 17:45:59 UTC 
It is troubling that an 'yum remove <all openstack related rpms>' left bits around that messed up the glanceclient from Grizzly, but you're right, the Folsom->Grizzly upgrade path is less relevant now that we're getting farther along in time.  Based on this, you can safely close this ticket as NOTABUG or whatever.