Bug 1326580

Summary: webUI shows compute-resource section to select network-type while adding BMC interface
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: ProvisioningAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 08:30:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
RHEV compute-resource section is displayed while adding BMC interface
none
libvirt CR section displayed while adding BMC interface none

Description Sachin Ghai 2016-04-13 07:24:57 UTC
Created attachment 1146729 [details]
RHEV compute-resource section is displayed while adding BMC interface

Description of problem: I was trying to add BMC interface and realized that webUI is showing CR section like 'Libvirt/RHEV' on adding BMC interface. I believe its not required for BMC interface


Version-Release number of selected component (if applicable):
sat6.2 beta snap7.1

How reproducible:


Steps to Reproduce:
1. Add a BMC interface
2.
3.

Actual results:
 CR section like 'Libvirt/RHEV' on adding BMC interface

Expected results:
CR section shouldn't be there on adding BMC interface

Additional info:
Please see screenshots

Comment 1 Sachin Ghai 2016-04-13 07:25:59 UTC
Created attachment 1146730 [details]
libvirt CR section displayed while adding BMC interface

Comment 3 Sachin Ghai 2016-04-13 07:54:18 UTC
Please note that this appears only if we try to add interface on a host which is going to be deployed on some compute-resource. Not for bare-metal.

Comment 4 Sachin Ghai 2016-04-13 08:30:06 UTC
I've a IRC discussion with dev. As per dev, this network section is required to which the 'virtual bmc' will connect. here is the chat snippet:

<mhulan> sghai: now when I think of it, BMC can make sense on virtual host, there might be some simple shell provider
<mhulan> sghai: so because of ssh provider I'd keep it for virtual hosts, which even rejects https://bugzilla.redhat.com/show_bug.cgi?id=1326580 I think
<mhulan> sghai: sorry I didn't realize it earlier... but it make sense to choose network to which this "virtual BMC" will be connected, ssh provider might use it for connection (I'm not sure it does today)


Closing this bz for now.