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:
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.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
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).
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
(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.
In the bz 1061611 I am talking about appearance - GUI, so not a duplicate
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.
Moti Asayag 2014-12-02 03:03:42 EST Assignee: masayag → alonbl how can I help?
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.
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.