-
Notifications
You must be signed in to change notification settings - Fork 51
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
Minor enhancement required for OCP EUS-EUS upgrade #174
Comments
juliemathew
changed the title
Minor enhancements required for
Minor enhancements required for OCP EUS-EUS upgrade
Nov 10, 2022
juliemathew
changed the title
Minor enhancements required for OCP EUS-EUS upgrade
Minor enhancement required for OCP EUS-EUS upgrade
Nov 10, 2022
/assign @varad-ahirwadkar |
varad-ahirwadkar
pushed a commit
to varad-ahirwadkar/ocp4-playbooks
that referenced
this issue
Dec 23, 2022
…n#174) Signed-off-by: Varad Ahirwadkar <varad.ahirwadkar@ibm.com> A
varad-ahirwadkar
pushed a commit
to varad-ahirwadkar/ocp4-playbooks
that referenced
this issue
Dec 23, 2022
…n#174) Signed-off-by: Varad Ahirwadkar <varad.ahirwadkar@ibm.com>
varad-ahirwadkar
pushed a commit
to varad-ahirwadkar/ocp4-playbooks
that referenced
this issue
Jan 20, 2023
…n#174) Signed-off-by: Varad Ahirwadkar <varad.ahirwadkar@ibm.com>
varad-ahirwadkar
pushed a commit
to varad-ahirwadkar/ocp4-playbooks
that referenced
this issue
Feb 2, 2023
…n#174) Signed-off-by: Varad Ahirwadkar <varad.ahirwadkar@ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OCP EUS-EUS upgrade
Comment1:
In the 'ReadMe' https://github.com/ocp-power-automation/ocp4-playbooks/tree/main/playbooks/roles/ocp-upgrade#readme , under Section for 'Role Variables'
upgrade_version - Set to a specific version eg. 4.5.4
4.5.z is out of support. Here, can you give a more relevant example, say 4.11.12.
Comment 2:
Can you add some steps in the code, to verify if the worker nodes are actually paused, and not upgraded to intermediate version.
Check the version of kubelet, kubernetes etc on the worker nodes after intermediate upgrade. It should reflect the original version on the worker nodes, only the master nodes should get updated.
And check it once again after the final upgrade.
Note: Need to show the results in the output (log file), on running the playbook.
@varad-ahirwadkar
The text was updated successfully, but these errors were encountered: