Closed triceam closed 1 year ago
Support case created: https://cloud.ibm.com/unifiedsupport/cases?number=CS3084464
The disk pressure status appears to be related to a regression in ROKS, which is separate from the Portworx issue. Details/discussion on the disk pressure condition in Slack at: https://ibm-cloudplatform.slack.com/archives/CJH0UPN2D/p1666900631736399?thread_ts=1666896501.625019&cid=CJH0UPN2D
Update:
I started a thread on the Portworx forums here: https://forums.portworx.com/t/portworx-failing-on-openshift-4-10-on-ibm-cloud/1478
I also requested an account on https://pure1.purestorage.com/support so I can create support tickets for Portworx/Pure Storage, but it has to be "approved" before I can submit a ticket.
response on forums:
This implies the kernel is not compatible with the Portworx version. I am assuming you are trying to install Portworx 2.11.4 with Cloud Drives option. We will get PWX version updated (within 48 hours).
Just confirmed Portworx is working again on IBM Cloud, based on update from the Portworx forums thread above.
Portworx deployments on IBM Cloud are failing due to a recent change by Portworx. This scenario can be recreated using our automation, or when clusters & portworx deployments are created manually. Deploying Portworx onto a brand new cluster results in:
To recreate:
portworx
andportworx-api
DaemonSets never enter a healthy state, and both events and logs show failures. It looks like the Portworx deployment tries to self-update, and fails. This also ends up eating up disk space on the cluster, and sends the workers into a "Disk Pressure" warning state.