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

Bug 1079691

Summary: OVIRT35 - [RFE] Set 'save network configuration' default to 'true' on setup networks dialog
Product: [Retired] oVirt Reporter: Moti Asayag <masayag>
Component: ovirt-engine-webadminAssignee: Lior Vernia <lvernia>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: high    
Version: 3.5CC: bazulay, ecohen, gklein, iheim, lpeer, mburman, mgoldboi, rbalakri, yeylon
Target Milestone: ---Keywords: Improvement, Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: ovirt-3.5.0-alpha1.1 Doc Type: Release Note
Doc Text:
The "Save Network Configuration" check box is now marked by default, due to users' configurations being wiped by accident; please pay attention to uncheck it when experimenting.
Story Points: ---
Clone Of:
: 1114241 (view as bug list) Environment:
Last Closed: 2014-10-17 12:44:57 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:
Bug Depends On:    
Bug Blocks: 1114241    

Description Moti Asayag 2014-03-23 06:46:39 UTC
With the setup networks dialog, a complex network configuration can be set at once, by specifying the target settings.

It makes sense that the default of the 'save network' action in that context will be marked as true.

An advanced approach will be persisting the network changes automatically as done by the engine for any network label-based configuration and as suggested on [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1043018#c3

Comment 1 lpeer 2014-03-23 07:05:44 UTC
The bug was reported as a result of BenRitter88 twit -
https://twitter.com/BenRitter88/status/447512219253612544/photo/1

Comment 2 Sandro Bonazzola 2014-10-17 12:44:57 UTC
oVirt 3.5 has been released and should include the fix for this issue.