#64 RBA extrinsic Method are not tested

[Akash_Malhotra]

since condition is false. Although RI supports RBA extrinsic method, since condition is false, OTM will never test it.

See section 7.2 and 7.2.1 of DSP 1039 along with Section 8 conditions.

Soon OTM will start failing

[Akash_Malhotra]

Logged In: YES
user_id=1720313
Originator: YES

In order words, it is a static role

[Thomas Weber]

Logged In: YES
user_id=1857294
Originator: NO

Authorized Role Management is not supported by RI 1.0.3. DRI_Role "role1" therefor has RoleCharacteristics value 2 (static) set, see developers manual. Due to DSP1039 7.2.1 this is spec compliant. OTM should be able to handle static methods.

[Akash_Malhotra]

Logged In: YES
user_id=1720313
Originator: YES

It is perfectly legitimate under the constraints of specification. OTM handle this situation well and it does not execute the method. If we claim support of supporting CreateRole, DeleteRole and ModifyRole, then RoleCharateristic value cannot be 2.

OTm wil not verify these methods.

[Thomas Weber]

Logged In: YES
user_id=1857294
Originator: NO

CreateRole, DeleteRole and ModifyRole are not supported by RI, so RoleCharateristic IMHO has to be 2 (static).
What behavior other than this do you expect? Or in other words, what needs to be done to prevent OTM from failure?

[Navin Boppuri]

Logged In: YES
user_id=2002123
Originator: NO

Thomas,

According to the list that you recently sent of all extrinsic methods, at least CreateRole and DeleteRole show up as "Implemented" features in RI (see below). And now you are claiming that these are NOT supported by RI. Can you please clarify?

Implemented:

DRI_BootConfigSetting ChangeBootOrder
DRI_BootService ApplyBootConfigSetting
DRI_ComputerSystem RequestStateChange
DRI_Fan RequestStateChange
DRI_Fan Reset
DRI_Fan SetSpeed
DRI_Memory Reset
DRI_NumericSensor RequestStateChange
DRI_NumericSensor Reset
DRI_NumericSensor RestoreDefaultThresholds
DRI_PowerManagementService RequestPowerStateChange
DRI_PowerSupply RequestStateChange
DRI_PowerSupply Reset
DRI_ProcessorCore RequestStateChange
DRI_RedundancySet Failover
DRI_RoleBasedAuthorizationService AssignRoles
<!--DRI_RoleBasedAuthorizationService CreateRole -->
<!-- DRI_RoleBasedAuthorizationService DeleteRole -->
DRI_Sensor RequestStateChange
DRI_Sensor Reset

[Thomas Weber]

Logged In: YES
user_id=1857294
Originator: NO

I'm sorry I got things mixed up a bit.
The current implementation of Authorized Role Management is experimental and incomplete, that's why we decided to not use it for emulation. Although CreateRole and DeleteRole extrinsic methods are implemented, we would like to state them not supported. So they do not need to be tested.

[Navin Boppuri]

Logged In: YES
user_id=2002123
Originator: NO

I believe this issue still exists for v1.0.6. It is not a high priority issue to be fixed but the bug may be kept open for tracking purposes.

[Navin Boppuri]

Logged In: YES
user_id=2002123
Originator: NO

Akash: OTM is still looking into this issue. At present there is an issue with OTM and we are resolving it. Cannot comment on how RI will respond after the fix.