[PCA 3.x] Node Pool Nodes in Failing state Post Upgrade/Patching from 302M3.8 to 302M3.9
(Doc ID 3035508.1)
Last updated on JULY 16, 2024
Applies to:
Private Cloud Appliance X10 - Version Not Applicable to Not Applicable [Release N/A]Private Cloud Appliance X9-2 - Version Not Applicable to Not Applicable [Release NA]
Private Cloud Appliance
Symptoms
When a rack on 302M3.8 milestone is upgraded/patched to 302M3.9 , some of the node pool nodes of existing clusters move to FAILING state after the upgrade completes while the underlying compute instances are in RUNNING state.
Changes
Upgrade
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |