Skip to content

Tweaks to Ubuntu Noble Upgrade#2098

Closed
technowhizz wants to merge 2 commits intostackhpc/2025.1from
update-noble-upgrade-docs
Closed

Tweaks to Ubuntu Noble Upgrade#2098
technowhizz wants to merge 2 commits intostackhpc/2025.1from
update-noble-upgrade-docs

Conversation

@technowhizz
Copy link
Copy Markdown
Contributor

No description provided.

@technowhizz technowhizz self-assigned this Jan 22, 2026
@technowhizz technowhizz requested a review from a team as a code owner January 22, 2026 14:51
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces several tweaks for the Ubuntu Noble upgrade process. The documentation for Pulp repository synchronization is updated with necessary arguments. In the Ansible playbook for the upgrade, a task to add Noble repository definitions is moved to a more logical position. A critical comment has been kept regarding a broken task in the same playbook, which ensures /tmp is mounted with exec, due to missing parameters that would cause the playbook to fail. A suggestion to fix this has been provided.

Moves the addition of new Ubuntu repositories to directly before the
call to do-release-upgrade. This ensures that any any failures after
that point are only due to the upgrade itself, and not due to missing
mounts (such as /tmp not being mounted).
@Alex-Welsh
Copy link
Copy Markdown
Member

@technowhizz are you planning on including all the changes from #1927?
If so, there are a few more tweaks to the docs that might be useful

@technowhizz
Copy link
Copy Markdown
Contributor Author

I didnt see that PR @Alex-Welsh

@technowhizz
Copy link
Copy Markdown
Contributor Author

happy to add to that PR if you think its better @Alex-Welsh

@Alex-Welsh
Copy link
Copy Markdown
Member

happy to add to that PR if you think its better @Alex-Welsh

I think the changes there are going to be stuck until someone from the stackhpc org re-creates the PR and this seems like a good opportunity to do it. If you could cherry-pick the changes and maybe squash them so it's not so many commits, that'd be great

@jovial
Copy link
Copy Markdown
Contributor

jovial commented Feb 6, 2026

We decide in the Infra meeting (5/02/2026) to maintain the docs in 2024.1 and to link to the 2024.1 docs on 2025.1 to avoid maintaining both.

@jovial
Copy link
Copy Markdown
Contributor

jovial commented Feb 6, 2026

@jovial jovial closed this Feb 6, 2026
auto-merge was automatically disabled February 6, 2026 17:42

Pull request was closed

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.

4 participants