Missing or invalid Resources do not result in a Fail

[jyundt]

Related to this redfishforum.com post, a defined Resource in an Interop Profile will not result in a Fail when that Resource is missing / not detected.

As an example, this profile provides as Pass as expected:

{
        "SchemaDefinition": "RedfishInteroperabilityProfile.v1_5_0",
        "ProfileName": "test",
	"ProfileVersion": "0.0.1",
        "Resources": {
                "Chassis": {
			"ReadRequirement": "Mandatory",
			"MinVersion": "1.0.1"
		}
	}
}

However, if I list a Resource that is not present, I'm not getting any type of Fail. Example:

{
        "SchemaDefinition": "RedfishInteroperabilityProfile.v1_5_0",
        "ProfileName": "test",
	"ProfileVersion": "0.0.1",
        "Resources": {
                "FOO": {
			"ReadRequirement": "Mandatory",
			"MinVersion": "1.0.1"
		}
	}
}

(edit: fixed typo for the "working" Chassis example)

[mraineri]

Definitely a bug; we'll need to look into this

[JordanCHW]

Hmm, I thought that's expected? Doesn't we only validate the resource requirement when that resource exists in the Redfish tree?

(I also found this before, for example we have some property requirements for resourceA, the validation would pass when the Redfish service reports 0 resources for resourceA. So I need to add MinCount requirement for resourceA's collection to ensure there're resources reported, then we could do further checks.)

[mraineri]

The default requirement on a resource is "Mandatory" when you stub it out like that. So, the expectation is at least one instance of the resource must exist. If you add "ReadRequirement: Recommended" at the root level of the resource definition, you can loosen it to be optional.

MinCount is used specifically for arrays. It is possible to achieve similar behavior by specifying "MinCount" in "Members" for a resource collection though.