Are you able to browse vCenter Server component from BL console. If not then you should do DCO first on server for vCenter. If vCenter can be browsed then check if you can see datastore in console for that vCenter.
There might be issue with vCenter credentials store in BSA console property dictonary. This is probably DCO issue.
I think there is a missunderstanding.
We do not have any problem with accessing our Datastores (LUNs) in vC - what I meant is that we have issues to configure the Installer/RSCD location through the PxeDatastore Instance which is defined in the Property Dictionary/Built-in-Property Classes when we try to add or change a System Package.
I have opened an incident for that.
not sure where you are getting anything about virtual provisioning here ...
anyway - i think that's some kind of datastore validation happening - do you see anything in the rscd log on the datastore when you do this ? (maybe on debug logging)
no, after activating debug for rscd on the only info in the rscd.log is about divice type/filesystem and total/free/used space.
When I try to add/change the Installer/RSCD location nothing is logged in the rscd.log.
what version of bsa ? and are you browsing to the datastore location to add the relative paths to the various installers or just typing it in ?
BSA Version: 8.6.01.66
OS for our environment is SLES 12 SP0
Problem was solved by support.
The PXE Server is managed by short name, the DataStore Instance had the fqdn in the LOCATION propertie.
Changing the propertie to the short name solved the problem.
I am just wondering why this worked out for so long.
Thank you for help.
maybe the check was made more strict ? i believe the same has happened w/ patch catalogs.
what was your ticket # ?
the ticket # was INC000000100235.