Recovery message and actions are inconsistent

Description

Tested with Everest v0.0.0-e74de40 version.

Create a mysql database, take scheduled backup and restore using PITR. When the restore is started, the restore message “We are recovering your database…” does not appear and all the db actions are enabled

The message appears briefly when the Restore Status changes to Restoring and then disappears after few seconds. Db actions get disabled during the message and then get enabled again.

A video of the above behavior is attached in the slack message https://perconacorp.slack.com/archives/C0545J2BEJX/p1720607822783919?thread_ts=1720530706.489659&cid=C0545J2BEJX

Environment

None

Attachments

3
  • 22 Jul 2024, 04:05 PM
  • 11 Jul 2024, 06:18 AM
  • 11 Jul 2024, 06:18 AM

Activity

Show:

Manish Chawla August 9, 2024 at 11:28 AM

Tested with Everest v1.1.0-rc2 version and did not observe this issue.

Diana Birsan July 22, 2024 at 4:05 PM

This works correctly from the UI point of view; the UI displays an alert when the DB is in the 'restoring' state. However, after a restore is started, the API call returns the DB with first 'restoring' state and then 'stopping', which causes the alert to temporarily disappear

Unresolved

Details

Assignee

Reporter

Regression Issue

Yes

Fix versions

Affects versions

Priority

Smart Checklist

Created July 11, 2024 at 6:18 AM
Updated August 12, 2024 at 12:28 PM