Bug 1782777 - Virtualmedia based drivers are not supported in BMC address
Summary: Virtualmedia based drivers are not supported in BMC address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Metal3 Plugin
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.4.z
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks: 1782762
TreeView+ depends on / blocked
 
Reported: 2019-12-12 10:24 UTC by Jiri Tomasek
Modified: 2020-05-26 16:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1782762
Environment:
Last Closed: 2020-05-26 16:50:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3749 0 None closed Add support for additional drivers in BMC addess validation 2020-06-18 13:28:37 UTC
Red Hat Product Errata RHBA-2020:2180 0 None None None 2020-05-26 16:50:53 UTC

Description Jiri Tomasek 2019-12-12 10:24:33 UTC 
+++ This bug was initially created as a clone of Bug #1782762 +++

Description of problem:
Virtualmedia based drivers are not supported in BMC address 


Version-Release number of selected component (if applicable):


How reproducible:
100%


Steps to Reproduce:
1. Navigate to Bare Metal Hosts and click Add Host
2. Fill in BMC Address field with 'idrac-virtualmedia://192.168.111.1:6235'

Actual results:
Field renders invalid


Expected results:
Field is accepted as valid


Additional info:
Comment 3 Yanping Zhang 2020-05-21 06:36:45 UTC 
Checked on 4.4 cluster with payload: 4.4.0-0.nightly-2020-05-18-164758
Create BM host by "Add Host", Fill in BMC Address field with 'idrac-virtualmedia://192.168.111.1:6235', the input is valid, after set other fields, click "Create", could succeed.
Comment 6 errata-xmlrpc 2020-05-26 16:50:30 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, 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-2020:2180
Note You need to log in before you can comment on or make changes to this bug.