-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS#38323: Adding BZ#2151169 to known issues in 4.17 #81240
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
OSDOCS#38323: Adding BZ#2151169 to known issues in 4.17 #81240
Conversation
|
🤖 Tue Sep 03 14:40:24 - Prow CI generated the docs preview: |
|
@jherrman: 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. |
|
/label merge-review-needed |
|
@jherrman I am guessing this will not automatically cherrypick into 4.15-4.16, since it is going into a file called |
jeana-redhat
left a comment
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.
Change LGTM
/remove-label merge-review-in-progress
/remove-label merge-review-needed
|
@jeana-redhat: Those labels are not set on the issue: 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 kubernetes-sigs/prow repository. |
|
/cherrypick enterprise-4.16 |
|
@jeana-redhat: #81240 failed to apply on top of branch "enterprise-4.16": 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 kubernetes-sigs/prow repository. |
|
ok yeah this is not going to cherry pick by itself. Please open manual ones and tag for merge, you can link to this one to show that they are simply cherrypicks :) |
|
@jeana-redhat , right, I guess the cherry-pick was wishful thinking on my part >_< I'll go ahead and create the other PRs for 4.15 and 4.16. Thank you for trying anyway :-) |
|
@jeana-redhat , so turns out I messed up and placed the description into an incorrect section :-/ I pushed a commit to fix it into the branch, but it doesn't seem to be even registering, probably since the PR is closed. I guess I'll create one extra PR for this, too, then... :-) |
yeah, I think that's right - can't push if it's merged. |
Version(s):
4.15
Issue:
https://issues.redhat.com/browse/CNV-38323
Link to docs preview:
TBA
QE review:
Additional information:
A sort-of-clone for #78023 aimed to avoid cherry-pick conflicts