Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1782777

Summary: Virtualmedia based drivers are not supported in BMC address
Product: OpenShift Container Platform Reporter: Jiri Tomasek <jtomasek>
Component: Console Metal3 PluginAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, ukalifon, vlaad, yanpzhan
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1782762 Environment:
Last Closed: 2020-05-26 16:50:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1782762    

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