-
Notifications
You must be signed in to change notification settings - Fork 36
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
docs: add new vsphere known issue #3896
Conversation
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Some quick comments
@@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti | |||
|
|||
| Description | Workaround | Publish Date | Product Component | | |||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | | |||
| Self-hosted instances of Palette in VMware vCenter do not have unique cluster IDs for their persistetn volumes. This can lead to issues if there are multiple self-hosted instances of Palette or during an upgrade. | Refer to the Troubleshooting section for guidance. | Sep 13, 2024 | Self-hosted | |
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.
Double checking on Sumit with the issue because I don't think clusters not having unique IDs was the case, but rather the PVC all looked the same, regardless of what EC cluster it belonged to.
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.
I am just going to use the language from Romain in the slack channel
Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com>
@@ -77,3 +77,83 @@ following steps to restart the management pod. | |||
```shell hideClipboard | |||
pod "mgmt-f7f97f4fd-lds69" deleted | |||
``` | |||
|
|||
## Non-unique vSphere CNS Mapping |
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.
🚫 [vale] reported by reviewdog 🐶
[spectrocloud-docs-internal.headings-title] Avoid using a noun that starts with an -ing in headings. Your heading starts with a word ending in 'ing'.
|
||
## Non-unique vSphere CNS Mapping | ||
|
||
In Palette releases 4.4.8 and earlier, Persistent Volume Claims (PVCs) metadata do not use a unique identifier for |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVCs'?
## Non-unique vSphere CNS Mapping | ||
|
||
In Palette releases 4.4.8 and earlier, Persistent Volume Claims (PVCs) metadata do not use a unique identifier for | ||
self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, potentially leading |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Terms] Use 'cloud' instead of 'Cloud'.
|
||
This issue is resolved in Palette releases starting with 4.4.14. However, upgrading to 4.4.14 will not automatically | ||
resolve this issue. If you have self-hosted instances of Palette in your vSphere environment older than 4.4.14, you | ||
should execute the following utility script manually to make the Cloud Native Storage (CNS) mapping unique for the |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Terms] Use 'cloud' instead of 'Cloud'.
@@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti | |||
|
|||
| Description | Workaround | Publish Date | Product Component | | |||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | | |||
| Persistent Volume Claims (PVCs) metadata do not use a unique identifier for self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, potentially leading to issues during node operations and cluster upgrades. | Refer to the Troubleshooting section for guidance. | Sep 13, 2024 | Self-hosted | |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVCs'?
@@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti | |||
|
|||
| Description | Workaround | Publish Date | Product Component | | |||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | | |||
| Persistent Volume Claims (PVCs) metadata do not use a unique identifier for self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, potentially leading to issues during node operations and cluster upgrades. | Refer to the Troubleshooting section for guidance. | Sep 13, 2024 | Self-hosted | |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Terms] Use 'cloud' instead of 'Cloud'.
@@ -61,6 +61,7 @@ for information on the fix version and the date the issue was resolved. | |||
|
|||
| Description | Publish Date | Product Component | Fix Version | | |||
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------- | ----------- | | |||
| In a VMware environment, self-hosted Palette instances do not receive a unique cluster ID when deployed, which can cause issues during a node repave event, such as a Kubernetes version upgrade. Specifically, Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) will experience start problems due to the lack of a unique cluster ID. | April 14, 2024 | Self-Hosted | 4.4.14 | |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVs'?
@@ -61,6 +61,7 @@ for information on the fix version and the date the issue was resolved. | |||
|
|||
| Description | Publish Date | Product Component | Fix Version | | |||
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------- | ----------- | | |||
| In a VMware environment, self-hosted Palette instances do not receive a unique cluster ID when deployed, which can cause issues during a node repave event, such as a Kubernetes version upgrade. Specifically, Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) will experience start problems due to the lack of a unique cluster ID. | April 14, 2024 | Self-Hosted | 4.4.14 | |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVCs'?
kubectl delete pvc mongo-data-mongo-2 --namespace=hubble-system | ||
``` | ||
|
||
8. Delete the PV associated with the MongoDB pod. Use the following command to list all PVs and find the PV associated |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVs'?
@@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti | |||
|
|||
| Description | Workaround | Publish Date | Product Component | | |||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | | |||
| Persistent Volume Claims (PVCs) metadata do not use a unique identifier for self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, potentially leading to issues during node operations and cluster upgrades. | Refer to the [Troubleshooting section](../troubleshooting/enterprise-install.md#non-unique-vsphere-cns-mapping) for guidance. | Sep 13, 2024 | Self-hosted | |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVCs'?
@@ -16,6 +16,7 @@ The following table lists all known issues that are currently active and affecti | |||
|
|||
| Description | Workaround | Publish Date | Product Component | | |||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | | |||
| Persistent Volume Claims (PVCs) metadata do not use a unique identifier for self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, potentially leading to issues during node operations and cluster upgrades. | Refer to the [Troubleshooting section](../troubleshooting/enterprise-install.md#non-unique-vsphere-cns-mapping) for guidance. | Sep 13, 2024 | Self-hosted | |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Terms] Use 'cloud' instead of 'Cloud'.
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.
Just some minor suggestions. The only other item worth noting is that we need the same in the VerteX section. I called it out where needed. Thanks for tackling this @lennessyy
docs/docs-content/enterprise-version/upgrade/upgrade-vmware/non-airgap.md
Show resolved
Hide resolved
@lennessyy I added the version backports for 4.0 and 4.1 as they were missing. |
Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com>
|
||
## Non-unique vSphere CNS Mapping | ||
|
||
In Palette and VerteX releases 4.4.8 and earlier, Persistent Volume Claims (PVCs) metadata do not use a unique |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PVCs'?
## Non-unique vSphere CNS Mapping | ||
|
||
In Palette and VerteX releases 4.4.8 and earlier, Persistent Volume Claims (PVCs) metadata do not use a unique | ||
identifier for self-hosted Palette clusters. This causes incorrect Cloud Native Storage (CNS) mappings in vSphere, |
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.
🚫 [vale] reported by reviewdog 🐶
[Vale.Terms] Use 'cloud' instead of 'Cloud'.
* docs: first draft * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * docs: add clarifying details * docs: move old content to deprecated * docs: clarify known issue not automatically resolved * docs: add warning to more obvious places * docs: add link to warning and xlinks * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * ci: auto-formatting prettier issues --------- Co-authored-by: Lenny Chen <lenny.chen@spectrocloud.com> Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> Co-authored-by: lennessyy <lennessyy@users.noreply.github.com> (cherry picked from commit b46a973)
* docs: first draft * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * docs: add clarifying details * docs: move old content to deprecated * docs: clarify known issue not automatically resolved * docs: add warning to more obvious places * docs: add link to warning and xlinks * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * ci: auto-formatting prettier issues --------- Co-authored-by: Lenny Chen <lenny.chen@spectrocloud.com> Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> Co-authored-by: lennessyy <lennessyy@users.noreply.github.com> (cherry picked from commit b46a973)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
* docs: first draft * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * docs: add clarifying details * docs: move old content to deprecated * docs: clarify known issue not automatically resolved * docs: add warning to more obvious places * docs: add link to warning and xlinks * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * ci: auto-formatting prettier issues --------- Co-authored-by: Lenny Chen <lenny.chen@spectrocloud.com> Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> Co-authored-by: lennessyy <lennessyy@users.noreply.github.com> (cherry picked from commit b46a973) Co-authored-by: Lenny Chen <55669665+lennessyy@users.noreply.github.com>
* docs: add new vsphere known issue (#3896) * docs: first draft * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * docs: add clarifying details * docs: move old content to deprecated * docs: clarify known issue not automatically resolved * docs: add warning to more obvious places * docs: add link to warning and xlinks * Apply suggestions from code review Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> * ci: auto-formatting prettier issues --------- Co-authored-by: Lenny Chen <lenny.chen@spectrocloud.com> Co-authored-by: Karl Cardenas <29551334+karl-cardenas-coding@users.noreply.github.com> Co-authored-by: lennessyy <lennessyy@users.noreply.github.com> (cherry picked from commit b46a973) * docs: fix broken link --------- Co-authored-by: Lenny Chen <55669665+lennessyy@users.noreply.github.com> Co-authored-by: Lenny Chen <lenny.chen@spectrocloud.com>
🎉 This issue has been resolved in version 4.4.13 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the Change
This PR adds a new known issue with regarding self-hosted instances in vsphere.
Changed Pages
💻 Troubleshooting
Known Issues
Upgrade notes
Jira Tickets
🎫 DOC-1376
🎫 DOC-1377
🎫 DOC-1378
Backports
Can this PR be backported?