Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport 534 for 2.19: Make sure the absence of audit_entries table is not fatal #530

Open
wants to merge 1 commit into
base: stable
from

Conversation

@juruen
Copy link
Contributor

@juruen juruen commented Dec 6, 2019

This PR backports #534 to stable (2.19).

In order to avoid issues with the absence of the audit_entries table in certain scenarios:

  1. Do not try to backup the table if it doesn't exist
  2. Do not try to restore the schema if the snapshot doesn't contain one
@juruen juruen self-assigned this Dec 10, 2019
@juruen
Copy link
Contributor Author

@juruen juruen commented Dec 30, 2019

Closing this for now. We'll revisit it again when we gather more data about the actual impact of the issue it addresses.

@juruen juruen closed this Dec 30, 2019
@juruen juruen changed the title Make sure the absence of audit_entries table is not fatal Backport 534 for 2.19: Make sure the absence of audit_entries table is not fatal Jan 8, 2020
@juruen juruen reopened this Jan 8, 2020
@juruen juruen closed this Jan 8, 2020
@juruen juruen reopened this Jan 8, 2020
@juruen juruen changed the base branch from master to stable Jan 8, 2020
@juruen juruen force-pushed the juruen/2.19-audit-entries branch from 09e3a86 to ac41ce6 Jan 8, 2020
1 similar comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.