Bug 1678898

Summary: Run iotests in rhel77 qemu-kvm-ma build %check phase
Product: Red Hat Enterprise Linux 7 Reporter: Karen Mezick <kmezick>
Component: qemu-kvm-maAssignee: Karen Mezick <kmezick>
Status: CLOSED ERRATA QA Contact: Zhenyu Zhang <zhenyzha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7CC: areis, coli, jen, jsnow, juzhang, kmezick, ldoktor, mrezanin, ngu, qzhang, timao, virt-maint, ymankad
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-ma-2.12.0-24.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:00:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karen Mezick 2019-02-19 20:20:53 UTC
Description of problem:

RHEL77 (qemu-kvm-ma)

We want to run iotests as part of the brew build process in order to catch potential issues earlier in the development cycle.

The following iotests are stable at this time on RHEL77 (qemu-kvm-ma) and will be added to the build process.

All of these iotests are currently passing consistently.

This list does not include any iotests that take greater than 25 seconds to execute in the interest of not adding a significant amount of time to the build process.

The following code will be added to qemu-kvm.spec.template. The numbers represent the iotest name:

 ./check -v -raw 001 002 003 004 008 009 010 011 012 021 025 032 033 045 
                  048 052 077 101 104 106 113 120 140 143 145 147 157 159 
                  160 162 170 184 205 226 227 232

  ./check -v -qcow2 001 002 003 004 005 007 008 009 010 011 012 017 018 019 
                    020 021 022 024 025 027 029 031 032 033 034 035 036 037 
                    038 039 042 043 046 047 048 049 050 051 051 053 054 057 
                    058 061 062 063 065 066 068 069 072 073 074 082 086 087 
                    089 090 091 097 098 102 103 104 105 107 108 110 111 114 
                    117 120 126 130 133 134 137 140 143 145 147 150 157 158 
                    162 165 170 174 177 179 184 187 188 189 190 195 196 198 
                    202 203 204 205 206 209 214 216 217 223 226 227 232

  ./check -v -luks 001 002 003 004 008 009 010 011 012 021 032 033 052 140 
                   143 145 157 162 174 184 210 227

  ./check -v -nbd 001 003 004 008 009 010 021 032 033 045 077 104 119 123 143 
                  145 147 162 184 205

-------------------------------------------------------------

These are the iotests that were removed from the above list due to failure or long execution time:
    

    ./check -v raw
         Failures: 005 055 081 086 093 109 132 136 148 150
                   152 171 175 181 194 208 218 221 222
         Execution Times > 25 sec: 163 178
    
    ./check -v qcow2
         Failures: 028 030 040 041 055 056 067 085 095 096 124 127 129 132 
                   138 139 141 142 144 152 155 156 178 181 182 185 191 194 
                   200 201 208 218 219 222 229 234
         Execution Times > 25 sec: 013 014 015 023 026 044 060 079 080 112
                                   115 121 122 125 154 159 163 169 176

    ./check -v luks
         Failures: 005 149 181 208 218 226 232
         Execution Times > 25 sec: 025 048 205

    ./check -v nbd
         Failures: 002 005 011 055 083 093 094 132 136 
                   148 152 181 194 208 218 222
         Execution Times > 25 sec: 163

Comment 4 Miroslav Rezanina 2019-02-26 11:25:12 UTC
Fix included in qemu-kvm-ma-2.12.0-24.el7

Comment 6 Zhenyu Zhang 2019-03-01 09:29:04 UTC
Hi Karen Mezick:
I saw the code you added in qemu-kvm.spec.template and building qemu-kvm-ma-2.12.0-24.el7 successfully.
but How can I view the results of the iotest run during the build process?
Does iotest generate a log during the build process?

Comment 19 errata-xmlrpc 2019-08-06 13:00:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2019:2166