Bug 1786700

Summary:	VM created using hammer default take 'OS Disk Caching' value 'ReadWrite'
Product:	Red Hat Satellite	Reporter:	vijsingh
Component:	Compute Resources - Azure	Assignee:	Aditi Puntambekar <apuntamb>
Status:	CLOSED ERRATA	QA Contact:	vijsingh
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	apuntamb, zhunting
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_azure_rm-2.0.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:28:12 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:
Bug Depends On:
Bug Blocks:	1775890

Description vijsingh 2019-12-27 10:39:47 UTC

Description of problem:

VM created using hammer default take 'OS Disk Caching' value 'ReadWrite'

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

@Satellite 6.7.0 snap 7.0

How reproducible:

Always

Steps to Reproduce:
1. Create a host using Azure CR using hammer
2. Once VM is created check 'OS Disk Caching' on UI for same host.


Actual results:

  Hosts 'OS Disk Caching' shows 'ReadWrite'


Expected results:

 This behaviour should be same as UI and value should be 'None' by default

Additional info:

Comment 4 Bryan Kearney 2020-01-22 21:03:52 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28772 has been resolved.

Comment 5 vijsingh 2020-02-11 10:06:19 UTC

Verified

@Satellite 6.7.0 snap 11.0

Observation: Default behaviour 'ReadWrite' now for 'OS Disk Caching' on UI as well.

Comment 8 errata-xmlrpc 2020-04-14 13:28:12 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-2020:1454