You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This assertion is strange. It fails when Sessions has no members. If we post a new session, it passes. But for EventDestination Collection which has no member as well, it passes.
URI
Members
Result
/redfish/v1/SessionService/Sessions
No
FAIL, property Members@odata.nextLink should be present in the resource Root Service_Links_Sessions
Yes
PASS
/redfish/v1/EventService/Subscriptions
No
PASS
Yes
PASS
Look source code of Assert 6.5.23.1 and find the if statementif count<=member_count: taking true when a collection has no members (count = member_count = 0), and check whether there's next link property. It does not make sense the next link property be present in this case.
The count is not reset for each iteration, so the result would be incorrect. This is why the assertion passes when there's no member in EventDestination collection.
>> loop N-1
Resource uri: /redfish/v1/Registries
count = 36, member_count = 4
>> loop N
Resource uri: /redfish/v1/EventService/Subscriptions
count = 36, member_count = 0 <-- the count should be zero
The text was updated successfully, but these errors were encountered:
This assertion is strange. It fails when Sessions has no members. If we post a new session, it passes. But for EventDestination Collection which has no member as well, it passes.
Look source code of Assert 6.5.23.1 and find the if statement
if count<=member_count:
taking true when a collection has no members (count = member_count = 0), and check whether there's next link property. It does not make sense the next link property be present in this case.The count is not reset for each iteration, so the result would be incorrect. This is why the assertion passes when there's no member in EventDestination collection.
The text was updated successfully, but these errors were encountered: