cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pranav Saxena <pranav.sax...@citrix.com>
Subject RE: Review Board Patches Submission Not Working
Date Mon, 25 Jun 2012 09:23:58 GMT
Hi Ram,

Yes I am able to login through the UI (credentials are correct) . Also I observed when I try
to visit this URL - https://reviews.apache.org/account/login  , it is able to direct to the
correct page but for https://reviews.apache.org/api/json/accounts/login , it says the page
does not exist  and by default , (/api/json/accounts/login) is being passed into the python
script.

Regards,
Pranav

-----Original Message-----
From: Ram Chinta 
Sent: Monday, June 25, 2012 2:15 PM
To: Pranav Saxena
Subject: RE: Review Board Patches Submission Not Working

Are you able to login through the web using those same credentials (doublecheck the spelling)
? 

> -----Original Message-----
> From: Pranav Saxena [mailto:pranav.saxena@citrix.com]
> Sent: Monday, June 25, 2012 11:20 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Ewan Mellor
> Subject: Review Board Patches Submission Not Working
> 
> Hi ,
> 
> I was trying to submit a patch to the review board 
> (https://reviews.apache.org ) in the below mentioned way-
> 
> post-review   --username=pranavs --password=abcdefgh  --guess-summary CS-
> 13738:Some issue   --guess-description changed the Api
> 
> But I  was not successful as it threw a  HTTP 404 exception.  I tried 
> to do some work around like the modifying the login url in the python 
> script (postreview.py present here " 
> /usr/share/pyshared/rbtools/postreview.py"  )
> /*
> try:
>             print('Logging in with above credentials');
>             self.api_post('json/account/login', {                             // This
was  -
> api/json/accounts/login by default.
>                 'username': username,
>                 'password': password,
>             })
>         except APIError, e:
>             die("Unable to log in: %s" % e)
> 
> debug("Logged in.")
> */
> 
> Is anybody aware of this issue ? Is there some other workaround for 
> handling this issue ? Any sort of suggestions are most welcome.
> 
> Thanks & Regards,
> Pranav

Mime
View raw message