Bug 1062136

Summary:	[Neutron integration] Reinstall of the host doesn't keep Network provider configuration that existed on the Host
Product:	[oVirt] ovirt-engine	Reporter:	GenadiC <gcheresh>
Component:	General	Assignee:	Barak <bazulay>
Status:	CLOSED EOL	QA Contact:	GenadiC <gcheresh>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bazulay, bugs, dougsland, ecohen, gcheresh, gklein, lsurette, masayag, oblaut, rbalakri, sbonazzo, yeylon, ylavi
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-02 10:37:33 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:	1063716

Description GenadiC 2014-02-06 09:38:25 UTC

Description of problem:
If you configure Network Provider configuration when adding the Host to the setup and then try to reinstall the Host, the Network Provider configuration is not solved for reinstall and you need to reconfigure it again

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Configure Network Provider configuration when adding a Host to a Setup
2. Pick reinstall option from GUI for that host 
3.

Actual results:
You need to reconfigure Network Provider fields again

Expected results:
Reinstall should keep Network Provider configuration

Additional info:

Comment 1 Itamar Heim 2014-02-09 08:53:01 UTC

Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-04 09:23:21 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Mike Kolesnik 2014-03-10 09:19:28 UTC

Closing due to a number of reasons:

1. Since this information is not reported by the host there is no way to know if it wasn't changed out of band, so there is no point to keep stale data in the host.
2. This is install only parameter that is necessary only during the installation, like the host password. It has no use out of that scope.
3. If admin would like to change these parameters I don't believe he will reinstall the host, but instead would change them on Neutron (or an RFE can be opened to allow it via setup networks command).

Comment 4 GenadiC 2014-03-17 08:08:57 UTC

If something got wrong with the host and I want to reinstall it, I want to keep the Neutron provider that was installed with Host

Comment 5 Moti Asayag 2014-05-02 12:28:27 UTC

(In reply to GenadiC from comment #4)
> If something got wrong with the host and I want to reinstall it, I want to
> keep the Neutron provider that was installed with Host

Wouldn't that make this bug a duplicate of Bug 1061611 [Neutron] Network provider field is missing for installed host ?

If yes - please close as duplicate, else please describe the differences.

Comment 6 GenadiC 2014-05-04 07:13:19 UTC

In the bz 1061611 I am talking about appearance - GUI, so not a duplicate

Comment 7 Sandro Bonazzola 2014-05-08 13:56:37 UTC

This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 8 Alon Bar-Lev 2014-12-02 08:05:22 UTC

 Moti Asayag 2014-12-02 03:03:42 EST
Assignee: masayag → alonbl

how can I help?

Comment 9 Sandro Bonazzola 2015-09-04 09:03:05 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 10 Sandro Bonazzola 2015-10-02 10:37:33 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained
anymore.
Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still
an issue.