Skip to content
This repository has been archived by the owner on Nov 24, 2021. It is now read-only.

Fixes #16869 - only run post upgrade steps once #408

Merged
merged 1 commit into from
Oct 12, 2016

Conversation

jlsherrill
Copy link
Member

No description provided.

@@ -1,3 +1,7 @@
require 'fileutils'

STEP_DIRECTORY='/etc/foreman-installer/hooks/post/'
Copy link
Contributor

@stbenjam stbenjam Oct 11, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use a directory out of @kafo.config.app? Just in case we stop using this dir.

Or, what do you think about having a hidden directory/file like we do for applied migrations? Maybe right inside the hook directory itself, we could have a .ran file or something.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's fine since you do mkpath, but I think I'd prefer if it was a more obvious name

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't see anything in @kafo.config.app that was useful. Just references to:

/etc/foreman-installer/scenarios.d/katello-answers.yaml
and
/etc/foreman-installer/scenarios.d

i could parse /etc/foreman-installer/scenarios.d and go up one or something, but that might be just as risky as hardcoding.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine then, just making it more obvious what it is should be good enough. e.g., applied_hooks like we talked about on IRC

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

@@ -83,7 +104,7 @@ def fail_and_exit(message)
upgrade_step :restart_services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this an always run?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops! good catch

@stbenjam
Copy link
Contributor

stbenjam commented Oct 11, 2016

One more thought, can we add an installer option to run everything? I'd guess that'd be easier to tell a user, in case we need them to run the steps again

@ehelms
Copy link
Member

ehelms commented Oct 11, 2016

👍 to the general idea, this process could use some standardization similar to migrations but i think having a solution for current makes sense.

@jlsherrill
Copy link
Member Author

Added option to force --force-upgrade-steps

Copy link
Contributor

@stbenjam stbenjam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, ACK

@jlsherrill jlsherrill merged commit a3d0e51 into Katello:master Oct 12, 2016
@jlsherrill jlsherrill deleted the 16869 branch October 12, 2016 17:17
zjhuntin added a commit to zjhuntin/katello-installer that referenced this pull request Oct 30, 2018
…ello#408)

Adds one organization-validation test.

Added organization-specification test.

Creates test for repository search options creator.

Fixes issue with filter.

Fixed test issue.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants