#Unable to add ONTAP Cluster - 4.0.1

1 messages · Page 1 of 1 (latest)

stoic ivy
#

We created the role and the user as stated in the documentation. However, we get the following error: "empty cluster name". But it works if we use the admin user.
Did the needed permissions change?

autumn zephyr
sweet crag
#

What is your ONTAP version ? Please collect a support bundle and send it to help@NAbox.org

stoic ivy
#

The link helped with troubleshooting, thanks for that! Adding a cluster has now worked. However, I find the documentation (especially on nabox.org) somewhat misleading, or maybe I don't fully understand the permissions concept.
I currently don't have access to the systems, but I will send an update tomorrow.
Thanks a lot for now!
@autumn zephyr I'm not falarcon10, sorry 🙂

autumn zephyr
#

glad you made some progress! No worries, we got a similar question on GitHub and I was trying to understand if they were the same. Thanks

sweet crag
#

Let me know how I can improve the documentation !

stoic ivy
#

Okay, although I don't have any logs, I'll try to explain our approach.

If I understand the documentation correctly, the connection should work if there is a user with "-application http" and an RO role with "-api /api".
However, this resulted in the error 'empty cluster name'.
After we added "-application ontapi" to the user, it worked. The role wasn't changed.

Does Harvest gather data either via ONTAPI or REST, or are both methods used and there needs to be a corresponding user?

sweet crag
#

I don’t think everything is available through REST. What is the exact ONTAP version indicated by “version” ?

stoic ivy
#

It's 9.12.1P7

sweet crag
#

Ok. The error seems to indicate that version couldn’t be fetched using rest and fell back to Zapi which failed again.

autumn zephyr
#

How Harvest handles REST and ZAPI is documented here https://netapp.github.io/harvest/nightly/architecture/rest-strategy/#how-does-harvest-decide-whether-to-use-rest-or-zapi-apis

"empty cluster name" is an nabox error that happened when trying to add a new cluster via the UI. As Yann, mentioned nabox attempts to use REST to gather the cluster's name first and if that fails, attempts to use ZAPI.

Sounds like in your case, the initial REST request failed and then ZAPI failed. ZAPI failing was expected in your case, but what is not understood is why REST failed. @sweet crag is anything logged when the REST call fails the first time?

Harvest does not require ZAPI

sweet crag
#

What has been changed to make it work ? It seems maybe even rest didn’t have privileges ?

I’m providing a build with details logged soon

sweet crag
chilly ore
sweet crag
#

What is the exact version string for this cluster ?

chilly ore
#

it's the GA so : NetApp Release 9.14.1: Wed Jan 24 025030 UTC 2024

#

The others that worked are 9.14.1P5

sweet crag
#

Ok I see what’s going on

chilly ore
#

Just tested with another cluster... also running the same release and I get the same result... I'm looking for a cluster with another release so make sure it's the version that is causing it..

#

...yep managed to add a cluster with release 9.13.1P4

sweet crag
#

You will have this issue with non-P release

chilly ore
sweet crag
#

It’s in 4.0.2 which has been released

chilly ore
stoic ivy
sweet crag
#

4.0.2 has it