[enterprise-4.13] OCPBUGS-19453: add admonition about node reboot
Version(s): 4.12, 4.13
Issue: https://issues.redhat.com/browse/OCPBUGS-19453
Link to docs preview: https://73711--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/certificates/replacing-default-ingress-certificate#replacing-default-ingress_replacing-default-ingress
QE review:
- [ ] QE has approved this change.
Additional information:
@jldohmann: This pull request references Jira Issue OCPBUGS-19453, which is invalid:
- expected Jira Issue OCPBUGS-19453 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Version(s): 4.12, 4.13
Issue: https://issues.redhat.com/browse/OCPBUGS-19453
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.
@sergiordlr could you PTAL for QE ack? this is related to #72185, but for pre-OCP 4.14 behavior where the node drains and reboots after updating certs. this PR adds a small note before the procedure about this
🤖 Mon Mar 25 20:32:11 - Prow CI generated the docs preview: https://73711--ocpdocs-pr.netlify.app
@jldohmann: This pull request references Jira Issue OCPBUGS-19453, which is invalid:
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
- expected Jira Issue OCPBUGS-19453 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
Version(s): 4.12, 4.13
Issue: https://issues.redhat.com/browse/OCPBUGS-19453
Link to docs preview: https://73711--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/certificates/replacing-default-ingress-certificate#replacing-default-ingress_replacing-default-ingress
QE review:
- [ ] QE has approved this change.
Additional information:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.
/label peer-review-in-progress
/label peer-review-done /remove-label peer-review-needed /remove-label peer-review-in-progress
@jldohmann: all tests passed!
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
LGTM
@jldohmann: Jira Issue OCPBUGS-19453 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.
In response to this:
Version(s): 4.12, 4.13
Issue: https://issues.redhat.com/browse/OCPBUGS-19453
Link to docs preview: https://73711--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/certificates/replacing-default-ingress-certificate#replacing-default-ingress_replacing-default-ingress
QE review:
- [x] QE has approved this change.
Additional information:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.
/cherrypick enterprise-4.12
@jldohmann: new pull request created: #73833
In response to this:
/cherrypick enterprise-4.12
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.