Forum Widgets
Recent Discussions
Accelerate Breakout Replay: The Modern Virtualization Journey at SiriusXM
Learn how SiriusXM modernized its infrastructure—key technology choices, migration tips, and strategies for scalable virtualization. Speakers: Adam Swidler Nate Mason, SiriusXM https://www.purestorage.com/video/webinars/the-modern-virtualization-journey-at-sirius-xm/6375807986112.htmlPortworx backup 2.9.1 is now GA
Portworx Backup 2.9.1 is now GA. This release has support for configuring limits for NFS backups with the Portworx, CSI, and KDMP drivers. Which helps users to define the maximum number of concurrent delete jobs, helping to prevent quota exhaustion and providing greater control over backup deletion management. Release-notesAccelerate Breakout Replay: Unifying VMs and Containers: Adopting Modern Virtualization with Portworx® and Red Hat OpenShift
See how Portworx® + Red Hat ease the move from VMware to modern platforms, using KubeVirt and container-native data strategies. Speakers: Eric Shanks George Jones, RedHat https://www.purestorage.com/video/webinars/adopting-modern-virtualization-with-portworx-red-hat-openshift/6375805963112.htmlAccelerate Breakout Replay: Architecting Data Infrastructure for AI at Scale
Explore how to optimize and scale AI with FlashArray™, FlashBlade®, and Portworx®—from vector DBs to model inferencing and data tuning. Speaker: Jon Owings https://www.purestorage.com/video/webinars/architecting-data-infrastructure-for-ai-at-scale/6375341437112.htmlAnnouncing the General Availability of Portworx Backup 2.9.0
We are excited to announce that the latest version of Portworx Backup 2.9.0 is now Generally Available. The latest version of PX Backup has the following new features and host of improvements. Features: Retry backups at VM level: you can now retry only failed VMs in VM backups without reprocessing successful ones, reducing load on backup server. This feature helps maintain efficient backup operations, provides granular control on VM backups and ensures better adherence to RPO targets. PXB deployment on proxy-enabled clusters: you can deploy PXB in proxy-enabled Kubernetes cluster (PXB cluster) environments across all supported platforms, except IKS. It supports proxy configuration through Helm parameters or Kubernetes secrets, including setups requiring authentication and custom CA certificates to ensure secure and compliant communication. Bulk operations for schedules: you can now suspend, resume, or delete multiple backup schedules in bulk, simplifying backup management across large environments. In addition, you can filter schedules by their names, schedule policies, or a combination of both to precisely target the desired schedules. Back up volume resources: you can now back up only the Kubernetes PersistentVolume (PV) and PersistentVolumeClaim (PVC) specifications without including the actual volume data. This helps to optimize backup jobs by reducing data footprint, improving performance, and avoiding redundancy when the volume data is protected through other mechanisms like external snapshots or NFS backups. Usage instructions: PXB 2.9.0 can be consumed via central. Upgrade instructions can be found here. Additional Resources Portworx Backup Documentation Release NotesPortworx Enterprise Version 3.2.3 - Release Announcement
We are excited to announce that Portworx Enterprise 3.2.3 is now Generally Available. This version consists of solutions for some key customer asks and support for FlashArray capabilities Key Highlights General Availability of FlashArray Direct Access (FADA) shared raw block (RWX) volumes Support for FADA shared raw block (RWX) volumes, to enable live migration of KubeVirt VMs with high-performance raw block storage Early access support for FlashArray Direct Access volumes with FlashArray Active Cluster feature Early access of the ability to create custom labels for storage pools. This helps placement of volumes and replicas based on environment or workload requirements Other Notable Improvements Support sticky option for FlashArray Direct Access Volumes Scalability improvements to reduce the load of the Kubernetes API Server Usage Instructions Prerequisites Supported Kernels Install, Upgrade and Usage Documentation Additional Resources and Documentation Release Notes Portworx Enterprise Documentation Run KubeVirt VMs with FlashArray Direct Access shared raw block (RWX) volumes ActiveCluster on FlashArray Direct Access volumes (Early Access) Custom labels for device pools (Early Access)
Hey I observed the following issue with pso which renders it unusable in 25 of our customer clusters
We can still not upgrade to portworx because of missing features, ```E0105 1755.820180 1 runtime.go:69] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:76 /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65 /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51 /usr/local/go/src/runtime/panic.go:969 /usr/local/go/src/runtime/panic.go:212 /usr/local/go/src/runtime/signal_unix.go:742 /go/src/pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1/intrusion_types.go:232 /go/src/pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1/intrusion_types.go:209 /go/src/pso.purestorage.com/cockroach-operator/pkg/controller/cockroach/intrusion/intrusion_controller.go:444 /go/src/pso.purestorage.com/cockroach-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215 /go/src/pso.purestorage.com/cockroach-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158 /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 /usr/local/go/src/runtime/asm_amd64.s:1374 panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xf6b5a7] goroutine 417 [running]: http://k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0|k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0) /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:58 +0x10c panic(0x161fd00, 0x22731b0) /usr/local/go/src/runtime/panic.go:969 +0x1b9 http://pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1.GetNodeIdentifier|pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1.GetNodeIdentifier(0xc0006d9564, 0xa, 0x0, 0xc00079d360, 0x11, 0x0, 0x0) /go/src/pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1/intrusion_types.go:232 +0x67 http://pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1.ValidateIntrusionSpec(0xc0005f2408|pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1.ValidateIntrusionSpec(0xc0005f2408, 0xc0002d0140, 0x0) /go/src/pso.purestorage.com/cockroach-operator/pkg/apis/pso/v1alpha1/intrusion_types.go:209 +0x2c5 http://pso.purestorage.com/cockroach-operator/pkg/controller/cockroach/intrusion.(*ReconcileIntrusion).Reconcile(0xc00057b6c0|pso.purestorage.com/cockroach-operator/pkg/controller/cockroach/intrusion.(*ReconcileIntrusion).Reconcile(0xc00057b6c0, 0xc0006d9520, 0xa, 0xc0006d9504, 0x6, 0xc0007ef578, 0xc0007ef578, 0x448f33, 0xc000092a18) /go/src/pso.purestorage.com/cockroach-operator/pkg/controller/cockroach/intrusion/intrusion_controller.go:444 +0x12f2 http://sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc00025ca00|sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc00025ca00, 0xc0008eab00) /go/src/pso.purestorage.com/cockroach-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215 +0x1de http://sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1()|sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1() /go/src/pso.purestorage.com/cockroach-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158 +0x36 http://k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc0005994c0)|k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc0005994c0) /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x5f http://k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0005994c0|k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0005994c0, 0x3b9aca00, 0x0, 0x1, 0xc0005c3d40) /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 +0x105 http://k8s.io/apimachinery/pkg/util/wait.Until(0xc0005994c0|k8s.io/apimachinery/pkg/util/wait.Until(0xc0005994c0, 0x3b9aca00, 0xc0005c3d40) /go/src/pso.purestorage.com/cockroach-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d created by http://sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start|sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start /go/src/pso.purestorage.com/cockroach-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:157 +0x331```I'm trying to redeploy a workload
I'm trying to redeploy a workload. When the pod is trying to spin up i'm getting this error: ``` MountVolume.SetUp failed for volume "pvc-af2b1e0f-2732-4c13-ac9f-a8b8332069a0" : rpc error: code = AlreadyExists desc = Volume is attached on another node ``` I thought PX was supposed to move the volumes to where the nodes are, or to schedule the pods to be run where the volume is? this volume has a repl of 2.
Community Resources
Account Info & Registration
Check out these articles for user account and registration information.
Using the Community
A place to learn how to find your way around the community.