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

Bug 1322515

Summary: The "Default" cluster doesn't have Display and Migration networks set out of the box
Product: [oVirt] ovirt-engine Reporter: jniederm
Component: BLL.NetworkAssignee: Yevgeny Zaspitsky <yzaspits>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.5CC: bugs, jniederm, mburman, sbonazzo
Target Milestone: ovirt-4.0.0-betaKeywords: Regression
Target Release: 4.0.0Flags: rule-engine: ovirt-4.0.0+
rule-engine: blocker+
rule-engine: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 07:56:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Manage networks dialog none

Description jniederm 2016-03-30 15:44:02 UTC
Created attachment 1141818 [details]
Manage networks dialog

Description of problem:
"Default" cluster misses Display and Migration networks by default.

Version-Release number of selected component (if applicable):
3.6 master, commit d35c04d1686850dd03

How reproducible:
100%

Steps to Reproduce:
1. Clean installation, or at least "Default" cluster the "Logical Networks" was not touched
2. Select "Default" cluster
3. Select "Logical Networks" subtab
4. Select "ovirtmgmt" and click "Manage Networks"
5. Columns "Migration network" and "Display Network" in "Manage networks" dialog

Actual results:
radio-buttons unchecked

Expected results:
radio-buttons checked

Additional info:
User created clusters has all three networks (Management, Display and Migration) selected by default

Comment 1 Dan Kenigsberg 2016-04-14 07:36:07 UTC
Are you sure you are testing ovirt-engine-3.6.0_alpha1-2538-gd35c04d the screenshot mentions clusterLevel 4.0.

Meni has just confirmed this bug in ovirt-engine 4ffd5a4.

Comment 2 Red Hat Bugzilla Rules Engine 2016-04-14 07:36:13 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 jniederm 2016-04-14 12:14:15 UTC
I can confirm this problem happens on my custom 3.6 build based on commit d35c04d1686850dd03 (as mentioned in comment 0), on RHEVM  3.6.5.3-0.1.el6, and - as the screenshot shows - on some version of 4.0.

Comment 4 Michael Burman 2016-06-08 09:28:34 UTC
Verified on - 4.0.0.2-0.1.el7ev

Comment 5 Sandro Bonazzola 2016-07-05 07:56:43 UTC
oVirt 4.0.0 has been released, closing current release.