Skip to content

Commit

Permalink
docs: add to resolved list
Browse files Browse the repository at this point in the history
  • Loading branch information
lennessyy committed Jul 23, 2024
1 parent 4b8fb79 commit 1b795f2
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/docs-content/release-notes/known-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,7 @@ for information on the fix version and the date the issue was resolved.

| Description | Publish Date | Product Component | Fix Version |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------- | ----------- |
| The VerteX enterprise cluster is unable to complete backup operations. | June 6, 2024 | VerteX | 4.4.11 |
| An issue prevents RKE2 and Palette eXtended Kubernetes (PXK) on version 1.29.4 from operating correctly with Canonical MAAS. | July 20, 2024 | Packs, Clusters | 4.4.11 |
| Deploying self-hosted Palette or VerteX to a vSphere environment fails if vCenter has standalone hosts directly under a Datacenter. Persistent Volume (PV) provisioning fails due to an upstream issue with the vSphere Container Storage Interface (CSI) for all versions before v3.2.0. Palette and VerteX use the vSphere CSI version 3.1.2 internally. The issue may also occur in workload clusters deployed on vSphere using the same vSphere CSI for storage volume provisioning. | July 20, 2024 | Self-Hosted | 4.4.11 |
| When you upgrade VerteX from version 4.3.x to 4.4.x, a few system pods may remain unhealthy and experience _CrashLoopBackOff_ errors. This issue only impacts VMware vSphere-based installations and occurs because the internal Mongo DNS is incorrectly configured in the configserver ConfigMap. | June 29, 2024 | Self-Hosted, VerteX | 4.4.7 |
Expand Down

0 comments on commit 1b795f2

Please sign in to comment.