Bug 2009555 - Supermicro X11 system not booting from vMedia with AI
Summary: Supermicro X11 system not booting from vMedia with AI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.8
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: 4.10.0
Assignee: Jacob Anders
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks: 2025754
TreeView+ depends on / blocked
 
Reported: 2021-09-30 23:53 UTC by Dave Cain
Modified: 2022-03-10 16:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Release Note text: Previously, Ironic failed to attach virtual media images for provisioning SuperMicro X11/X12 servers because these models expect a non-standard device string ("UsbCd") for CD-based virtual media instead of more commonly used "Cd". This issue is fixed by overriding to "UsbCd" on SuperMicro machines provisioned with CD-based virtual media. (BZ#2009555) Cause: SuperMicro X11/X12 expects "UsbCd" device string for CD-based virtual media while "Cd" is commonly used. Consequence: Virtual media based provisioning fails on SuperMicro X11/X12. Fix: Override virtual media device string to "UsbCd" when a SuperMicro server is being provisioned from virtual media. Result: Virtual media based provisioning will succeed on SuperMicro X11/X12 machines.
Clone Of:
: 2025754 2025755 (view as bug list)
Environment:
Last Closed: 2022-03-10 16:14:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ironic-image pull 236 0 None open Enable vMedia provisioning of SuperMicro X11/X12 2021-11-19 04:24:21 UTC
OpenStack Storyboard 2009663 0 None None None 2021-11-05 13:25:14 UTC
OpenStack gerrit 817137 0 None NEW Changing boot device string for vmedia on SuperMicro 2021-11-10 00:04:07 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:15:06 UTC

Description Dave Cain 2021-09-30 23:53:30 UTC
Description of problem:
Supermicro X11 system can now attach ISOs from BMO in 4.8.13, although it looks like boot device management is having problems.  The node boots mounts vMedia okay, but boots off local storage.

Relevant component information and versioning:
Supermicro Chassis CSE-515-R407
Supermicro Board X11SPW-TF
Supermicro Firmware Version 01.73.06
Supermicro Firmware Build Time  11/20/2020
Supermicro Redfish Version 1.8.0
Supermicro BIOS Firmware Version 3.4
Supermicro SFT-DCMS-SINGLE license applied


Version-Release number of selected component (if applicable):
Red Hat OpenShift version 4.8.13
assisted-service-operator.v99.0.0-unreleased


How reproducible:
everytime


Steps to Reproduce:
1. Install Assisted Installer Operator, Hive, onto a 4.8 cluster as the hub or management cluster
2. Create an InfraEnv, AgentClusterInstall, ClusterDeployment, and BMH host files contingent for an OCP 4.8.13 deployment spoke cluster including Supermicro X11 system
3. Observe failure message for X11 system after kicking off install process


Actual results:
2021-09-30 22:42:21.361 1 DEBUG sushy.connector [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] HTTP response for POST https://172.28.11.40/redfish/v1/Managers/1/VirtualMedia/CD1/Actions/VirtualMedia.InsertMedia: status code: 202 _op /usr/lib/python3.6/site-packages/sushy/connector.py:185^[[00m
2021-09-30 22:42:21.361 1 INFO ironic.drivers.modules.redfish.boot [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] Inserted boot media http://10.40.0.122:6180/redfish/boot-71493915-2ac3-45d9-8fa0-883c27279a95.iso?filename=tmpkzbvdoyk.iso into cd for node 71493915-2ac3-45d9-8fa0-883c27279a95^[[00m
2021-09-30 22:42:21.372 1 DEBUG sushy.connector [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] HTTP request: GET https://172.28.11.40/redfish/v1/Systems/1/; headers: {'OData-Version': '4.0'}; body: None; blocking: False; timeout: 60; session arguments: {}; _op /usr/lib/python3.6/site-packages/sushy/connector.py:111^[[00m
2021-09-30 22:42:21.725 1 DEBUG sushy.connector [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] HTTP request: PATCH https://172.28.11.40/redfish/v1/Systems/1/; headers: {'Content-Type': 'application/json', 'OData-Version': '4.0'}; body: {'Boot': {'BootSourceOverrideTarget': 'Cd', 'BootSourceOverrideEnabled': 'Once'}}; blocking: False; timeout: 60; session arguments: {}; _op /usr/lib/python3.6/site-packages/sushy/connector.py:111^[[00m
/usr/lib/python3.6/site-packages/urllib3/connectionpool.py:847: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
2021-09-30 22:42:22.022 1 DEBUG sushy.connector [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] HTTP response for PATCH https://172.28.11.40/redfish/v1/Systems/1/: status code: 200 _op /usr/lib/python3.6/site-packages/sushy/connector.py:185^[[00m
2021-09-30 22:42:23.923 1 INFO ironic.conductor.utils [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] Node 71493915-2ac3-45d9-8fa0-883c27279a95 current power state is 'power off', requested state is 'power on'.^[[00m
2021-09-30 22:42:24.303 1 WARNING sushy.resources.system.system [req-4e7eadc1-6abe-4c34-b411-afc25a2a0226 ironic-user - - - -] Could not figure out the allowed values for the reset system action for System 1^[[00m
2021-09-30 23:19:34.355 1 DEBUG sushy.exceptions [req-adc923d5-68d1-4efe-ad84-5aaf13ff8953 ironic-user - - - -] HTTP response for GET https://172.28.11.40/redfish/v1/Systems/1/: status code: 401, error: Base.v1_4_0.GeneralError: While accessing the resource at /redfish/v1/Systems/1, the service received an authorization error unauthorized., extended: [{'MessageId': 'Base.1.4.ResourceAtUriUnauthorized', 'Severity': 'Critical', 'Resolution': 'Ensure that the appropriate access is provided for the service in order for it to access the URI.', 'Message': 'While accessing the resource at /redfish/v1/Systems/1, the service received an authorization error unauthorized.', 'MessageArgs': ['/redfish/v1/Systems/1', 'unauthorized'], 'RelatedProperties': ['unauthorized']}] __init__ /usr/lib/python3.6/site-packages/sushy/exceptions.py:122^[[00m



Expected results:
System boots to the ISO.
If I press F11 and tell the system to boot from the ISO, it works.

Comment 1 Derek Higgins 2021-10-05 16:09:57 UTC
Assigning to Jacob as he has been looking into this, 
Jacob would you mind triaging this please,

Comment 2 Jacob Anders 2021-10-07 01:47:10 UTC
(In reply to Derek Higgins from comment #1)
> Assigning to Jacob as he has been looking into this, 
> Jacob would you mind triaging this please,

Done, thank you Derek.

Comment 3 Dave Cain 2021-10-11 22:59:48 UTC
Looks like the same problem on Supermicro X12.

Comment 12 Jacob Anders 2021-11-18 23:02:14 UTC
https://review.opendev.org/c/openstack/sushy/+/817137 has merged, setting status to MODIFIED.

Backports to stable/xena and stable/wallaby are work in progress:
https://review.opendev.org/c/openstack/sushy/+/818369
https://review.opendev.org/c/openstack/sushy/+/818364

I am also working with Dave on a hotfix.

Comment 14 Dave Cain 2021-11-19 02:51:37 UTC
I've taken Jacob's patched Ironic and have used it to provision two different Supermicro SYS-210P-FRDN6T systems out of my lab.  These are Supermicro X12 models.

This allowed me to be able to mount the CD created by the assisted-service, and the systems indeed booted to it, and were recognized in the Assisted Installer.  This effectively is working for me.

Comment 15 Jacob Anders 2021-11-19 04:24:21 UTC
I raised a PR to have the merged sushy patch included in OCP4.10 ironic-image:

https://github.com/openshift/ironic-image/pull/236

Setting status back to POST as while the Sushy patch is merged upstream, the PR is not merged yet.

Comment 17 Jacob Anders 2021-11-19 21:01:50 UTC
https://github.com/openshift/ironic-image/pull/236 has now merged, updating status to MODIFIED.

Comment 20 Jacob Anders 2021-11-23 00:28:10 UTC
Hi Luba. Dave and I verified this in a remote session using method described in https://bugzilla.redhat.com/show_bug.cgi?id=2009555#c16.

Dave confirmed it worked https://bugzilla.redhat.com/show_bug.cgi?id=2009555#c14.

Would you be happy to mark this as VERIFIED/OtherQA based on the above?

Comment 21 Lubov 2021-11-23 06:23:07 UTC
суре(In reply to Jacob Anders from comment #20)
> Hi Luba. Dave and I verified this in a remote session using method described
> in https://bugzilla.redhat.com/show_bug.cgi?id=2009555#c16.
> 
> Dave confirmed it worked
> https://bugzilla.redhat.com/show_bug.cgi?id=2009555#c14.
> 
> Would you be happy to mark this as VERIFIED/OtherQA based on the above?

sure, many thanks

Comment 25 errata-xmlrpc 2022-03-10 16:14:46 UTC
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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.