Restore process fails

[dbinetti]

What command did you execute?

staging restore-from production

What did you expect to happen?

Overwrite staging with most recent production backup.

What actually happened?

Resetting postgresql-flat-55107... done
Starting restore of https://xfrtu.s3.amazonaws.com/XXXXXXX/2018-12-19T13%3A11%3A44Z/XXXXXXX?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=XXXXXXXXXXXXXXXX%2F20181219%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20181219T131537Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=XXXXXX to postgresql-flat-55107... !
 ▸    Expected response to be successful, got 500

Some information about your installation

• What's your operating system? MacOS 10.14.2

• What's the output of which development, which staging, which production? Parity has had multiple installation channels, and it's not uncommon for an old version to be somewhere else in your path.

  (barberscore-api) bash-3.2$ which staging
  /usr/local/bin/staging
  (barberscore-api) bash-3.2$ which production
  /usr/local/bin/production

• If installed via Homebrew, what does brew list parity output?

  (barberscore-api) bash-3.2$ brew list parity
  /usr/local/Cellar/parity/3.0.1/bin/development
  /usr/local/Cellar/parity/3.0.1/bin/pr_app
  /usr/local/Cellar/parity/3.0.1/bin/production
  /usr/local/Cellar/parity/3.0.1/bin/staging
  /usr/local/Cellar/parity/3.0.1/lib/parity/ (5 files)
  /usr/local/Cellar/parity/3.0.1/lib/parity.rb

• If installed via Rubygems, what's the gem version? N/A

Additional Context

I upgraded from Postgresql 10 -> 11 and then tried to run the copy from production to backup, which failed. Worked prior to the upgrade.

Also, I was able to successfully upgrade my development environment; only staging is failing at this point.

[geoffharcourt]

Hi, a 500 error means there was a server error. I'm able to perform this operation at the moment from production to staging on one of my apps. Can you still produce the issue?

Heroku had an incident related to database provisioning this morning, so if you're able to restore now that might explain why you had trouble.

Also: Heroku doesn't support PG 11 yet, and it's possible that the Heroku CLI leverages your local psql or pg_restore to perform some of the operations and is doing something not permitted or expected. That you can pull data down to your development machine but can't push it up to Heroku might point to that as a cause.

[dbinetti]

Yep, was transitory! Thanks...