-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS#44672: 4.14 Added IPsec enabled node known issue to RNs #85079
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
Conversation
@dfitzmau: This pull request references Jira Issue OCPBUGS-44672, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
@dfitzmau: No Jira issue is referenced in the title of this pull request. In response to this:
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. |
🤖 Mon Nov 18 16:47:34 - Prow CI generated the docs preview: |
@dfitzmau: 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-sigs/prow repository. I understand the commands that are listed here. |
LGTM |
This LGTM, but it looks like it will require CM based on this bullet point from the manual: Adding or removing known or fixed issues in between releases (including z stream releases) to the release notes. Sometimes, a known issue might be missed by the documentation team for a z-stream because confirmation from an engineer on a private bug was not resolved; retrospective addition of this known issue after a z-stream release would require a CM. |
Thanks, @stevsmit . Yes, a CM is planned. I'm waiting on the engineer to approve the text before I sent the CM as people want to review the polished text before it is merged. I'll add a note to the description section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
Note: CM WILL BE SENT AFTER SME ACK.
Note: In error I used the engineering Jira number to represent the feature branch name. This number will not interfere with engineering PRs. OCPBUGS-44672 is the correct docs Jira for this issue.
Version(s):
4.14
Issue:
OCPBUGS-44672
Link to docs preview: