When running the upgrade script, the following appears (excerpted):
Verifying database schemata... Found no adjustments for schemata. Target Error phabricator_repository.repository_uri Missing SCHEMATA ERRORS The schemata have errors (detailed above) which the adjustment workflow can not fix. If you are not developing Phabricator itself, report this issue to the upstream.
| Restricted Differential Revision | Restricted Diffusion Commit | |
| Restricted Differential Revision | Restricted Diffusion Commit |
Versions:
phabricator fbfe7304521464151986aee99d71fa07b20e0768 (Sun, Apr 17)
arcanist a2ab38df78a9d111459fab8d0d63e74d811edf29 (Sat, Apr 16)
phutil 1ea69b48e36d8411c329559b593772ae51a2e6f9 (Fri, Apr 15)
I get the same issue after upgrading:
| Component | From | To |
| libphutil | 7a18444 | 1ea69b4 |
| arcanist | 737f5c0 | a2ab38d |
| phabricator | fad9e04 | fbfe730 |
Transcript:
Storage is up to date. Use 'storage status' for details. Verifying database schemata... Found no adjustments for schemata. Target Error phabricator_repository.repository_uri Missing SCHEMATA ERRORS The schemata have errors (detailed above) which the adjustment workflow can not fix. If you are not developing Phabricator itself, report this issue to the upstream. If you are developing Phabricator, these errors usually indicate that your schema specifications do not agree with the schemata your code actually builds.
Sorry everyone -- we don't actually read or write this table yet so I didn't add the schema, but the fact that bin/storage adjust would complain slipped my mind. D15744 will fix it and make sure bin/storage adjust is run as part of the test suite.
If you aren't already aware of it, an alternative we made available a while ago is that you can track stable instead of master:
https://secure.phabricator.com/book/phabricator/article/upgrading/#stable-branch
It runs about a week behind master, so it's not too out-of-date, but usually avoids getting hit by obvious developer error like this. While I think these are fairly rare even in master, they do happen occasionally and they're more likely in the next couple of weeks as we're shuffling a lot of infrastructure around while pursuing T10751.
Hmm,
I get a new error when i run ./bin/storage upgrade:
phabricator_repository.repository_uri.credentialPHID
Before running storage upgrades, you should take down the Phabricator web
interface and stop any running Phabricator daemons (you can disable this
warning with --force).
Are you ready to continue? [y/N] y
Storage is up to date. Use 'storage status' for details.
Verifying database schemata...
Found no adjustments for schemata.
Target Error
phabricator_repository.repository_uri.credentialPHID Missing
SCHEMATA ERRORS
The schemata have errors (detailed above) which the adjustment workflow can
not fix.
If you are not developing Phabricator itself, report this issue to the
upstream.
If you are developing Phabricator, these errors usually indicate that your
schema specifications do not agree with the schemata your code actually
builds.