Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script halt due to "TypeError: argument of type 'NoneType' is not iterable" #118

Closed
jacktan888 opened this issue May 11, 2018 · 3 comments
Closed

Comments

@jacktan888
Copy link

Hi,
The test stopped due to TypeError while running to Assertion 6.1.8.1. Please see attachment for detail output. Please advice how to resolve it?

Thanks.

Jack Tan.
ConformanceOutput.txt

@billdodd
Copy link
Contributor

Jack,

It looks like the test run had a more fundamental problem connecting to your service. It was getting connection reset errors from the /redfish, /redfish/v1/ and /redfish/v1/$metadata endpoints, so was unable to gather the service URIs to validate. From the beginning of your log:

Setting up Redfish Service Check Tool Revision: 01.05.17 : OpenPowerP9:172.31.56.169
OPERATIONAL ERROR: GET Request for /redfish FAILED with exeption: <class 'ConnectionResetError'>
Protocol version and Service Root uri could not be retrieved through '/redfish', assuming spec mandated values
OPERATIONAL ERROR: GET Request for /redfish/v1/odata FAILED with exeption: <class 'ConnectionResetError'>
OPERATIONAL ERROR: GET Request for /redfish/v1/ FAILED with exeption: <class 'ConnectionResetError'>

Collecting all relative uris from Service Root: /redfish/v1/
OPERATIONAL ERROR: GET Request for /redfish/v1/ FAILED with exeption: <class 'ConnectionResetError'>

Serializing SUT metadata document: /redfish/v1/$metadata ...
OPERATIONAL ERROR: GET Request for /redfish/v1/$metadata FAILED with exeption: <class 'ConnectionResetError'>
Unable to parse Service Metadata Document /redfish/v1/$metadata

Can you double-check the config information in the SUTs section of the properties.json file to be sure it is correctly specifying the target system? If that looks OK, you can then try accessing those endpoints with tools like curl or Postman to diagnose further.

@mraineri
Copy link
Contributor

@jacktan888 any update on @billdodd's request?

@jacktan888
Copy link
Author

Hi @billdodd @mraineri , the target was correctly set.
This issue has been resolved by newly update code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants