#Upgraded to 3.3 and now don't see all volumes
1 messages · Page 1 of 1 (latest)
Upgraded to 3.3 and now don't see all volumes
@tribal rapids I see that you have upgraded NABox to 3.3. Could you share Harvest version being used? Also if you could email logs to ng-harvest-files@netapp.com
https://nabox.org/documentation/troubleshooting/#collecting-logs
@iron coral harvest is running on version 22.11.1-1
You should definitely upgrade harvest as well. Also double check the roles created for it, not sure when it was modified last time
@hot marten Thanks for the information. Yes, Please try upgrading to latest Harvest version. Additionally, Could you send us the Harvest logs via email ng-harvest-files@netapp.com? These logs are needed for us to further investigate and understand issues you might be experiencing.
https://nabox.org/documentation/troubleshooting/#collecting-logs
@iron coral i followed the article, the first command gets hung after I execute it.
I will upgrade the harvest
@hot marten dc logs -f --tail 10 nabox-api will follow the logs, printing them to the console as they happen. It won't finish until the process dies or you press Ctrl+C. Can you run this instead to collect the logs and tar.gz them?
dc logs nabox-api > nabox-api.log; dc logs nabox-harvest2 > nabox-harvest2.log;
tar -czf nabox-logs-date +%Y-%m-%d_%H:%M:%S.tgz *
Thank you Chris. I have sent the logs to the above email address provided by Rahul
thanks! received, we'll take a look
@hot marten still digging through the log files, but one thing that jumps out related to missing volumes is there are four clusters were the user talking to the cluster does not have permission to get volumes.
I'm guessing you followed the least-privileged approach outlined here https://netapp.github.io/harvest/23.08/prepare-cdot-clusters/#least-privilege-approach perhaps volume was missed when you did that
Two more permissions issues I noticed. The security template tries to collect fips, telnet, and rsh protocol information via the security-config-get and security-protocol-get zapi. Both of those are failing due to insufficient privileges: user 'netapp-harvest'
Ok, checking the permissions.