Bug 1781017

Summary: Assigned compute profile shows 'VM Attributes' blank
Product: Red Hat Satellite Reporter: vijsingh
Component: Compute Resources - AzureAssignee: Aditi Puntambekar <apuntamb>
Status: CLOSED ERRATA QA Contact: vijsingh
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: apuntamb
Target Milestone: 6.7.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_azure_rm-2.0.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:27:49 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    
Attachments:
Description Flags
Screenshot none

Description vijsingh 2019-12-09 05:51:48 UTC
Created attachment 1643163 [details]
Screenshot

Description of problem:

Assigned compute profile shows 'VM Attributes' blank

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

@Satellite 6.7.0 snap 5.0

How reproducible:

Always

Steps to Reproduce:
1. Create a Compute Resource using AzureRM provider
2. Under created CR 'Compute Profile' tab select '1-small' (or any Compute profile) => Click on Submit
3. go to :

   Infrastructure => Compute Resources => Click on same created CR => 'Compute profiles' => See 'VM Attributes' for assigned CP(1-small)

Actual results:

 VM Attributes' shows blank

Expected results:

 Assigned 'VM Attributes' should show i.e. 'VM Size'

Additional info:

attached screenshot for reference

Comment 4 vijsingh 2019-12-17 09:40:27 UTC
ON_QA Verified

@Satellite 6.7.0 snap 6.0

Comment 7 errata-xmlrpc 2020-04-14 13:27:49 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