bin/storage status shows both patches as applied.

Yes I found T4463 while I was searching for the issue. Here's log of issues I faced during upgrade;

I ran upgrade on very old install of phabricator, hadn't been updated for as long as 9 months. I ran into few issues during upgrade, but eventually managed to complete storage upgrade.

I have updated auth_providerconfig in phabricator_auth.auth_providerconfig table to something else and added new Google provider from web interface. Not sure if this is the correct way but it worked.

Storage upgrade executed with following errors;

Yes, that's what I wanted to state, missed it completely.

My bad, but the add credentials screen is a bit confusing when it asks for username (required field), I had added some values to the username and password field while importing plain text ssh key.

Thanks for quick response, but I do not have passphrase set for any keys added to my account. I have generated the keys without opting for a passphrase.

While trying to pull the remote repo from command line ./bin/repository pull X, it's asking for passphrase. I do not have passphrase set to any of my keys.

Resolved post phab install update.

Yes, I have added credentials using the screen you suggested. I have my personal key added as well as the phd user's key added. Both public keys are also added on my github account.

Killed it, there was just one. Hope it does not affect my install. Did a fresh clone from local and pushed changes. Everything seems to be stable now.

from htop logs;

I have restarted phabricator daemons, php5-fpm and nginx, but the cpu usage is still very high.

Thanks for clearing it out. Clone worked for me either way. We will follow the normal SSH URI.

I get the clone link as:

git clone ssh://git@phabricator.example.com/diffusion/HW/hello-world.git

I don't have the error trace, but will check httpd logs and report the trace if I find any.

+1