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

Bug 1352098

Summary: imgbase check FAILED
Product: [oVirt] ovirt-node Reporter: Huijuan Zhao <huzhao>
Component: GeneralAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Huijuan Zhao <huzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0CC: bugs, cshao, dfediuck, dguo, huzhao, leiwang, rbarry, weiwang, yaniwang, ycui
Target Milestone: ovirt-4.0.1Flags: dfediuck: ovirt-4.0.z+
rule-engine: planning_ack+
dfediuck: devel_ack+
rule-engine: testing_ack+
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: imgbased-0.7.1-0.1.el7ev Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 06:22:38 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
All logs none

Description Huijuan Zhao 2016-07-01 15:23:45 UTC
Created attachment 1174967 [details]
All logs

Description of problem:
imgbase check FAILED after clean installation


Version-Release number of selected component (if applicable):
ovirt-node-ng-installer-ovirt-4.0-2016062804.iso
imgbased-0.7.0-0.201606081307gitfb92e93.el7.centos.noarch
ovirt-node-ng-image-update-placeholder-4.0.0-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install ovirt-node-ng-installer-ovirt-4.0-2016062804.iso via default ks.cfg in ISO
2. Reboot and login NGN
#imgbase check


Actual results:
1. After step 2, The status is FAILED:
[root@dell-op790-01 home]# 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 0x22d4848>': '/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


Expected results:
1. After step 2, there should be no FAILED nor error info


Additional info:

Comment 1 Ryan Barry 2016-07-01 16:43:35 UTC
I can't reproduce this. Can you provide the kickstart you're using?

Comment 2 Huijuan Zhao 2016-07-04 09:28:40 UTC
The kickstart is as follow:

# cat huzhao.ks 

liveimg --url=http://10.66.10.22:8090/rhevh/ngn/ovirt-node-ng-installer-ovirt-4.0-2016062804.iso/ovirt-node-ng-image.squashfs.img

clearpart --all

autopart --type=thinp

rootpw --plaintext redhat

timezone --utc Asia/Harbin

zerombr

text

reboot

%post --erroronfail
imgbase layout --init
imgbase --experimental volume --create /var 4G
%end

Comment 3 Ying Cui 2016-07-04 09:52:50 UTC
Additional info:
If installed the RHVH with ISO(RHEV-H-7.2-20160627.2-RHVH-x86_64-dvd1.iso) by default ks.cfg, still encountered this issue.

Comment 5 Red Hat Bugzilla Rules Engine 2016-07-07 23:12:58 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 Red Hat Bugzilla Rules Engine 2016-07-07 23:12:58 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 7 Red Hat Bugzilla Rules Engine 2016-07-07 23:14:09 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 8 Red Hat Bugzilla Rules Engine 2016-07-10 07:41:18 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 9 Huijuan Zhao 2016-07-11 06:40:45 UTC
Test version:
ovirt-node-ng-installer-ovirt-4.0-snapshot-2016071004.iso
imgbased-0.7.2-0.201607081443git3203932.el7.centos.noarch

Test steps:
1. Install ovirt-node-ng-installer-ovirt-4.0-snapshot-2016071004.iso
2. Reboot and login ovirt-node 4.0, check:
   # imgbase check

Test results:
After step 2, imgbase check status is ok:
[root@dhcp-10-16 ~]# imgbase check
Status: 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

So this bug is fixed in ovirt-node-ng-installer-ovirt-4.0-snapshot-2016071004.iso, I will change the status to VERIFIED if the status changes to ON_QA

Comment 10 Huijuan Zhao 2016-07-13 01:48:00 UTC
According to comment 9, I will change the status to VERIFIED.

Comment 11 Sandro Bonazzola 2016-07-19 06:22:38 UTC
Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.

For information on the release, and how to update to this release, follow the link below.

If the solution does not work for you, open a new bug report.

http://www.ovirt.org/release/4.0.1/