Bug 1322137

Summary: [RFE] Allow choosing if installed node should be activated or not
Product: [oVirt] ovirt-engine Reporter: nicolas
Component: RFEsAssignee: Martin Perina <mperina>
Status: CLOSED DEFERRED QA Contact: Lukas Svaty <lsvaty>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.4CC: bkorren, bugs, mperina
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: mperina: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-01 14:44:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description nicolas 2016-03-29 21:19:49 UTC 
It would be a great enhancement if administrators could choose whether they want to activate the node immediately after installation or should it be put on maintenance.

This might seem a triviality but in our case (and I guess most people) have different networks for different services. For example, for storage we have a bond interface of two physical interfaces and that's a different subnet than the one employed for service.

When a node is installed, immediately afterwards is activated. If we don't configure the bond mentioned above before installation, the node will try to mount storage using the only one configured interface, which will be rejected as it has no permissions to do so. This will result in node being stuck on different states (Activating, Connecting, Non operational...) which will in turn produce a few fencing attempts.

We can surely configure the bond manually so it doesn't hang, but it's much more comfortable to configure interfaces from the WebAdmin, but for that we need the host to be on maintenance and eventually not having been activated, so errors don't occur.

I think *reinstalling* the node already allows this (there's an option to not activate host upon reinstallation). Would you consider this useful to be added to the host installation dialog as well?
Comment 1 Yaniv Kaul 2017-03-12 16:06:32 UTC 
*** Bug 1348909 has been marked as a duplicate of this bug. ***
Comment 2 Michal Skrivanek 2020-03-19 15:40:44 UTC 
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
Comment 3 Michal Skrivanek 2020-04-01 14:44:07 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Comment 4 Michal Skrivanek 2020-04-01 14:49:15 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.