Hello Everyone, I have an issue when trying to create two portworx Cluster on OpenShift 4.14 (OnPrem). I need to expose the service “portworx-service” for the remote connection between Clusters but when the route is created, nothing really happen. When i try to reach the route, i got “404 not found”. I also saw that the service was listing to a range starting at 9001 - 9021. Does anyone have already encountered this issue ? 1 post - 1 participant Read full topic ..read more

Portworx enterprise 3.0.5 is now GA, Refer release notes for more details 1 post - 1 participant Read full topic ..read more

Team, Happy to announce that we have made operator 23.10.5 GA. Highlight : Support for OCP 4.15. Release notes : https://docs.portworx.com/release-notes/operator#23105 1 post - 1 participant Read full topic ..read more

Portworx Enterprise 3.1.1 is now available! It is the latest release of Portworx Enterprise and has support for latest Kubernetes versions. This release includes several important enhancements and bug fixes as described in the release notes - Portworx Enterprise Release Notes | Portworx Documentation Please visit the pre-requisites and supported kernels page on the documentation site as there are updates post 3.1.0. 3.1.1 is the latest patch release on 3.1.x release train and this will be the next extended maintenance release after 2.13.x. The release lifecycle support policy document has been ..read more

Where can I find documentation about supported baremetal k8s node disks? I found this document but it only lists cloud provider disk types: docs.portworx.com Supported disk types | Portworx Documentation Various volume type that are supported by Portworx. 1 post - 1 participant Read full topic ..read more

Operator 23.10.4 has been GA’d. Contains support for ROKS 4.14 and also ability to export metric for OCP prometheus from OCP 4.12 and above on all the platforms (ARO, ROSA,ROKS and vanilla OCP). Some important fixes related to Anthos(1.28) upgrade are also part of this operator release. More details regarding the release can be found here : https://docs.portworx.com/release-notes/operator#23104 Note: Customers who are using autopilot has to upgrade to 1.3.14 with the above mentioned operator version. Autopilot 1.3.14 has been GA’d Contains: OpenShift users on version 4.12 or newer, can now con ..read more

Portworx Enterprise 2.13.12 is now available. This patch release includes critical fixes as described in the release notes - Portworx Enterprise Release Notes | Portworx Documentation Note that this release is for customers who are running 2.13.x (extended maintenance version) as outlined here. 3.1.0 is the latest feature release and it is recommended that customers upgrade to newest version especially if they are seeking support for newer Kubernetes versions. 1 post - 1 participant Read full topic ..read more

Hi there, I’m working on setting up PX-Essentials in our POC microk8s environment. License is showing as active. Pods are up and running and everything looks mostly good, but I’m seeing this error when I run “pxctl alerts show” NODE CallHomeFailure 91a9634e-f1fb-4588-8a95-c4199054ccef ALARM 1585 Feb 27 14:22:52 UTC 2024 Jan 24 17:45:52 UTC 2024 Error while calling home: failed to send callhome data. meteringUsageError: failed to send telemetry data after 4 retries. Loggly error count: 0, Pure1 error count: 1, clusterDataError: failed to send cluster telemetry data. Pure1 error: Post “http://10 ..read more

While validating Portworx v3.0.4 on Kubernetes (Hosted in MAAS), encountered this error that prevents portworx pod from coming up normally. Portworx version: v3.0.4 OS : Ubuntu 22.04 Kernel : Linux bm-az2-145 5.15.0-97-generic #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux @bm-az2-145 portworx[35235]: Failed to build PX filesystem dependency... @bm-az2-145 portworx[35235]: Attempting download from https://mirrors.portworx.com/build-results/pxfuse/released/12_latest/x86_64/5.15.0-97-generic/version/12/px.ko ... @bm-az2-145 portworx[35235]: Attempting download from h ..read more

Hi, i have a problem when i try to do snapshoot with csi driver. I have this error: name: px-csi-snapshot namespace: default resourceVersion: ‘483307549’ uid: 525fdf34-ddef-487b-8c07-62f15d39a775 selfLink: >- /apis/snapshot.storage.k8s.io/v1/namespaces/default/volumesnapshots/px-csi-snapshot status: error: message: >- Failed to create snapshot content with error snapshot controller failed to update px-csi-snapshot on API server: cannot get claim from snapshot time: ‘2024-02-26T07:49:04Z’ readyToUse: false spec: source: persistentVolumeClaimName: powerdns-pv volumeSnapshotClassName: px-c ..read more