Bug 1247512 - UI raises error "can't be blank' twice, on adding a 'Managed' BMC interface without mac
UI raises error "can't be blank' twice, on adding a 'Managed' BMC interface w...
Status: CLOSED WONTFIX
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Power & BMC (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: Lukas Zapletal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-07-28 04:10 EDT by Sachin Ghai
Modified: 2017-01-11 14:42 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-11 14:42:58 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
UI raises 'can't be blank' twice on configuring a BMC interface without mac (27.04 KB, image/png)
2015-07-28 04:10 EDT, Sachin Ghai
no flags Details

  None (edit)
Description Sachin Ghai 2015-07-28 04:10:08 EDT
Created attachment 1056958 [details]
UI raises 'can't be blank' twice on configuring a BMC interface without mac

Description of problem:
on adding new_interface without specifying mac, UI raises error:


can't be blank and can't be blank

This needs to be rephrased as just "can't be blank"

Version-Release number of selected component (if applicable):
sat6.1.1 GA snap14

How reproducible:
always

Steps to Reproduce:
1. new_host --> add 'managed' bmc interface without specifying mac and submit the form
2.
3.

Actual results:
On adding an interface without mac, UI raises error "can't be blank' twice,

Expected results:


Additional info:
Comment 2 Bryan Kearney 2017-01-11 14:42:58 EST
This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.

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