I believe this is a TLS issue that was identified by another community member. Take a look at this change: https://gerrit.akraino.org/r/#/c/552/
To test, you could change the HPE_GIT value in buildrc to match the change above, delete the /opt/akraino/hpe directory and run setup_tools.sh in /opt/akraino/redfish.
I am using HP-G10 for regional controller. And during installation red fish is installed on the build server to boot strap HP-G10. The redfish getting installed through the installation process is not working and fails with following error.
[172.27.43.204]. Beginning in 10 seconds ..........
Beginning create and apply json file to server at Tue Mar 26 18:42:11 IST 2019
Creating server BIOS/RAID settings file [/opt/akraino/server-config/aknode44.hpe_dl380_g10_uefi_base.json] for server [aknode44]
Applying server settings file [/opt/akraino/server-config/aknode44.hpe_dl380_g10_uefi_base.json] to [172.27.43.204]
This step could take up to 10 minutes
Traceback (most recent call last):
File "/opt/akraino/redfish/set_hpe_config.py", line 250, in <module>
raise excp
redfish.rest.v1.RetriesExhaustedError
ERROR: failed applying server BIOS/RAID settings
root@labadmin-virtual-machine:~#
Also manual testing of red fish does now work. Here as if red fish is installed from
https://github.com/HewlettPackard/python-ilorest-library works fine.
root@aknode80:/opt/akraino/hpe/examples# python quickstart_redfish.py
404
content-length 909
keep-alive timeout=60, max=100
x-frame-options DENY
server iDRAC/9
connection Keep-Alive
cache-control no-cache
date Fri, 29 Mar 2019 22:11:01 GMT
odata-version 4.0
access-control-allow-origin *
content-type application/json;odata.metadata=minimal;charset=utf-8
www-authenticate Basic realm="RedfishService"