Skip to content

Update disconnected update procedure for containerization - #5229

Open
aneta-petrova wants to merge 2 commits into
theforeman:masterfrom
aneta-petrova:foremanctl-updating-disco
Open

Update disconnected update procedure for containerization#5229
aneta-petrova wants to merge 2 commits into
theforeman:masterfrom
aneta-petrova:foremanctl-updating-disco

Conversation

@aneta-petrova

@aneta-petrova aneta-petrova commented Aug 20, 2026

Copy link
Copy Markdown
Member

What changes are you introducing?

Adding a procedure for updating a disconnected and containerized server.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

theforeman/foremanctl#621

https://redhat.atlassian.net/browse/SAT-48361

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

N/A

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 5.0/Katello 5.0
  • Foreman 3.19/Katello 4.21
  • Foreman 3.18/Katello 4.20 (Satellite 6.19; orcharhino 7.9)
  • Foreman 3.17/Katello 4.19
  • Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6, 7.7, and 7.8)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
  • We do not accept PRs for Foreman older than 3.14.

@aneta-petrova
aneta-petrova force-pushed the foremanctl-updating-disco branch 6 times, most recently from f26f7cb to 66f5d55 Compare August 21, 2026 09:32
Comment on lines +144 to +146
$ podman save $(podman images \
--format "{{.Repository}}:{{.Tag}}" | tr '\n' ' ') \
--output _My_Container_Images_.tar

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is failing for me due some of the images being untagged.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'll look into this. Concerning 😬

@aneta-petrova
aneta-petrova marked this pull request as ready for review August 21, 2026 10:10
@github-actions github-actions Bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Aug 21, 2026
@aneta-petrova
aneta-petrova force-pushed the foremanctl-updating-disco branch 2 times, most recently from b564f9b to 0846a27 Compare August 21, 2026 12:14
@aneta-petrova
aneta-petrova force-pushed the foremanctl-updating-disco branch from 0846a27 to b4e46d4 Compare August 21, 2026 12:16
Comment on lines +13 to +14
* Back up your disconnected {ProjectServer}.
For more information, see {AdministeringDocURL}backing-up-{project-context}[Backing up {Project}] in _{AdministeringDocTitle}_.

@aidenfine aidenfine Aug 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

One comment here, backup technically is not a requirement/pre req and upgrading can be done without it.

Maybe we could change the wording here or move it down to procedure?

For example in the foremanctl docs we used, "Consider backing up your Foreman environment before upgrade."

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Thanks! Applied here and in the connected update procedure.

You will be exporting the following repositories:
+
--
* `Red Hat Enterprise Linux 9 for x86_64 - BaseOS RPMs 9`

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@aidenfine There's one question that occurred to me: Here we are listing the three repositories required for the update, but the (already merged and containerized) procedure for updating a connected server doesn't include these repositories: Updating Satellite Server.

Is this an oversight? Should the connected update procedure also ask users to synchronize these repositories?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

That is a good point. Thanks for bringing this up, there is an updated PR on the foremanctl docs side, based on the new information on Y stream updates. I think that would be a good place to include this. I will add that into the PR.

The PR is here theforeman/foremanctl#787

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants