Update release notes unity #1191
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shanmydell
requested review from
atye,
bharathsreekanth,
Deepak-Ghivari,
gallacher,
mdutka-dell,
mgandharva,
mjsdell,
prablr79,
rajendraindukuri,
rajkumar-palani,
rsedlock1958,
sharont58,
shaynafinocchiaro and
shefali-malhotra
as code owners
Test Results76 tests 76 ✅ 3s ⏱️ Results for commit 58cca45. ♻️ This comment has been updated with latest results. |
AkshaySainiDell
previously approved these changes
Jul 22, 2024
gallacher
reviewed
Jul 22, 2024
| @@ -36,7 +36,7 @@ description: Release notes for Unity XT CSI driver | |||
| | A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-unity.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-unity-2.8.0/charts/csi-unity/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. | | |||
| | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with Kubernetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | | |||
| | fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter | | |||
| | Controller publish is taking too long to complete/ Health monitoring is causing Unity array to panic by opening multiple sessions | Disable Volume health monitoring on the node and keep it only at the controller level.| | |||
| | Controller publish is taking too long to complete/ Health monitoring is causing Unity array to panic by opening multiple sessions | Disable Volume health monitoring on the node and keep it only at the controller level. Refer [here](https://dell.github.io/csm-docs/docs/csidriver/features/unity/#volume-health-monitoring) for more information about enabling/disabling volume health monitoring| | |||
There was a problem hiding this comment.
"Disable Volume health... " - Volume should be volume. What other information can be provided besides "Controller publish is taking too long?". What about things that would be observed in the logs? Under what circumstances would this be seen?
There was a problem hiding this comment.
@gallacher : Health monitoring is causing Unity array to panic by opening multiple sessions - This is the reason why it has been seen, it is also added
There was a problem hiding this comment.
@shanmydell - what errors are seen in the logs? What's observed in k8s? Please provide more details.
There was a problem hiding this comment.
Thanks @shanmydell for mentioning the error we are receiving in k8s logs, reason and the roundabout to circumvent the issue.
chimanjain
force-pushed
the
update_release_notes_unity
branch
from
a47e9d5 to
58cca45
Compare
shefali-malhotra
approved these changes
Jul 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A few sentences describing the overall goals of the pull request's commits.
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist: