I just did an in place upgrade of VSC 4.1 to 4.2.1. When looking at the roles inside the VIC, I do not see any of the new default canned vsc roles. I now have no access to my backups. Has anyone seen this before? Is a reboot required? It is not mentioned in the documentation from what I saw, but it could have been over looked.
What role does the user have whose credentials are registered at https://VSC_HOST:8143/Register.html? Those credentials should belong to a user with the Administrator role (not just "VSC Administrator").
Just so I understand,
What do you see in VSC_INSTALL_DIR\log\nvpf.log on VSC service restart?
That is correct. I am seeing the same things in the log. The only thing that glares out to me is "Communication failure while creating role: VSC Administrator com.vmware.vim25.NoPermission".
Checking the event log I see the following: Persistence file ../../etc/vsphere-credentials does not exsist. as well as ../../etc/cred I am however seeing these files.
Found this even log entry as well:
10452 [WrapperSimpleAppMain] WARN com.netapp.common.flow.Engine - FLOW-10099: Exception while enabling Java Management Extensions
the message resource is present but the message is not found in the string/message table
1. Delete VSC_INSTALL_DIR/etc/vsphere-credentials,
2. Restart the VSC service,
3. Re-register at https://localhost:8143/Register.html with credentials for the user that is a vSphere Administrator (has all vSphere privileges).
No luck. I am seeing the same erros in the nvpf log as well as the event viewer. The Java error appears to be gone, but now it says it cannot find the /etc/cred as well as /etc/vsphere-credentials.
I have opened a case with NetApp as well. I am still not seeing the canned roles.