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:
Created attachment 1146828 [details] Screenshot showing the difference
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
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.
I will verify this bug after Bug 1340378 is verified or downstream build can support upgrade.
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.