Can you make sure that your ~/.gitcookies file contains lines for chromium.googlesource and chromium-review.googlesource, and that both reference your chromium.org address?

Oh, and that you don't have a plain "googlesource.com" entry in the file -- those wildcard entries mess things up.

I had a single line entry starting from-

.googlesource.com	TRUE	/	TRUE 

Can you point me to how should I go about correcting this?

Remove that entry, navigate to chromium.googlesource.com/new-password, sign in with your @chromium account, and follow the instructions there.

Thanks, still keeping the issue open since don't think that "git cl upload" should upload the patch with the command failing on the command line.

The problem is that it has to do many consecutive operations: some api calls at the beginning, then an actual git push, then some more API calls at the end. It ensures that you have credentials at the start, but that doesn't mean that all of the API calls will succeed (if authenticating with the wrong account, especially, some of the post-push API calls might fail because they change state rather than just reading it). And if one of the post-push calls fails, well, the change has already been pushed. We can't un-upload the change, obviously.