Answers.Body: <p>The issue is confirmed and solved in 3.6.18</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-06-27T08:07:50.167Z
Answers.LastActivityDate: 2021-06-27T08:07:50.167Z
Answers.UserDisplayName: Matthias Redl-Mann
Body: <p>Why does the console command <code>./craft db/restore</code> expect the info table to exist and contain a row?
  There is also no option to ignore a non-existing info or empty info table.</p>
  <p>When we create automated restore procedures via Jenkins, this causes the restore to fail, because the DB is e.g. empty.</p>
  <p>Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-06-16T15:43:38.350Z
Comments.Text: Not a direct solution, but maybe a workaround would be to run [install/craft](https://craftcms.com/docs/3.x/console-commands.html#install) in your CD pipeline (would need to specify all optional parameters to avoid it needing input). This will create all missing tables, so the restore should work.
Comments.UserDisplayName: MoritzLost
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-06-17T18:02:48.803Z
Comments.Text: There's an issue for this here: https://github.com/craftcms/cms/issues/7028. I just tested it on the latest Craft and while you do get that message, the database is also properly restored, so it's more of a UI issue. Did you verify the database was properly restored on Jenkins? Going to go ahead and vote to close here, but feel free to add a comment on the existing GH issue.
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-06-18T07:08:45.770Z
Comments.Text: Hmm. We had the issue at a customer's staging installation yesterday, where the info table existed, but was empty, and the restore failed. Only after manually inserting the single row in the info table I was able to restore the full database.
Comments.UserDisplayName: Matthias Redl-Mann
Tags: <craft3><console><commands>
Title: Console command ./craft db/restore expects "info" table. Why?
ThreadText: # Console command ./craft db/restore expects "info" table. Why?
  
  (Asked by: username_0 on 2021-06-16)
  
  Why does the console command `./craft db/restore` expect the info table to exist and contain a row?
  There is also no option to ignore a non-existing info or empty info table.
  
  When we create automated restore procedures via Jenkins, this causes the restore to fail, because the DB is e.g. empty.
  
  Thanks!
  
  **Tags:** craft3, console, commands
  
  > **Comments:**
  > **username_1**: Not a direct solution, but maybe a workaround would be to run [install/craft](https://craftcms.com/docs/3.x/console-commands.html#install) in your CD pipeline (would need to specify all optional parameters to avoid it needing input). This will create all missing tables, so the restore should work.  
  > **username_2**: There's an issue for this here: https://github.com/craftcms/cms/issues/7028. I just tested it on the latest Craft and while you do get that message, the database is also properly restored, so it's more of a UI issue. Did you verify the database was properly restored on Jenkins? Going to go ahead and vote to close here, but feel free to add a comment on the existing GH issue.  
  > **username_0**: Hmm. We had the issue at a customer's staging installation yesterday, where the info table existed, but was empty, and the restore failed. Only after manually inserting the single row in the info table I was able to restore the full database.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-06-27. Score: 1 | Accepted answer
  
  The issue is confirmed and solved in 3.6.18
  
  
  ---
  
  