fixes #14306 - fail without preupgrade run #224
Conversation
|
Needs Katello/katello#6010 |
|
Filed http://projects.theforeman.org/issues/15065 to track removal for 3.1 (or 3.X) |
We will ship a pre-upgrade script with 2.4. that needs to be run before upgrading to 3.0 GA. This should cause the yum transaction to fail out entirely, and let the user know they need to run the preupgrade before they can continue. Remove in 3.1.
|
Would this go in the 3.0 RPM or the 2.4 RPM? |
|
My idea was that this goes in 3.0, so when the user did |
|
I haven't tested yet, opened the PR to get some scratch builds built. |
|
|
It does not work like I expected, it only fails the katello RPM but the others upgrade just fine. Does the pre-upgrade script HAVE to be run against 2.4 first? @jlsherrill I'm not really sure how to solve the issue, I don't think there's a way to fail the entire transaction. |
|
@stbenjam no its not required to run, its more informational and gives the user a chance to handle conflicts themselves. |
|
Do you know if there was there some other reason for the downstream BZ then? |
|
@stbenjam i actually have no idea, i wasn't involved in that discussion |
|
Alright, thanks, I can't really think of a good way to do what they want. Maybe it's not really even needed. |
|
Closing this for now. |
We will ship a pre-upgrade script with 2.4. that needs to be run before
upgrading to 3.0 GA. This should cause the yum transaction to fail
out entirely, and let the user know they need to run the preupgrade
before they can continue. Remove in 3.1.