-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
OCPBUGS-29085: added shiftstack known issue to 4.15 release notes #71509
OCPBUGS-29085: added shiftstack known issue to 4.15 release notes #71509
Conversation
@sheriff-rh: This pull request references Jira Issue OCPBUGS-29085, 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. |
a264492
to
de9a842
Compare
🤖 Tue Feb 13 13:17:47 - Prow CI generated the docs preview: https://71509--ocpdocs-pr.netlify.app |
@@ -1619,6 +1619,8 @@ In the following tables, features are marked with the following statuses: | |||
|
|||
* When running a cluster with FIPS enabled, you might receive the following error when running an older version of the OpenShift CLI (`oc`) on a {op-system-base} 9 system: `FIPS mode is enabled, but the required OpenSSL backend is unavailable`. As a workaround, use the `oc` binary provided with the {product-title} cluster. (link:https://issues.redhat.com/browse/OCPBUGS-23386[*OCPBUGS-23386*]) | |||
|
|||
* In {rh-openstack-first} on {product-version} environments, `IngressController` objects configured with `endpointPublishingStrategy.type: LoadBalancerService` will fail to configure IPv6 correctly. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2263550[*BZ#2263550*], link:https://bugzilla.redhat.com/show_bug.cgi?id=2263552[*BZ#2263552*]) |
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.
It's not that it will not configure IPv6 correctly. It will fail on IPv6-first deployments.
Also it's the other way around - OpenShift runs on top of OpenStack. How about:
In {product-version} with IPv6 networking running on {rh-openstack-first} environments, `IngressController` objects configured with `endpointPublishingStrategy.type=LoadBalancerService` will not function correctly. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2263550[*BZ#2263550*], link:https://bugzilla.redhat.com/show_bug.cgi?id=2263552[*BZ#2263552*])
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.
Thanks! I copied it word for word to the release notes 👍
de9a842
to
4f7fe14
Compare
@@ -1694,6 +1694,8 @@ In the following tables, features are marked with the following statuses: | |||
|
|||
* When running a cluster with FIPS enabled, you might receive the following error when running an older version of the OpenShift CLI (`oc`) on a {op-system-base} 9 system: `FIPS mode is enabled, but the required OpenSSL backend is unavailable`. As a workaround, use the `oc` binary provided with the {product-title} cluster. (link:https://issues.redhat.com/browse/OCPBUGS-23386[*OCPBUGS-23386*]) | |||
|
|||
* In {product-version} with IPv6 networking running on {rh-openstack-first} environments, `IngressController` objects configured with `endpointPublishingStrategy.type=LoadBalancerService` will not function correctly. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2263550[*BZ#2263550*], link:https://bugzilla.redhat.com/show_bug.cgi?id=2263552[*BZ#2263552*]) |
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.
Looks good. I couldn't figure on how to get a noun after endpoint...
. I think we are ok though because you have objects configured with. The only thing you could do is maybe say endpoint...
YAML configuration or maybe install configuration or deployment config.
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.
That's great, thanks. I couldn't come up with a solution either! I'll make the change.
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.
question/suggestion
4f7fe14
to
bfff7e4
Compare
/retest |
@sheriff-rh: 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. |
Merging. |
@sheriff-rh: Jira Issue OCPBUGS-29085: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-29085 has been moved to the MODIFIED state. 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. |
Version(s):
4.15
Issue:
https://issues.redhat.com/browse/OCPBUGS-29085
Link to docs preview (VPN required):
Known Issues (fourth one down)