Skip to main content
NetApp Stage KB

CVO upgrading is failed due to the error "Qtree does not exist"

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

 

 

Applies to

  • NetApp Cloud Volumes ONTAP (CVO)
  • NetApp Cloud Manager 3.9.16
  • Qtree name is created by multi-byte Language

Issue

The CVO version upgrading is failed due to an error:
 
Sat Apr 16 2022 09:19:46 +09:00 [kern_audit:info:3160] 8305e800008a79be :: xxxxxxxxxxxxx:ontapi :: pii_encrypt/rG03/tp5EmuxyJ12/FmYYbXL6tCA0qt0M+oQkzv8qz7vSfQE9uWMeHTQm4T6aDbu+/pii_encrypt :: svm-og1:admin :: qtree-modify :: Error: Failed to modify qtree "xxxxxxxxxx@\303\203\302\244\303\202\302\272\303\202\302\213\303\203\302\246\303\202\302\245\303\202\302\255\303\203\302\247\303\202\302\265\303\202\302\214\303\203\301\447\603\602\303\220\303\204\302\204\303\203\302\251\302\602\302\203\303\102\302\350" for volume "xxxxxx" on Vserver "xxxxx". Reason: Qtree xxxxxxxxxx@\303\203\302\244\303\202\302\272\303\202\302\213\303\203\302\246\303\202\302\245\303\202\302\255\303\203\302\247\303\202\302\265\303\202\302\214\303\203\301\447\603\602\303\220\303\204\302\204\303\203\302\251\302\602\302\203\303\102\302\350" does not exist.
 
Note:
The Qtree name contains characters of multi-byte language (Japanese)

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.