Skip to main content
NetApp Knowledge Base

CVO Upgrade paused with error Node is not in "waiting for giveback state"

Views:
223
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Automated Non-Disruptive Upgrade (ANDU)

Issue

During CVO Upgrade the taken over node went down and the upgrade is paused with below error in cluster image show-update-progress :

AWSNAS08::> cluster image show-update-progress

                                             Estimated         Elapsed
Update Phase         Status                   Duration        Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks    completed                00:10:00        00:01:07
ONTAP updates        paused-on-error          01:32:00        01:03:35

Details:

Node name            Status            Status Description
-------------------- ----------------- --------------------------------------
AWSNAS-01          waiting
AWSNAS-02          failed              Error: Node "AWSNAS-02" is not in
                                       "waiting for giveback" state.
                                       Action: Use the "storage failover
                                       show" to verify that node
                                       "AWSNAS-02" is in one of the
                                       following states: "waiting for
                                       giveback" or "connected".
7 entries were displayed.

Status: Paused - An error occurred in "ONTAP updates" phase. The update cannot continue until the error has been resolved. Resolve all issues, then use the "cluster image resume-update" command to resume the update.

Output  of storage failover show :

AWSNAS08::> storage failover show
                              Takeover
Node           Partner        Possible State Description
-------------- -------------- -------- -------------------------------------
AWSNAS-01    AWSNAS-02    false        In takeover
AWSNAS-02    AWSNAS-01    -            Unknown
2 entries were displayed.

Output  of node show :

AWSNAS::> node show
Node      Health Eligibility Uptime        Model       Owner    Location
--------- ------ ----------- ------------- ----------- -------- ---------------
AWSNAS-01 true true          231 days 22:22 CDvM200
AWSNAS-02 false true                     - -           -        -

Warning: Unable to list entries on node AWSNAS-02. RPC: Couldn't make connection [from mgwd on node "AWSNAS-01"(VSID:-1) to mgwd at 10.80.41.145]
2 entries were displayed.

Disk reservation conflict found on the cloud provider serial console of down node :

Reservation conflict found on this node's disks! Local System ID: xxxxxxxxxx Press Ctrl-C for Maintenance menu to release disks. Boot argument NfsRdmaOk not specified. Default (set) is in effect. Boot argument NfsIpOk not specified. Default (set) is in effect. FWU 2nd trigger point FWU has no post firmware update action registered. sysctl_warn_reuse: can't re-use a leaf (sysvar.DETAIL_mask)! pnso provider init started. Notice : pnso card not detected. hwo: Node is using hardware provider : 1. cryptomod_fips: Executing Crypto FIPS Self Tests. cryptomod_fips: Crypto FIPS self-test: 'CPU COMPATIBILITY' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-128 ECB, AES-256 ECB' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-128 CBC, AES-256 CBC' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-128 GCM, AES-256 GCM' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-128 CCM' passed. cryptomod_fips: Crypto FIPS self-test: 'CTR_DRBG' passed. cryptomod_fips: Crypto FIPS self-test: 'KDF' passed. cryptomod_fips: Crypto FIPS self-test: 'SHA1, SHA256, SHA512' passed. cryptomod_fips: Crypto FIPS self-test: 'HMAC-SHA1, HMAC-SHA256, HMAC-SHA512' passed. cryptomod_fips: Crypto FIPS self-test: 'PBKDF2' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-XTS 128, AES-XTS 256' passed. cryptomod_fips: Crypto FIPS self-test: 'Self-integrity' passed. Waiting for reservations to clear

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.