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

Fixes #32580 - remove pulp2 actions except for capsule sync #9353

Merged

Conversation

jjeffers
Copy link
Member

@jjeffers jjeffers commented May 11, 2021

This remove pulp2 action from the content view actions for publish, promote, etc.

In some cases the sub-actions planned included additional pulp2 specific planing options, which are also removed.

Open questions: 1. what have I missed (are there actions I am not considering in this PR wrt to content views)? 2. should the PR expand to include other pulp2 actions, such as for non-capsule operations?

@theforeman-bot
Copy link

Issues: #32580

@jjeffers
Copy link
Member Author

[test katello]

@jjeffers jjeffers force-pushed the 32580_remove_pulp2_from_content_view_actions branch from c4d316a to 4d2e6c9 Compare May 19, 2021 10:28
@jjeffers jjeffers changed the title [WIP] Fixes #32580 - remove some pulp2 actions from planning in CV actions Fixes #32580 - remove some pulp2 actions from planning in CV actions May 19, 2021
@jjeffers jjeffers changed the title Fixes #32580 - remove some pulp2 actions from planning in CV actions Fixes #32580 - remove pulp2 actions from planning in CV actions May 19, 2021
copy_output += copy_yum_content(new_repo, solve_dependencies,
content[:package_ids],
content[:errata_ids])

plan_action(Katello::Repository::MetadataGenerate, new_repo)
Copy link
Member Author

Choose a reason for hiding this comment

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

@jlsherrill Since we are removing the unit copy here for pulp2 - are the following metadata generation and indexing required?

Copy link
Member

Choose a reason for hiding this comment

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

It looks like today there are two branches in this code:

  • pulp3 with yum
  • everything else

and really the only thing supported with everything else is

  • pulp2 w/yum
  • pulp2 w/ deb
    Which means that pulp3 w/deb is not supported via inc update, and no other content types are (which is expected).

However, reading the pulp3 with yum branch, i'm not sure where the publications are getting created, or the content is getting indexed? Maybe i'm missing something...

Copy link
Member

Choose a reason for hiding this comment

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

I think what you've got is fine, let me file a card to investigate this

Copy link
Member

@jlsherrill jlsherrill left a comment

Choose a reason for hiding this comment

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

ACK

@jlsherrill
Copy link
Member

don't forget to squash!

@jjeffers
Copy link
Member Author

don't forget to squash!

They call me Sir Squashalot.

@jjeffers jjeffers force-pushed the 32580_remove_pulp2_from_content_view_actions branch from 489e716 to 4da16c4 Compare June 11, 2021 18:45
@jjeffers jjeffers merged commit a1e0372 into Katello:master Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants