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 remove-pulp2 command after upgrading to 4.0 #1326

Merged
merged 1 commit into from Mar 31, 2021

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Mar 30, 2021

Given users are expected to run this at some point, and as we progress through the current Katello versions and those coming after,

@evgeni
Copy link
Member

evgeni commented Mar 30, 2021

Should this also run for luna? IMHO yes.

And currently this will run remove after the upgrade to 3.18, which means it will purge katello (as it depends on pulp-selinux in 3.18). I guess it should check whether the intermediate/final version is 4.0 instead?

@ehelms ehelms force-pushed the run-remove-pulp2 branch 2 times, most recently from b4bf3b4 to 9318183 Compare March 30, 2021 11:53
@ehelms
Copy link
Member Author

ehelms commented Mar 30, 2021

Should this also run for luna? IMHO yes.

Done

@@ -20,3 +20,11 @@
scenario_version: "{{ forklift_upgrade_version_final }}"
- foreman_server_repositories
- foreman_installer
post_tasks:
- name: Run remove Pulp 2
command: foreman-maintain content remove-pulp2
Copy link
Contributor

Choose a reason for hiding this comment

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

i think this will stop and ask if you want to proceed, in retrospect we should have added a --force option

Maybe you force some input into it?

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

Should it be shell: yes | foreman-maintain content remove-pulp2 while we file an issue for a --yes or --force? (I feel like --force may be too strong for just a "do not ask for confirmation").

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, I too hate it when --force means --assume-yes (or similar).

Copy link
Contributor

Choose a reason for hiding this comment

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

yes, i'd prefer --assume-yes, more meant a general option

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

We may need to revisit this if we start to add content migration tests but if this gets our pipelines unstuck then I'm all for it.

@@ -21,3 +21,11 @@
- foreman_server_repositories
- role: foreman_installer
foreman_installer_skip_installer: "{{ true if forklift_upgrade_version_start == forklift_upgrade_version_intermediate else false }}"
post_tasks:
- name: Run remove Pulp 2
shell: yes | foreman-maintain content remove-pulp2
Copy link
Member

Choose a reason for hiding this comment

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

I've known about this pattern for a long time but I think this is the first time I see it in action :)

@evgeni evgeni merged commit 5acc851 into theforeman:master Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants