Articles in this section

Cannot scale cluster, pods stuck in initialization

Problem Description

Cluster cannot scale.  It gets stuck in server initialization.  The PVCs appear to exist but are not getting attached to the Aerospike node pod.

In the server-init pod log we see this message:

INFO:pod-name: aerocluster2-0-5 - Get configuration request
DEBUG:Request config from url: https://kubernetes.default.svc/apis/asdb.aerospike.com/v1beta1/namespaces/aerospike/aerospikeclusters/aerocluster2
DEBUG:Request pod-image from url: https://kubernetes.default.svc/api/v1/namespaces/aerospike/pods/aerocluster2-0-5
DEBUG:Looking for Pod-Image
INFO:pod-name: aerocluster2-0-5 - Initializing
INFO:pod-name: aerocluster2-0-5 - Checking if volume initialization needed
DEBUG:pod-name: aerocluster2-0-5 - Looking for initialized volumes in status.pod.aerocluster2-0-5.initializedVolumes
WARNING:pod-name: aerocluster2-0-5 - Initialized volumes not found in status.pod.aerocluster2-0-5.initializedVolumes
DEBUG:pod-name: aerocluster2-0-5 - Looking for initialized volumes in status.pod.aerocluster2-0-5.initializedVolumePaths
WARNING:pod-name: aerocluster2-0-5 - Initialized volumes not found
DEBUG:pod-name: aerocluster2-0-5 - Checking for rack in rackConfig rack-id: 0
DEBUG:pod-name: aerocluster2-0-5 - Looking for volumes in rack.effectiveStorage.volumes
'effectiveWipeMethod'

 


Explanation

From the message "effectiveWipeMethod" we can see that at some point in an upgrade of the operator CRDs containing the call "effectiveWipeMethod" messages was missed and is now unavailable for the operator code to use. 

Solution

Apply the proper CRD version or versions to the AKO installation to provide the "effectiveWipeMethod"

Applies To Earliest Version

4.9

Applies To Latest Version

Current Version
Was this article helpful?
0 out of 0 found this helpful