SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)

orourke — Thu, 05 Jun 2025 07:17:13 GMT

I am using SDU 4.1.1 and SMO 3.0.3. I am trying to cloine a database and get the following error in the SDU log.

09:34:26 03/15/10 [5132b90]v,2,1,OUPUT <results reason="Invalid resource specified. Unable to find its Id" status="failed" errno="21041"/>

The flexclone of the NFS mount is created and is attached to the server however, the discovery fails. This looks similar ro BURT 381711, but not exactly.

When going through the discovery phase, does SDU need to see the "new flexcloned" volume in OpsManager? Could it be a refresh cycle in OpsManager?

I am using RBAC for SDU. I have attached the log files from SMO and SDU for the execution of the clone.

Here is a more detailed clip from the SDU log:

09:34:25 03/15/10 [5132b90]v,2,1,CDFMFactory::getServers()
09:34:25 03/15/10 [5132b90]v,2,35,readDFMConfigParms() port:8488 https:1
09:34:25 03/15/10 [5132b90]v,2,35,readDFMConfigParms() DFM List : chivmopsmgr
09:34:25 03/15/10 [5132b90]v,2,1,CDFMFactory::connect: admin: sd-admin
09:34:25 03/15/10 [5132b90]v,2,1,na_server_set_timeout 60
09:34:26 03/15/10 [5132b90]v,2,2,Data Protection Manager plug-in is installed with DFM server chivmopsmgr
09:34:26 03/15/10 [5132b90]v,2,2,CDFMRbac::readConfigParms()
09:34:26 03/15/10 [5132b90]v,2,35,determineUserName:
09:34:26 03/15/10 [5132b90]v,9,0,ASSISTANT EXECUTION (at 320774.676763): ypmatch passwd.byname
09:34:26 03/15/10 [5132b90]v,9,0,ASSISTANT EXECUTION (at 320774.688491): Output:
Usage: ypmatch [-d domain] [-kt] key ... mapname | -x
Try `ypmatch --help' or `ypmatch --usage' for more information.
09:34:26 03/15/10 [5132b90]v,2,35,determineUserName: userName:CHIVMRHEL54\
09:34:26 03/15/10 [5132b90]v,2,2,CDFMRbac::readConfigParms: username: CHIVMRHEL54\ cache:0 refreshTime: 15 refreshRetry: 12
09:34:26 03/15/10 [5132b90]i,2,2,CDFMRbac::checkRbac: resource name: chi250:/vol/SnapManager_20100315093057988_oracle_10g_data_dbtest1 operation: SD.Storage.Read type: volume us
er: CHIVMRHEL54\root
09:34:26 03/15/10 [5132b90]i,2,2,CDFMRbac::checkVolAccess:rbac-access-check for volume: chi250:/vol/SnapManager_20100315093057988_oracle_10g_data_dbtest1 operation:SD.Storage.Re
ad
09:34:26 03/15/10 [5132b90]v,2,2,DfmRbac::executeRbacApi:
09:34:26 03/15/10 [5132b90]v,2,1,INPUT <rbac-access-check>
        <admin-name-or-id>CHIVMRHEL54\root</admin-name-or-id>
        <operation>SD.Storage.Read</operation>
        <resource>
                <resource-identifier>
                        <volume>
                                <volume-resource>
                                        <host-identifier>
                                                <host-resource>
                                                        <host-name>chi250</host-name>
                                                </host-resource>
                                        </host-identifier>
                                        <volume-identifier-name-or-id>
                                                <volume-name-or-id>
                                                        <volume-name>SnapManager_20100315093057988_oracle_10g_data_dbtest1</volume-name>
                                                </volume-name-or-id>
                                        </volume-identifier-name-or-id>
                                </volume-resource>
                        </volume>
                </resource-identifier>
        </resource>
</rbac-access-check>

09:34:26 03/15/10 [5132b90]v,2,1,OUPUT <results reason="Invalid resource specified. Unable to find its Id" status="failed" errno="21041"/>

