Bug 1034706 - A user should be able to edit the MAC address of the hosted guest NIC _before_ being asked for the proposed FQDN of the engine once installed.
Summary: A user should be able to edit the MAC address of the hosted guest NIC _before...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-setup
Version: 3.3.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: 3.3.0
Assignee: Adam Litke
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks: GSS_RHEV_33_BETA
TreeView+ depends on / blocked
 
Reported: 2013-11-26 11:22 UTC by Lee Yarwood
Modified: 2014-01-21 16:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:55:30 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0083 0 normal SHIPPED_LIVE new package: ovirt-hosted-engine-setup 2014-01-21 21:42:22 UTC
oVirt gerrit 22112 0 None None None Never
oVirt gerrit 22125 0 None None None Never

Description Lee Yarwood 2013-11-26 11:22:47 UTC 
Description of problem:

A user should be able to edit the MAC address of the hosted guests NIC _before_ being asked for engines FQDN. The tool should ask if the auto generated MAC is acceptable or if the user would like to change this.

This would help guarantee the IP and FQDN of the guest of DHCP networks.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.0.0-0.9.beta4.el6ev.noarch

Actual results:
MAC address of the guest is auto generated and hidden from the user.

Expected results:
Mac address of the guest is auto generated, displayed and editable by the user.

Additional info:
Comment 1 Sandro Bonazzola 2013-12-06 14:39:54 UTC 
merged on upstream master and 1.0 branches.
Comment 4 errata-xmlrpc 2014-01-21 16:55: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.

http://rhn.redhat.com/errata/RHBA-2014-0083.html
Note You need to log in before you can comment on or make changes to this bug.