Bug 1317947 - engine-setup should default to not create NFS ISO domain
Summary: engine-setup should default to not create NFS ISO domain
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Yedidyah Bar David
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 15:03 UTC by Yedidyah Bar David
Modified: 2017-05-11 09:26 UTC (History)
2 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 07:48:38 UTC
oVirt Team: Integration
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1332813 0 unspecified CLOSED Deprecate the ISO domain setup on the RHEV-M machine (hide it in 4.0) 2021-02-22 00:41:40 UTC
oVirt gerrit 54760 0 master MERGED packaging: setup: Default to not configure an iso domain 2020-10-25 07:28:46 UTC

Internal Links: 1332813

Description Yedidyah Bar David 2016-03-15 15:03:50 UTC 
Description of problem:

$Subject.

Most installations probably prefer to use external storage also for that.

hosted-engine installations would suffer from worse performance, by having the iso domain served from inside the engine vm - if they have no dedicated storage server, they probably prefer to use one of their physical hosts for that.

Since we decided to not provide any default ACL (see bug 1110740), people that simply press 'Enter' accepting the defaults are prompted to provide an ACL, when they probably do not even want this domain or intend to use it, therefore have to start understanding the question and deciding about a proper answer.
Comment 1 Red Hat Bugzilla Rules Engine 2016-03-15 15:08:45 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 Karolína Hajná 2016-04-06 09:36:31 UTC 
Verified in ovirt-engine-4.0.0-0.0.master.20160404161620.git4ffd5a4.el7.centos.noarch
Comment 4 Sandro Bonazzola 2016-07-05 07:48:38 UTC 
oVirt 4.0.0 has been released, closing current release.
Note You need to log in before you can comment on or make changes to this bug.