09:34:26 03/15/10 [5132b90]v,2,1,DfmRbac::executeRbacApi:rbac-access-check failed reason: Invalid resource specified. Unable to find its Id

Details from the SMO log file:

2010-03-15 09:31:12,071 [default0 28a1eebb1cfc4edb7474e1e0b58b166a] [INFO ]: SD-00016: Discovering storage resources for /u02/data/dbtest1_CLONE1.
2010-03-15 09:31:12,084 [default0 28a1eebb1cfc4edb7474e1e0b58b166a] [DEBUG]: EXE-00000: Executing shell command:
0:/bin/sh -c "/usr/sbin/snapdrive" "storage" "show" "-fs" "/u02/data/dbtest1_CLONE1"
1:/usr/sbin/snapdrive storage show -fs /u02/data/dbtest1_CLONE1
2010-03-15 09:34:20,403 [Execution Monitor Thread [/usr/sbin/snapdrive storage show -fs /u02/data/dbtest1_CLONE1]] [DEBUG]: EXE-00001: Shell result [0:03:08.318] (Exit Value: 54
😞
0002-719 Warning: Could not check SD.Storage.Read access on volume chi250:/vol/SnapManager_20100315093057988_oracle_10g_data_dbtest1 for user CHIVMRHEL54\root on Operations Mana
ger server(s) chivmopsmgr
Reason: Invalid resource specified. Unable to find its Id on Operations Manager server chivmopsmgr

2010-03-15 09:34:20,409 [default0 28a1eebb1cfc4edb7474e1e0b58b166a] [WARN ]: SD-10015: Snapdrive command "/usr/sbin/snapdrive storage show -fs /u02/data/dbtest1_CLONE1" generate
d warning: 0002-719 Warning: Could not check SD.Storage.Read access on volume chi250:/vol/SnapManager_20100315093057988_oracle_10g_data_dbtest1 for user CHIVMRHEL54\root on Oper
ations Manager server(s) chivmopsmgr
Reason: Invalid resource specified. Unable to find its Id on Operations Manager server chivmopsmgr

2010-03-15 09:34:20,556 [default0 28a1eebb1cfc4edb7474e1e0b58b166a] [DEBUG]: SD-00018: Error discovering storage for /u02/data/dbtest1_CLONE1: SD-10016: Error executing snapdriv
e command "/usr/sbin/snapdrive storage show -fs /u02/data/dbtest1_CLONE1": 0002-719 Warning: Could not check SD.Storage.Read access on volume chi250:/vol/SnapManager_20100315093
057988_oracle_10g_data_dbtest1 for user CHIVMRHEL54\root on Operations Manager server(s) chivmopsmgr
Reason: Invalid resource specified. Unable to find its Id on Operations Manager server chivmopsmgr
.
com.netapp.snapfile.snapdrive.legacy.unix.SnapDriveUnixExecutionException: SD-10016: Error executing snapdrive command "/usr/sbin/snapdrive storage show -fs /u02/data/dbtest1_CL
ONE1": 0002-719 Warning: Could not check SD.Storage.Read access on volume chi250:/vol/SnapManager_20100315093057988_oracle_10g_data_dbtest1 for user CHIVMRHEL54\root on Operatio
ns Manager server(s) chivmopsmgr
Reason: Invalid resource specified. Unable to find its Id on Operations Manager server chivmopsmgr

Re: SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)

orourke — Tue, 16 Mar 2010 18:26:37 GMT

I found the problem. There was a second OpsManager server on the network that I was not aware of. The "forced discovery" was not updating OpsManager server I was working with, but the "other" OpsManager server was fat, dumb, and happy.

Egg of face.....

Re: SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)

watan — Tue, 16 Mar 2010 19:20:02 GMT

I'm sure there will be others running into the same problem. Thanks for posting the fix.

topic SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3) in Data Protection

SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)

Re: SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)

Re: SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)