Bug 1326728

Summary: Version scheme in imgbase layout should be similar after update
Product: [oVirt] ovirt-node Reporter: Fabian Deutsch <fdeutsch>
Component: Installation & UpdateAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED CURRENTRELEASE QA Contact: Huijuan Zhao <huzhao>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: bugs, ycui
Target Milestone: ovirt-4.0.0-rcFlags: rule-engine: ovirt-4.0.0+
huzhao: testing_plan_complete+
rule-engine: planning_ack+
fdeutsch: devel_ack+
ycui: testing_ack+
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-ng-installer-master-2016051700.iso Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-01 12:28:29 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:
Bug Depends On: 1340378, 1340382    
Bug Blocks:    
Attachments:
Description Flags
Screenshot showing the difference none

Description Fabian Deutsch 2016-04-13 11:31:19 UTC
Description of problem:
Currently the update procedure will create a new LV with a name which differes in the scheme from the name used for the initial LV name.

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

How reproducible:
always

Steps to Reproduce:
1. Install NGN, after installation focus on LV name
2. Update NGN, focus on new LV name
3.

Actual results:
LV names differ in the versioning scheme

Expected results:
LV names are similar in the versioning scheme

Additional info:

Comment 1 Fabian Deutsch 2016-04-13 11:31:54 UTC
Created attachment 1146828 [details]
Screenshot showing the difference

Comment 2 Sandro Bonazzola 2016-05-02 09:50:40 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 3 Fabian Deutsch 2016-05-17 11:56:23 UTC
The LV scheme is now the same for the image deployed during installaiton and on updates.

test steps:

1. Install NGN
2. Update NGN

After 2: Verify that the scheme (N-V-R) is the same for both images.

Comment 4 Huijuan Zhao 2016-06-02 06:41:31 UTC
I will verify this bug after Bug 1340378 is verified or downstream build can support upgrade.

Comment 5 Huijuan Zhao 2016-07-08 05:55:39 UTC
Test version:
1. Before upgrade:
ovirt-node-ng-installer-ovirt-4.0-2016062004.iso
imgbased-0.7.0-0.201606081307gitfb92e93.el7.centos.noarch
ovirt-node-ng-image-update-placeholder-4.0.0-1.el7.noarch
kernel-3.10.0-327.18.2.el7.x86_64
2. After upgrade:
imgbased-0.7.0-0.201606081307gitfb92e93.el7.centos.noarch
ovirt-node-ng-image-4.0.0-5.201606240219.el7.noarch
ovirt-node-ng-image-update-4.0.0-5.201606240219.el7.noarch
kernel-3.10.0-327.22.2.el7.x86_64

Test Steps:
1. Install NGN, after installation focus on LV name
2. Update NGN, focus on new LV name

Test results:
LV names are similar in the versioning scheme.
1. After step 1,
[root@dhcp-10-16 home]# lvs
  LV                                 VG              Attr       LSize   Pool   Origin                           Data%  Meta%  Move Log Cpy%Sync Convert
  home                               rhel_dhcp-10-16 Vwi-aotz-- 857.19g pool00                                  0.05                                   
  ovirt-node-ng-4.0.0-0.20160620.0   rhel_dhcp-10-16 Vwi---tz-k  50.00g pool00 root                                                                    
  ovirt-node-ng-4.0.0-0.20160620.0+1 rhel_dhcp-10-16 Vwi-aotz--  50.00g pool00 ovirt-node-ng-4.0.0-0.20160620.0 4.31                                   
  pool00                             rhel_dhcp-10-16 twi-aotz-- 907.23g                                         0.36   0.74                            
  root                               rhel_dhcp-10-16 Vwi-a-tz--  50.00g pool00                                  4.40                                   
  swap                               rhel_dhcp-10-16 -wi-ao----   7.75g                                                                                
  var                                rhel_dhcp-10-16 Vwi-aotz--   4.00g pool00                                  8.09 

2. After step 2,
[root@dhcp-10-16 ~]# lvs
  LV                                 VG              Attr       LSize   Pool   Origin                           Data%  Meta%  Move Log Cpy%Sync Convert
  home                               rhel_dhcp-10-16 Vwi-aotz-- 857.19g pool00                                  0.05                                   
  ovirt-node-ng-4.0.0-0.20160620.0   rhel_dhcp-10-16 Vwi---tz-k  50.00g pool00 root                                                                    
  ovirt-node-ng-4.0.0-0.20160620.0+1 rhel_dhcp-10-16 Vwi-a-tz--  50.00g pool00 ovirt-node-ng-4.0.0-0.20160620.0 6.57                                   
  ovirt-node-ng-4.0.0-0.20160624.0   rhel_dhcp-10-16 Vri---tz-k   4.49g pool00                                                                         
  ovirt-node-ng-4.0.0-0.20160624.0+1 rhel_dhcp-10-16 Vwi-aotz--   4.49g pool00 ovirt-node-ng-4.0.0-0.20160624.0 38.01                                  
  pool00                             rhel_dhcp-10-16 twi-aotz-- 907.23g                                         0.73   0.95                            
  root                               rhel_dhcp-10-16 Vwi-a-tz--  50.00g pool00                                  4.41                                   
  swap                               rhel_dhcp-10-16 -wi-ao----   7.75g 


So the bug is fixed, I will change the status to verified.