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

Bug 1427478

Summary: RHVH can not be up in RHVM 4.0 side after upgrade to RHVH 4.1
Product: [oVirt] ovirt-node Reporter: jianwu <jiawu>
Component: Installation & UpdateAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED DUPLICATE QA Contact: jianwu <jiawu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1CC: bugs, cshao, dguo, gklein, huzhao, jiawu, leiwang, lsurette, rbalakri, rbarry, Rhev-m-bugs, srevivo, weiwang, yaniwang, ycui, ykaul, ylavi, yzhao
Target Milestone: ---Flags: cshao: testing_ack+
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-28 14:50:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
related log about this bug none

Description jianwu 2017-02-28 10:28:08 UTC 
Description of problem:
when register old bulid  RHVH 4.0 to rhevm 4.0, it cannot be up again after upgrade to RHVH 4.1 new build from engine side

Version-Release number of selected component (if applicable):
Before upgrade:
rhvh-4.0-0.20161116.0
After upgrade:
redhat-virtualization-host-4.1-20170222.0
cockpit-ws-126-1.el7.x86_64
cockpit-ovirt-dashboard-0.10.7-0.0.11.el7ev.noarch
imgbased-0.9.13-0.1.el7ev.noarch

How reproducible:
100%
Regression bug
Keywords: Upgrade

Steps to Reproduce:
1. Install RHVH 4.0 old build via anaconda GUI
2. Reboot and set local repo
3. Register to rhevm 4.0 and upgrade from rhevm side
4. Upgrade successfully and Reboot into new system
5. Check RHVH status in the side of rhevm

Actual results:
After step 5, RHVH 4.1 cannot be up in the side rhevm of 4.0

Expected results:
After step 5, RHVH 4.1 can be up in the side of rhevm 4.0

Additional info:
RHVH 4.1 could be up after register to rhevm 4.0 directly
Comment 1 jianwu 2017-02-28 10:30:35 UTC 
Created attachment 1258325 [details]
related log about this  bug
Comment 2 Ryan Barry 2017-02-28 14:50:23 UTC 
This appears to be a dupe. No service which relies on anything in /var could be started...

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