Bug 1364371 - Imgbase initiation fail when manual part as thinp in kickstart file.
Summary: Imgbase initiation fail when manual part as thinp in kickstart file.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-node
Classification: oVirt
Component: Installation & Update
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Fabian Deutsch
QA Contact: Wei Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-05 07:59 UTC by Wei Wang
Modified: 2016-09-19 08:23 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-19 08:23:04 UTC
oVirt Team: Node
Embargoed:
fdeutsch: ovirt-4.1?
rule-engine: planning_ack?
rule-engine: devel_ack?
cshao: testing_ack+


Attachments (Terms of Use)
ks file (2.57 KB, text/plain)
2016-08-05 07:59 UTC, Wei Wang
no flags Details
log file (155.11 KB, application/x-gzip)
2016-08-05 08:00 UTC, Wei Wang
no flags Details
install fail log file (102.13 KB, application/x-gzip)
2016-08-08 05:55 UTC, Wei Wang
no flags Details
new ks file (2.51 KB, text/plain)
2016-09-19 02:14 UTC, Wei Wang
no flags Details

Description Wei Wang 2016-08-05 07:59:50 UTC
Created attachment 1187794 [details]
ks file

Description of problem:
Imgbase initiation fail when manual part as thinp in kickstart file.

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160803.3.x86_64
imgbased-0.7.4-0.1.el7ev.noarch

How reproducible:
100%


Steps to Reproduce:
1. Install redhat-virtualization-host-4.0-20160803.3.x86_64 with kickstart file in attachment on FC machine
2. Login with root account
3. Check the imgbase status, and check command #imgbase layout


Actual results:
Imgbase initiation fail when manual part as thinp in kickstart file.
Last login: Fri Aug  5 15:10:36 2016 from vpn1-7-177.pek2.redhat.com

  imgbase status: DEGRADED
  Please check the status manually using `imgbase check`

[root@bootp-73-75-228 ~]# imgbase layout
rhvh-4.0-0.20160803.0



Expected results:
Imgbase initiation should be successful, imgbase status should be "OK"
#imgbase layout
rhvh-4.0-0.20160803.0
  +- rhvh-4.0-0.20160803.0+1


Additional info:
[root@bootp-73-75-228 ~]# imgbase check
Status: FAILED
Mount points ... FAILED - This can happen if the installation was performed incorrectly
  Separate /var ... OK
  Discard is used ... ERROR
    Exception in '<function check_discard at 0x1273c80>': KeyError('/var',) '/var'
Basic storage ... OK
  Initialized VG ... OK
  Initialized Thin Pool ... OK
  Initialized LVs ... OK
Thin storage ... OK
  Checking available space in thinpool ... OK
  Checking thinpool auto-extend ... OK

Comment 1 Wei Wang 2016-08-05 08:00:51 UTC
Created attachment 1187795 [details]
log file

Comment 2 Fabian Deutsch 2016-08-05 13:18:39 UTC
Please re-test this but do not use "imgbase --experimental volume --create /var 40G"

Comment 3 Wei Wang 2016-08-08 05:49:58 UTC
(In reply to Fabian Deutsch from comment #2)
> Please re-test this but do not use "imgbase --experimental volume --create
> /var 40G"

If removing the "imgbase --experimental volume --create /var 40G" from ks file, the installation will be failed.

Comment 4 Wei Wang 2016-08-08 05:55:48 UTC
Created attachment 1188535 [details]
install fail log file

Comment 5 Fabian Deutsch 2016-09-02 10:28:49 UTC
Please try:

Ensure to use kernel, intird, squashfs/stage2 from the latest ISO, then a kickstart like yours but with:

%post --erroronfail
imgbase layout --init
%end


# System bootloader configuration
bootloader --location=mbr
# Partition clearing information
clearpart --all
# Disk partitioning information
part pv.01 --ondisk=/dev/disk/by-id/scsi-36005076300810b3e0000000000000022 --size=100000
part pv.02 --ondisk=/dev/disk/by-id/scsi-36005076300810b3e0000000000000023 --size=50000
part /boot --ondisk=/dev/disk/by-id/scsi-36782bcb03cdfa2001ebc7e930f1ca244 --size=10000
volgroup testgroup pv.01 pv.02
logvol none  --size=120000 --thinpool --name=ngn_pool --vgname=testgroup
logvol /  --fstype="ext4" --size=30000 --thin --poolname=ngn_pool --name=root --vgname=testgroup
# ^^ HERE YOU NEED EXT4 or XFS
logvol swap  --fstype="swap" --size=2048 --thin --poolname=ngn_pool --name=swap --vgname=testgroup
logvol /var  --fstype="xfs" --size=80000 --thin --poolname=ngn_pool --name=data --vgname=testgroup
# ^^ HERE YOU NEED /var not /home on a separate vol

Comment 6 Wei Wang 2016-09-07 02:41:41 UTC
A problem about my environment is met, I need to research and debug it, so I will give the result later.

Comment 7 Ying Cui 2016-09-08 07:52:59 UTC
Setting needinfo back to avoid missing the test result for comment 6.

Comment 8 Wei Wang 2016-09-19 02:13:21 UTC
Test Version:
redhat-virtualization-host-4.0-20160916.0
imgbased-0.8.5-0.1.el7ev.noarch

Test Steps:
1. Install redhat-virtualization-host-4.0-20160916.0 with kickstart file in attachment on FC machine
2. Login with root account
3. Check the imgbase status, and check command #imgbase layout

Result:
Imgbase initiation is successful, imgbase status is "OK"
[root@hp-dl385g8-03 ~]# imgbase layout
rhvh-4.0-0.20160916.0
 +- rhvh-4.0-0.20160916.0+1

[root@hp-dl385g8-03 ~]# imgbase check
Status: OK
Bootloader ... OK
  Layer boot entries ... OK
  Valid boot entries ... OK
Mount points ... OK
  Separate /var ... OK
  Discard is used ... OK
Basic storage ... OK
  Initialized VG ... OK
  Initialized Thin Pool ... OK
  Initialized LVs ... OK
Thin storage ... OK
  Checking available space in thinpool ... OK
  Checking thinpool auto-extend ... OK

The bug cannot be reproduced with the latest build.

Comment 9 Wei Wang 2016-09-19 02:14:23 UTC
Created attachment 1202284 [details]
new ks file

Comment 10 Fabian Deutsch 2016-09-19 08:23:04 UTC
Closing according to comment 8.


Note You need to log in before you can comment on or make changes to this bug.