Skip to content

OCPBUGS-49933:adds link to KI and updates attribute #88908

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 20, 2025
Merged

OCPBUGS-49933:adds link to KI and updates attribute #88908

merged 1 commit into from
Feb 20, 2025

Conversation

JoeAldinger
Copy link
Contributor

@JoeAldinger JoeAldinger commented Feb 19, 2025 •
edited
Loading

Version(s):

Issue:
Fixes attribute and adds xref to RN.

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Feb 19, 2025
@openshift-ci-robot
Copy link

@JoeAldinger: This pull request references Jira Issue OCPBUGS-49933, 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-49933 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):

Issue:

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.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 19, 2025
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 19, 2025
@JoeAldinger JoeAldinger added this to the Planned for 4.18 GA milestone Feb 19, 2025
abhat
abhat reviewed Feb 19, 2025
View reviewed changes
release_notes/ocp-4-18-release-notes.adoc Outdated
* A regression in the behaviour of `libreswan` caused some nodes with IPsec enabled to lose communication with pods on other nodes in the same cluster. To resolve this issue, consider disabling IPsec for your cluster. (link:https://issues.redhat.com/browse/OCPBUGS-43713[*OCPBUGS-43713*])

* There is a known issue with {op-base-system} 8 worker nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` As a workaround, users should migrate worker nodes from `cgroupv1` to `cgroupv2`. (link:https://issues.redhat.com/browse/OCPBUGS-49933[*OCPBUGS-49933*])
* There is a known issue with {op-system-base} 8 worker nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` As a workaround, users must reconfigure their nodes from `cgroupv1` to `cgroupv2` before creating a user-defined network. For more information, see xref:../nodes/clusters/nodes-cluster-cgroups-2.adoc#nodes-cluster-cgroups-2[Configuring Linux cgroup]. (link:https://issues.redhat.com/browse/OCPBUGS-49933[*OCPBUGS-49933*])
Copy link

@abhat abhat Feb 19, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as #88906. We should not limit the surface area of this bug to only rhel8 nodes. this applies to any node using cgroupsv1. cc @npinaeva.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asood-rh here is the message you asked about in the other PR #88906

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Feb 19, 2025 •
edited
Loading

🤖 Thu Feb 20 21:34:11 - Prow CI generated the docs preview:

https://88908--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html

asood-rh
asood-rh reviewed Feb 20, 2025
View reviewed changes
release_notes/ocp-4-18-release-notes.adoc Outdated
* A regression in the behaviour of `libreswan` caused some nodes with IPsec enabled to lose communication with pods on other nodes in the same cluster. To resolve this issue, consider disabling IPsec for your cluster. (link:https://issues.redhat.com/browse/OCPBUGS-43713[*OCPBUGS-43713*])

* There is a known issue with {op-base-system} 8 worker nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` As a workaround, users should migrate worker nodes from `cgroupv1` to `cgroupv2`. (link:https://issues.redhat.com/browse/OCPBUGS-49933[*OCPBUGS-49933*])
* There is a known issue with nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` As a workaround, users must reconfigure their nodes from `cgroupv1` to `cgroupv2` before creating a user-defined network. For more information, see xref:../nodes/clusters/nodes-cluster-cgroups-2.adoc#nodes-cluster-cgroups-2[Configuring Linux cgroup]. (link:https://issues.redhat.com/browse/OCPBUGS-49933[*OCPBUGS-49933*])
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

5m16s       Warning   UDNKubeletProbesNotSupported          node/ip-10-0-51-120.us-east-2.compute.internal                     Kubelet probes for UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JoeAldinger There is an event generated of type warning.

Copy link

@anuragthehatter anuragthehatter Feb 20, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: s/cgroupv1/Cgroup v1 as per convention. Most conventions use capital C as well but leave it up to you but space is recommended. Thanks @JoeAldinger

asood-rh
asood-rh reviewed Feb 20, 2025
View reviewed changes
release_notes/ocp-4-18-release-notes.adoc Outdated
* A regression in the behaviour of `libreswan` caused some nodes with IPsec enabled to lose communication with pods on other nodes in the same cluster. To resolve this issue, consider disabling IPsec for your cluster. (link:https://issues.redhat.com/browse/OCPBUGS-43713[*OCPBUGS-43713*])

* There is a known issue with {op-base-system} 8 worker nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` As a workaround, users should migrate worker nodes from `cgroupv1` to `cgroupv2`. (link:https://issues.redhat.com/browse/OCPBUGS-49933[*OCPBUGS-49933*])
* There is a known issue with nodes that use `cgroupv1` Linux Control Groups (cgroup). The following is an example of the error message displayed for impacted nodes: `UDN are not supported on the node ip-10-0-51-120.us-east-2.compute.internal as it uses cgroup v1.` An event of type `Warning` triggers a `UDNKubeletProbesNotSupported` event for impacted nodes. As a workaround, users must reconfigure their nodes from `cgroupv1` to `cgroupv2` before creating a user-defined network. For more information, see xref:../nodes/clusters/nodes-cluster-cgroups-2.adoc#nodes-cluster-cgroups-2[Configuring Linux cgroup]. (link:https://issues.redhat.com/browse/OCPBUGS-49933[*OCPBUGS-49933*])
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JoeAldinger Thanks
An event of type Warning, with reason UDNKubeletProbesNotSupported is triggered for impacted nodes

@npinaeva
Copy link

Considering @asood-rh 's comment ^ will be fixed
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 20, 2025
@asood-rh
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Feb 20, 2025

New changes are detected. LGTM label has been removed.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 20, 2025
@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 20, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Feb 20, 2025

@JoeAldinger: 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.

@JoeAldinger JoeAldinger merged commit e759947 into openshift:enterprise-4.18 Feb 20, 2025
2 checks passed
@openshift-ci-robot
Copy link

@JoeAldinger: Jira Issue OCPBUGS-49933 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Version(s):

Issue:
Fixes attribute and adds xref to RN.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
3 more reviewers

@abhat abhat abhat left review comments

@anuragthehatter anuragthehatter anuragthehatter left review comments

@asood-rh asood-rh asood-rh left review comments

Reviewers whose approvals may not affect merge requirements
Assignees

@npinaeva npinaeva

@asood-rh asood-rh

Labels
jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
OCP 4.18 GA
Development

Successfully merging this pull request may close these issues.
8 participants
@JoeAldinger @openshift-ci-robot @ocpdocs-previewbot @npinaeva @asood-rh @abhat @anuragthehatter @openshift-merge-robot