Jay, thanks for your feedback and we will work on it. Thanks --jyh
> -----Original Message----- > From: openstack-bounces+yunhong.jiang=intel....@lists.launchpad.net > [mailto:openstack-bounces+yunhong.jiang=intel....@lists.launchpad.net] On > Behalf Of Jay Pipes > Sent: Thursday, August 02, 2012 12:16 AM > To: openstack@lists.launchpad.net > Subject: Re: [Openstack] python novaclient's response when extension is > disabled > > On 08/01/2012 10:10 AM, Jiang, Yunhong wrote: > > Currently, if an extension is disabled, there will be no clear information > > like > "extension is not support", instead, it will return " ERROR: n/a (HTTP 404)", > like > followed output in my devstack. > > > > yjiang5@yjiang5-linux1:~/work/openstack/devstack$ nova hypervisor-list > > ERROR: n/a (HTTP 404) > > > > I'm not sure if this is the expected response. Per my understanding, python > nova-client should tell user clearly that the extension is not supported. > This can > be achieved by checking the " v2/extensions" API, either at nova-client start > stage, or at the time that the extension get "HTTP 404" error. > > > > Is my understand correct? If yes, we can create a blueprint and provide > patches. > > I don't see anything wrong with your logic. I'd fully support you putting > together > patches that would produce a nice error message like "Sorry, that extension is > not available" instead of the 404 error. > > Best, > -jay > > _______________________________________________ > 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
