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

Bug 1422978

Summary: RFE: add /etc/hosts to backup for upgrade purposes
Product: Red Hat Enterprise Virtualization Manager Reporter: François Cami <fcami>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0.6CC: gklein, lsurette, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-16 18:25:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Sub-Eng RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description François Cami 2017-02-16 17:28:40 UTC
Description of problem:
When no DNS is available the /etc/hosts file should be identical on all hypervisors and engine.
However, this file is not backuped with engine-backup and therefore on upgrade it is not restored, leading to less-than-desirable behaviour.

Version-Release number of selected component (if applicable):
ovirt-engine-tools-backup-4.0.6.3-0.1.el7ev

NB: reported against ovirt-engine as ovirt-engine-tools-backup is not in the drop-down list.

How reproducible:
Always

Steps to Reproduce:
1. Install RHEV 3.6 with two hypervisors without DNS (use the hosts file instead)
2. Upgrade to RHV 4.0

Actual results:
The engine's host file only contains one hypervisor and the engine's FQDN, leading to loss of connectivity with all remaining hypervisors


Expected results:
Engine /etc/hosts kept during upgrade (and backup/restore btw).

Comment 1 Yaniv Kaul 2017-02-16 18:25:36 UTC
I see no reason to open an RFE for every file under /etc.
Duplicate of bug 1422980 (which I don't think we should implement either, as described there).

*** This bug has been marked as a duplicate of bug 1422980 ***