Bug 1576783

Summary: Engine VM MAC address is hard-coded
Product: [oVirt] cockpit-ovirt Reporter: Phillip Bailey <phbailey>
Component: Hosted EngineAssignee: Phillip Bailey <phbailey>
Status: CLOSED CURRENTRELEASE QA Contact: Yihui Zhao <yzhao>
Severity: high Docs Contact:
Priority: high    
Version: 0.11.20CC: bugs, cshao, huzhao, jiaczhan, qiyuan, rbarry, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
cshao: testing_plan_complete?
yzhao: testing_ack+
Target Release: 0.11.25   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.11.25-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:35:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1582207    

Description Phillip Bailey 2018-05-10 11:55:02 UTC
Description of problem:
The engine VM MAC address is hard-coded in the Cockpit wizard, but should be randomly generated.

Version-Release number of selected component (if applicable):
cockpit-ovirt-0.11.23-1

How reproducible:
100%

Steps to Reproduce:
1. Install hosted engine via the Cockpit hosted engine wizard

Actual results:
The engine VM MAC address is not randomly generated.

Expected results:
A unique, randomly generated address should be created for each run of the wizard.

Comment 1 Yihui Zhao 2018-05-30 01:24:55 UTC
Can reproduce with cockpit-ovirt-0.11.23-1.

Comment 2 Yihui Zhao 2018-05-30 01:26:19 UTC
Tested with cockpit-ovirt-0.11.25-1:

Randomly generated address was created for each run of the HE wizard.

So, change the bug's status to verified.

Comment 3 Sandro Bonazzola 2018-06-26 08:35:53 UTC
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.