Description of problem: My customer has run into this issue whilst building a new Baremetal cluster: Currently Ironic/sushy always attempt to set "Inserted" and "WriteProtected" properties in the payload of Redfish InsertMedia call to BMC. According to https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2021.1.pdf, these fields are optional and doing this is not necessary. The current behavior is breaking the baremetal installation in our situation: ERROR Error: could not inspect: could not inspect node, node is currently 'inspect failed' , last error was 'Failed to inspect hardware. Reason: unable to start inspection: HTTP POST https://xx.xx.xx.xx/redfish/v1/Managers/1/VirtualMedia/CD1/Actions/VirtualMedia.InsertMedia returned code 400. Base.v1_4_0.GeneralError: The property Inserted is not in the list of valid properties for the resource. Extended information: [{'MessageId': 'Base.1.4.PropertyUnknown', 'Severity': 'Warning', 'Resolution': 'Remove the unknown property from the request body and resubmit the request if the operation failed.', 'Message': 'The property Inserted is not in the list of valid properties for the resource.', 'MessageArgs': ['Inserted'], 'RelatedProperties': ['Inserted']}, {'MessageId': 'Base.1.4.PropertyUnknown', 'Severity': 'Warning', 'Resolution': 'Remove the unknown property from the request body and resubmit the request if the operation failed.', 'Message': 'The property WriteProtected is not in the list of valid properties for the resource.', 'MessageArgs': ['WriteProtected'], 'RelatedProperties': ['WriteProtected']}]' ERROR ERROR on ../../tmp/openshift-install-188611083/masters/main.tf line 1, in resource "ironic_node_v1" "openshift-master-host": ERROR 1: resource "ironic_node_v1" "openshift-master-host" { I can manually insert the media: curl -X POST https://xx.xx.xx.xx/redfish/v1/Managers/1/VirtualMedia/CD1/Actions/VirtualMedia.InsertMedia -d '{"Image": "http://xx.xx.xx.xx:8080/rhcos-48.84.202106301921-0-openstack.x86_64.iso", "UserName": "<user>", "Password":"<password>"}' -k -u <user>:<password> | python3 -m json.tool { "Accepted": { "code": "Base.v1_4_0.Accepted", "Message": "Successfully Accepted Request. Please see the location header and ExtendedInfo for more information.", "@Message.ExtendedInfo": [ { "MessageId": "SMC.1.0.OemIndicateDriveLedAcceptedMessage", "Severity": "Ok", "Resolution": "No resolution was required.", "Message": "Please also check Task Resource /redfish/v1/TaskService/Tasks/1 to see more information.", "MessageArgs": [ "/redfish/v1/TaskService/Tasks/1" ], "RelatedProperties": [ "VirtualMediaMountAccepted" ] } ] } } Hardware: Supermicro SuperServer 1029U-TN12RV https://www.supermicro.com/en/products/system/1U/1029/SYS-1029U-TN12RV.cfm Found a related bug: https://storyboard.openstack.org/#!/story/2009085 Version-Release number of selected component (if applicable): Baremetal OCP 4.8.10 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The upstream fix is https://opendev.org/openstack/sushy/commit/b76050c5c162e78572976dd4b199cab389d1d2d5, probably hasn't reached 4.8 yet.
Hi Andy, We have a fix for this in 4.9 (but the bz is not verified https://bugzilla.redhat.com/show_bug.cgi?id=1986238 so we can't backport to 4.8.z yet) I will check with my team if there is a way we can move forward to have the fix in 4.8 asap.
Thanks Lury we have passed this info on to the customer. Regards, Andy
Hi lury, Can confirm that the fix works in 4.9 tested with: Hardware: Supermicro SuperServer 1029U-TN12RV https://www.supermicro.com/en/products/system/1U/1029/SYS-1029U-TN12RV.cfm Regards, Paul Peereboom
Hi Paul, Thank you very much for testing the 4.9 in the Super Micro machine! I've already asked people in the 4.9 bz to see if we can now mark the bug as verified since you were able to test, so we can backport to 4.8
Hi Andy, when you have a chance can you test 4.8.13 ? (it contains the fix for virtual media in SuperMicro) Thank you!
Hi lury, I have asked Paul (who posted above) if he could test it next week, we will let you know how it goes. Regards, Andy
Awesome, thanks!
@
@andbartl and @imelofer would you be able to move this bug to either Verified or Closed so that it does not get included in the future Openshift z-stream release advisories.
Hi Roshni, Jacob will check if Dave tested 4.8.z so we can mark this bug as verified.
I can confirm that the WriteProtected / Inserted Media error went away in 4.8 based on my experiences in https://bugzilla.redhat.com/show_bug.cgi?id=1986238#c71. There are still issues with the complete end to end flow, but they are being looked at (and addressed) in different BZs: https://bugzilla.redhat.com/show_bug.cgi?id=2011626 https://bugzilla.redhat.com/show_bug.cgi?id=2009555
Thanks Dave! Can you share what 4.8 version you used? @andbartl do you mind if we mark this as verified? Since Dave tested I think it's ok (like he mentioned there are other SMC issues but not related to the fact that the attributes are not writable.)
4.8.13 for me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.8.19 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:4109