When configuring virtual media via RedFish on HP e910 server, if the URL specified isn't valid or reachable, the BMC still reports "Inserted": true. It seems it always reports "Inserted": true if there is any URL set.
Version:
Various, I recently reproduced this on latest (as per 25 January 2022) BIOS 1.90 and latest iLO 2.55.
How reproducible:
Steps to Reproduce:
1. Attach a vMedia image using an incorrect URL, e.g.
Property "Inserted": true is set despite this URL not being reachable from the BMC.
Expected results:
The BMC should reject the URL as it is not reachable and/or valid.
Additional info:
When the wrong URL is specified, the vMedia device is not visible in the OS. It only appears when a valid image is specified. I think "Inserted": true should be in line with what is visible in the OS.
Description of problem:
When configuring virtual media via RedFish on HP e910 server, if the URL specified isn't valid or reachable, the BMC still reports "Inserted": true. It seems it always reports "Inserted": true if there is any URL set.
Version:
Various, I recently reproduced this on latest (as per 25 January 2022) BIOS 1.90 and latest iLO 2.55.
How reproducible:
Steps to Reproduce:
1. Attach a vMedia image using an incorrect URL, e.g.
$ curl -X POST https:/ /HOST/redfish/ v1/Managers/ 1/VirtualMedia/ 2/Actions/ VirtualMedia. InsertMedia --user USER:PASS --insecure -d '{"Image": "https:/ /11.22. 33.44/iso/ file.iso"}' -H "Content-Type: application/json" | jq 10.ExtendedInfo ", ExtendedInfo for more information.", ExtendedInfo" : [
"MessageId" : "Base.1.4.Success"
{
"error": {
"code": "iLO.0.
"message": "See @Message.
"@Message.
{
}
]
}
}
2.Check configuration
$ curl -ksu USER:PASS https:/ /HOST/redfish/ v1/Managers/ 1/VirtualMedia/ 2 | jq v1/$metadata# VirtualMedia. VirtualMedia" , v1/Managers/ 1/VirtualMedia/ 2", v1_2_0. VirtualMedia" , dia.EjectMedia" : { v1/Managers/ 1/VirtualMedia/ 2/Actions/ VirtualMedia. EjectMedia" dia.InsertMedia ": { v1/Managers/ 1/VirtualMedia/ 2/Actions/ VirtualMedia. InsertMedia" /11.22. 33.44/iso/ file.iso", @odata. context" : "/redfish/ v1/$metadata# HpeiLOVirtualMe dia.HpeiLOVirtu alMedia" , @odata. type": "#HpeiLOVirtual Media.v2_ 2_0.HpeiLOVirtu alMedia" ,
"#HpeiLOVirtua lMedia. EjectVirtualMed ia": { v1/Managers/ 1/VirtualMedia/ 2/Actions/ Oem/Hpe/ HpeiLOVirtualMe dia.EjectVirtua lMedia"
"#HpeiLOVirtua lMedia. InsertVirtualMe dia": { v1/Managers/ 1/VirtualMedia/ 2/Actions/ Oem/Hpe/ HpeiLOVirtualMe dia.InsertVirtu alMedia" BootOnNextServe rReset" : false
{
"@odata.context": "/redfish/
"@odata.etag": "W/\"3E4155BE\"",
"@odata.id": "/redfish/
"@odata.type": "#VirtualMedia.
"Id": "2",
"Actions": {
"#VirtualMe
"target": "/redfish/
},
"#VirtualMe
"target": "/redfish/
}
},
"ConnectedVia": "URI",
"Description": "Virtual Removable Media",
"Image": "https:/
"ImageName": "file",
"Inserted": true,
"MediaTypes": [
"CD",
"DVD"
],
"Name": "VirtualMedia",
"Oem": {
"Hpe": {
"
"
"Actions": {
"target": "/redfish/
},
"target": "/redfish/
}
},
"
}
},
"WriteProtected": true
}
Actual results:
Property "Inserted": true is set despite this URL not being reachable from the BMC.
Expected results:
The BMC should reject the URL as it is not reachable and/or valid.
Additional info:
When the wrong URL is specified, the vMedia device is not visible in the OS. It only appears when a valid image is specified. I think "Inserted": true should be in line with what is visible in the OS.