fix(docs): correct playbook commands and minor inconsistencies in Ubuntu Noble upgrade guide#1927
fix(docs): correct playbook commands and minor inconsistencies in Ubuntu Noble upgrade guide#1927jasonrayne wants to merge 5 commits intostackhpc:stackhpc/2025.1from
Conversation
…ntu Noble upgrade guide - Fix incorrect ceph-enter-maintenance.yml usage where ceph-exit-maintenance.yml should be used - Add missing -e flags to pulp-repo-publish.yml and pulp-repo-promote-production.yml commands - Fix typo: "change" -> "chance" in storage section potential issues
There was a problem hiding this comment.
Code Review
This pull request provides important corrections to the Ubuntu Noble upgrade documentation. The changes correctly add missing flags to playbook commands, fix incorrect playbook usage for Ceph maintenance operations, and correct a typo. These fixes significantly improve the accuracy and reliability of the upgrade guide. I've added a couple of suggestions to improve the readability of the long shell commands by splitting them across multiple lines.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
lgtm but unfortunately our CI won't run correctly on repo forks. I'd be in favor of force-merging this though as it's such a simple docs change. @mnasiadka or @priteau are required for that |
|
@jasonrayne Thank you for these fixes! I am just confused by why you need to set
Can you double check your configuration settings? |
|
And on 2024.1 the variable is set as: |
|
@priteau I think the problem is if you are on Ubuntu Jammy and 2024.1 you it won't sync Noble packages as observed during the upgrade process. https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/2024.1/etc/kayobe/pulp.yml#L70 |
|
@priteau Jack is correct. My KC is synced with SKC |
|
@jasonrayne So, is it meant to be a fix for stackhpc/2024.1 branch? |
|
@seunghun1ee Seems like it might help avoid some confusion for users if we just apply this to both branches, honestly. Jack and I both defaulted to following the 2025.1 docs for the upgrade process, which would have been fine except for the fact that the Noble upgrade is ideally done before switching one's KC from 2024.1 to 2025.1, which creates a bit of an awkward crossover. |
Head branch was pushed to by a user without write access
6960bc5
|
Thanks - I've included these in #2139 as our CI doesn't run against external PRs currently :( |
-eflags topulp-repo-publish.ymlandpulp-repo-promote-production.ymlplaybook commands (without these flags, Noble repos are not promoted, causing apt failures on upgraded systems)ceph-enter-maintenance.ymlusage whereceph-exit-maintenance.ymlshould be used when taking hosts out of maintenance mode