Bug 2094829
| Summary: | node-volume-attach-limit not considered | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | rlobillo |
| Component: | Storage | Assignee: | ShiftStack Bugwatcher <shiftstack-bugwatcher> |
| Storage sub component: | OpenStack CSI Drivers | QA Contact: | Jon Uriarte <juriarte> |
| Status: | CLOSED DEFERRED | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | lmurthy, pprinett |
| Version: | 4.11 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause: CSINode's count isn't updated by kubelet when CSIDriver provides a new value.
Consequence: This causes node-volume-attach-limit cloud provider option modifications to be ignored.
Workaround (if any): After modification delete CSINode objects and restart kubelet on all the nodes. You might also just delete all CSINode objects before the modification of cloud provider config.
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-03-09 01:21:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
rlobillo
2022-06-08 11:39:17 UTC
Okay, a simple workaround to the problem is to delete CSINode objects and restart kubelet on every of the nodes. Then the node-volume-attach-limit is correctly put there and everything will work find. We don't understand the root cause yet, but clearly it's an issue with the fact you're updating the configuration after the installation. OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-9308 |