Created attachment 968832 [details] tmp-ovirt.log
Created attachment 968834 [details] cciss-auto-failed.png
Can you please also provide /tmp/ovirt.log?
Hi fabiand, All log already uploaded. /var/log/*.( /tm/ovirt.log Please see #c 1. Thanks!
Thanks! Can we also get access to that machine?
There are many errors in the log: Buffer I/O error on device cciss/c0d0, logical block 1 Buffer I/O error on device cciss/c0d0, logical block 2 cciss 0000:50:08.0: cmd ffff88007fac0280 has CHECK CONDITION sense key = 0x3 … Buffer I/O error on device sr0, logical block 118589 Buffer I/O error on device sr0, logical block 118590 Buffer I/O error on device sr0, logical block 118591 Buffer I/O error on device sr0, logical block 118592 Buffer I/O error on device sr0, logical block 118593 Buffer I/O error on device sr0, logical block 118594 Buffer I/O error on device sr0, logical block 118595 Buffer I/O error on device sr0, logical block 118596 Buffer I/O error on device sr0, logical block 118597 SQUASHFS error: squashfs_read_data failed to read block 0xa9ced39 SQUASHFS error: Unable to read data cache entry [a9ced39] SQUASHFS error: Unable to read page, block a9ced39, size 12065 SQUASHFS error: Unable to read data cache entry [a9ced39] SQUASHFS error: Unable to read page, block a9ced39, size 12065 Please verify: + That the ISO is not corrupted + That the hardware is okay + That RHEL can boot and no errors are in dmesg
Created attachment 969581 [details] 1212-cciss.tar.gz
The cause for this bug is an incorrect multipath configuration. It seems that some of our changes, collide with changes from other packages.
One way to rule out the error source network: Can you please try to reproduce this bug which a USB media install?
Created attachment 970366 [details] new1212.tar.gz
Chen, comment 13 does not help me at all. I need logs! dmesg, /var/log/messages /var/log* ... Otehrwise I can not help. Also: It seems as if the test env is on the cciss machine, and it is installed. Could you please elaborate and explain a bit more why this is, if you say that it fails to instzall on a cciss machine?
Created attachment 971148 [details] sosreport log for comment13
Fabian, I setup another new CCISS machine to grab the new logs and paste here the one by one steps on pic. see the below: sosreport-hp-bl465cg5-01-20141219130528-b2da.tar.xz, cciss_step1/step2/step3/setep4.
Created attachment 971149 [details] sosreport for comment 14
Created attachment 971150 [details] /tmp/log for comment 14
Created attachment 971151 [details] step1
Created attachment 971152 [details] cciss_step2
Created attachment 971153 [details] cciss_step3
Created attachment 971155 [details] cciss_step4 error happend
(In reply to Fabian Deutsch from comment #14) > Chen, comment 13 does not help me at all. > > I need logs! > dmesg, /var/log/messages /var/log* ... Otehrwise I can not help. > > Also: It seems as if the test env is on the cciss machine, and it is > installed. Could you please elaborate and explain a bit more why this is, if > you say that it fails to instzall on a cciss machine? Hi fabiand, yes, the env is on cciss machine, and rhevh is not installed, for you can ssh access conveniently, so I configured network connection and TUI menu via run"setup" command on shell mode , therefore it looked like installed but actually not. Thanks! Hi ycui, Thank you for the clarification and log info. Thanks!
Created attachment 972253 [details] var.log.tar.gz Upload /var/log/*.* for #c23.
Created attachment 972733 [details] ccisslog.tar.gz
(In reply to shaochen from comment #27) > Created attachment 972733 [details] > ccisslog.tar.gz This log is for #c26.
Please note that this bug covers several problems, mainly it mixes up a failure to install on cciss during auto-install (see comment 0 / description) and during tui install (see comment 26), with different errors. Additionally it seems to include logs from a hardware related installation failure (see comment 6).
Removing one patch. because it does not seem to be absolutely necessary.
Test version: rhev-hypervisor6-6.6-20150105.0 ovirt-node-3.1.0-0.39.20150105gitb784105.el6.noarch Test steps: 1. TUI Install RHEV-H on cciss machine. Test result: Install the hypervisor on cciss machine can succeed. So I will verify this bug after status change to ON_QA
Test version: rhev-hypervisor6-6.6-20150123.2 ovirt-node-3.2.1-6.el6.noarch Test steps: 1. TUI Install RHEV-H on cciss machine. Test result: Install the hypervisor on cciss machine can succeed. So the bug has been fixed, change bug status to VERIFIED.
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://rhn.redhat.com/errata/RHEA-2015-0160.html