IBM / watson-vehicle-damage-analyzer

A server and mobile app to send pictures of vehicle damage to IBM Watson Visual Recognition for classification
https://developer.ibm.com/patterns/classify-vehicle-damage-images/
Apache License 2.0
63 stars 46 forks source link

Not authorized for this request #47

Closed mananaya closed 6 years ago

mananaya commented 6 years ago

Am getting following error while trying to deploy using "Deploy to IBM Cloud" link. It is giving error that failed to create service wvda-visual-recognition. I have authorization to create standalone Watson Visual Recognition service, but when i use the "Deploy to IBM Cloud" it fails.

Preparing to start the job... Logging into Bluemix as user: "####@##.ibm.com" Preparing the build artifacts... Target: https://api.ng.bluemix.net Creating service instance wvda-visual-recognition in org ####@##.ibm.com / space #### as ####@##.ibm.com... FAILED Server error, status code: 502, error code: 10001, message: Service broker error: Failed to retrieve service details from catalog. Error : {"message":"Not authorized for this request.","code":403,"global_transaction_id":"gend-5113345195223265594"}

Finished: FAILED

stevemar commented 6 years ago

Can you confirm you are using a region that is not US South on IBM cloud?

mananaya commented 6 years ago

Hi Steve, Am using US South on IBM Cloud.

Thanks & regards, Manas R Nayak, ITIL® V3 Foundation, TOGAF® 9 Foundation Mobile # +91-98305-17018 Office # +91-33-711-97008 E-mail - mananaya@in.ibm.com

From: Steve Martinelli notifications@github.com To: IBM/watson-vehicle-damage-analyzer watson-vehicle-damage-analyzer@noreply.github.com Cc: mananaya mananaya@in.ibm.com, Author author@noreply.github.com Date: 05/28/2018 05:11 PM Subject: Re: [IBM/watson-vehicle-damage-analyzer] Not authorized for this request (#47)

Can you confirm you are using a region that is not US South on IBM cloud? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

scottdangelo commented 6 years ago

I am able to reproduce this issue. I believe it is due to breaking changes in the Visual Recognition API. I am working on a fix.

scottdangelo commented 6 years ago

This should work now. Please re-test.

mananaya commented 6 years ago

This works fine now, thanks for providing the fix.