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

Run cpdb --update #139

Merged
merged 1 commit into from
Jan 13, 2020
Merged

Run cpdb --update #139

merged 1 commit into from
Jan 13, 2020

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Nov 29, 2019

cpdb --create creates the database but --update updates it to the latest schema. The installer can also remove the marker file /var/lib/candlepin/cpdb_update_done to trigger a schema migration.

@ehelms
Copy link
Member

ehelms commented Dec 6, 2019

This is a strange failure :/ I'm OK merging this despite this plaguing failure.

@ekohl
Copy link
Member Author

ekohl commented Dec 6, 2019

Given the intermittent failures I'm leaning to holding this off until our Katello nightly pipeline is green again. Otherwise we'll just keep stacking potential failures.

@ekohl
Copy link
Member Author

ekohl commented Jan 13, 2020

Updated to now call both.

cpdb --create creates the database but --update updates it to the latest
schema. The installer can also remove the marker file
/var/lib/candlepin/cpdb_update_done to trigger a schema migration.
@ehelms ehelms merged commit fadb503 into theforeman:master Jan 13, 2020
@ekohl ekohl deleted the update-db branch January 13, 2020 19:48
@ekohl
Copy link
Member Author

ekohl commented Feb 12, 2020

Not sure if this really is breaking, but I consider this major enough for a major version bump and don't want to pull this into a stable branch.

@ekohl ekohl linked an issue Apr 27, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exec 'cpdb' should be executed after all updates?
3 participants