Wire log just shows some random hex numbers. I thought they may be bytes of image being uploaded. I observed stack screen but it does not show any activity when uploading with jclouds but when I do direct upload through horizon it enlists some calls to various python clients (/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:909 /opt/stack/glance/glance/common/client.py:411)
After waiting for half an hour the status of image is still queued and not active On Fri, Apr 11, 2014 at 8:06 PM, Everett Toews <[email protected]>wrote: > On Apr 11, 2014, at 9:11 AM, Shital Patil <[email protected]> wrote: > > > It doe not throw exception when I call upload/create image API, the > call returns with image ID but when I log in to horizon the status of imge > over there is queuing(image is being queued) and it never shows active > status. However when I upload image through horizon dashboard with create > image tab , it successfully gets uploaded. Why there is problem while > uploading through API then? Can it be problem with my devstack setup? > > That's definitely a possibility. 2 things. > > 1. You'll want to enable Logging [1] for jclouds so you can see exactly > how it's communicating with Glance. > > 2. You'll want to go into your DevStack screen session (screen -r stack) > and look at the screens that start with "g-". Those are the Glance > services. The output is effectively their logs. > > Between the jclouds logs and the Glance logs hopefully you'll be able to > work out what's wrong. See what the difference is between when you use > Horizon and when you use jclouds. > > HTH, > Everett > > [1] http://jclouds.apache.org/reference/logging/
