Bug 2013252

Summary:	kcs: How to set ioTimeout values in Windows
Product:	Container Native Virtualization (CNV)	Reporter:	Fabian Deutsch <fdeutsch>
Component:	Virtualization	Assignee:	Jean-Francois Saucier <jsaucier>
Status:	CLOSED ERRATA	QA Contact:	guy chen <guchen>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.9.0	CC:	cnv-qe-bugs, giridhar.ramaraju, ipinto, jsaucier, kbidarka, oramraz, sgott
Target Milestone:	---	Keywords:	TestCannotAutomate
Target Release:	4.9.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-13 19:59:01 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 Fabian Deutsch 2021-10-12 12:55:35 UTC

Description of problem:
IN some situations (slow network) with storagenetwork, we want to increase windows guests ioTimeout value.
Let's create a kcs for this to have this internally documented

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 10 Oded Ramraz 2021-12-11 15:16:12 UTC

Removing QE test coverage flag as this issue is doc bug and can't be tested automatically

Comment 15 errata-xmlrpc 2021-12-13 19:59:01 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 (OpenShift Virtualization 4.9.1 Images), 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/RHBA-2021:5091