| Summary: | Device install check for other device stability fails on win7 & 2k8R2 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | cshao <cshao> | ||||||||
| Component: | xenpv-win | Assignee: | Paolo Bonzini <pbonzini> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 5.7 | CC: | drjones, leiwang, mshao, pbonzini, rwu, vrozenfe, whuang | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-04-05 19:36:22 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 518435 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
cshao
2011-03-15 07:42:02 UTC
Created attachment 484386 [details]
Device Scan
Can you attach or link the whole .cpk file? Created attachment 485624 [details]
blk-win7-64.cpk
Attach blk-win7-64.cpk file.
Does the error still show for you in the submission status? The attached .cpk shows a pass for "Device Install Check for Other Device Stability". In this case, I believe it's better if you first rerun the test with EDO=3 and make it fail.
In any case, looks like we can apply for "Manual Errata #1856":
<ms-docs>
Issue Description
=================
If you are failing this test because the same device is being reported as ''added newly'' and ''removed'', then you may qualify for a manual errata. Please see ''Issue Resolution'' section.
Issue Resolution
================
From the logs, compare the device ID of the device that is being reported as
''added newly'', with the device ID of the device that is being reported as
''removed''. If the device IDs differ ONLY in their ''instance ID'' portion,
then you may qualify for manual errata #1856. Please refer to this errata id in
the readme file with your submission. Please contact support if you are unsure
if you qualify for this errata.
Example (note the difference in instance id):
* USB\VID_XXXX&PID_XXXX\6&991CE86&0&1 - Removed
* USB\VID_XXXX&PID_XXXX\6&991CE86&0&2 - Added newly
</ms-docs>
Here is our case instead:
* SCSI\DISK&VEN_RHEL&PROD_DISK\4&32FE5319&C&010001 - Removed
* SCSI\DISK&VEN_RHEL&PROD_DISK\4&32FE5319&D&010001 - Added newly
For both devices, the attributes are the same:
DeviceName RHEL DISK SCSI Disk Device
Description Disk drive
ProblemCode 0
Driver {4d36e967-e325-11ce-bfc1-08002be10318}
DriverName disk
IsDisabled False
IsFailedStart False
IsFailedInstall False
IsReinstallNeeded False
IsStarted True
Vadim, can you double check please that I'm correct?
In this case, Chen, please mark the cells in https://mirrorglass.englab.nay.redhat.com/XWiki/bin/view/xenpv-win-1.3.4-6/el5 as yellow or green while still referencing this bug.
(In reply to comment #4) > Does the error still show for you in the submission status? The attached .cpk > shows a pass for "Device Install Check for Other Device Stability". In this > case, I believe it's better if you first rerun the test with EDO=3 and make it > fail. > > In any case, looks like we can apply for "Manual Errata #1856": > > <ms-docs> > > Issue Description > ================= > If you are failing this test because the same device is being reported as > ''added newly'' and ''removed'', then you may qualify for a manual errata. > Please see ''Issue Resolution'' section. > > Issue Resolution > ================ > From the logs, compare the device ID of the device that is being reported as > ''added newly'', with the device ID of the device that is being reported as > ''removed''. If the device IDs differ ONLY in their ''instance ID'' portion, > then you may qualify for manual errata #1856. Please refer to this errata id in > the readme file with your submission. Please contact support if you are unsure > if you qualify for this errata. > > Example (note the difference in instance id): > * USB\VID_XXXX&PID_XXXX\6&991CE86&0&1 - Removed > * USB\VID_XXXX&PID_XXXX\6&991CE86&0&2 - Added newly > > </ms-docs> > > Here is our case instead: > > * SCSI\DISK&VEN_RHEL&PROD_DISK\4&32FE5319&C&010001 - Removed > * SCSI\DISK&VEN_RHEL&PROD_DISK\4&32FE5319&D&010001 - Added newly > > For both devices, the attributes are the same: > > DeviceName RHEL DISK SCSI Disk Device > Description Disk drive > ProblemCode 0 > Driver {4d36e967-e325-11ce-bfc1-08002be10318} > DriverName disk > IsDisabled False > IsFailedStart False > IsFailedInstall False > IsReinstallNeeded False > IsStarted True > > Vadim, can you double check please that I'm correct? I'm sure, you are. Best regards, Vadim. > > In this case, Chen, please mark the cells in > https://mirrorglass.englab.nay.redhat.com/XWiki/bin/view/xenpv-win-1.3.4-6/el5 > as yellow or green while still referencing this bug. (In reply to comment #4) > Does the error still show for you in the submission status? The attached .cpk > shows a pass for "Device Install Check for Other Device Stability". In this > case, I believe it's better if you first rerun the test with EDO=3 and make it > fail. > > In any case, looks like we can apply for "Manual Errata #1856": > Hi Paolo, Because I set EnumerateDevicesOverride=1 in other VM, this job can pass. So there is no error show in the submission status. But I think it is a wrong step for this job. After delete the pass job result, this error will show in the submission. Please see the new .cpk file. Thanks! Created attachment 485900 [details]
new cpk file for win764
|