Skip to content

Add Katello 4.19 structured APT for deb content upgrade docs #4452

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.

Sign up for GitHub

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
+15 −2
Draft

Add Katello 4.19 structured APT for deb content upgrade docs #4452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions guides/doc-Release_Notes/topics/katello.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,25 @@
[id="katello-headline-features"]
== Headline features

There are no headline features with Katello {KatelloVersion}.
=== Structured APT for deb content

With {KatelloVersion} all deb content will start using "structured APT" mode.
This means that deb content published in APT repos on Katello, will no longer publish Release files under the `dists/default/` path.
Instead, all APT repository publications will exclusively use the same repository structure (releases/distributions and components) as the remote upstream repositories they are synced from.


[id="katello-upgrade-warnings"]
== Upgrade warnings

There are no upgrade warnings with Katello {KatelloVersion}.
=== Strucutred APT migration for deb content

For all users with deb type content, we recommend migrating that content to "structured APT" enabled mode *before* upgrading to {KatelloVersion}.
Instructions for how to do this can be found here: https://docs.theforeman.org/3.16/Managing_Content/index-katello.html#enabling-structured-apt-content

If you do not migrate your deb content before upgrading, it will be automatically migrated by the foreman-installer run after upgrading.
However, if this automatic migration run is not fully successfull, or omitted, some of your deb type content may be left in an inconsistent state.
This is why we recommend migrating before the upgrade, at which point you can easily re-run the migration or get help in case there is an issue.


[id="katello-deprecations"]
== Deprecations
Expand Down