Closed generatz closed 2 years ago
16:33:21 state:
16:41:05 [redfish]: 0
looks like redfish call to the BMC failed.
Having said that... @swe12345 when u have time , please check on it latter.
@generatz Sweta is out this week, so we will come back next week on this
I've also run this on HW and confirmed that the BMC is subsequently unreachable using IPv4 addressing. I recovered access by using ipmitool with the IPv6 address and restored the needed ipv4 parameters (this was a static ip setup).
Perhaps the use of IPv6 addressing for recovery could be incorporated into the Setup and Teardown.
@generatz I ran it on BMC. Seems to be working fine
bash-4.2$ curl -k -H "X-Auth-Token: $bmc_token" -X PATCH -D patch.txt -d '{"IPv4StaticAddresses":[{},{"Address": "xx.xx.xx.xx","SubnetMask": "xx.xx.xx.xx","Gateway":"xx.xx.xx.xx"}]}' https://$bmc/redfish/v1/Managers/bmc/EthernetInterfaces/eth0
Thanks, @swe12345. I had problems with my configuration for the BMC (hardware). It is working there now.
The (virtual) romulus bmc isn't conventionally networked (it is running on the same host as the Jenkins agent). I think it is for that reason that the test fails in one way or another, even after I tried to adjust the ip addresses.
In the end, after getting the patch to be accepted, the test failed when it attempted cat /usr/share/ipmi-providers/channel_config.json
via ssh.
Looks resolved.. Closing ticket
I ran the test_bmc_network_conf suite on romulus in qemu. Here is that piece of the Jenkins log:
The BMC is subsequently unreachable. It also looks as if it could cause similar problems with real hardware BMCs.
I'd like to see some added documentation and changes to the tests that address: