Bug 1779009

Summary: VM properties widget is overlapping
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, zhunting
Target Milestone: 6.7.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
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:27:45 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:
Bug Depends On:    
Bug Blocks: 1775890    

Description vijsingh 2019-12-03 04:01:23 UTC
Description of problem:

VM properties widget is overlapping

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

@Satellite 6.7.0 Snap 4.0

How reproducible:


Steps to Reproduce:
1. On a already created VM.
 Hosts => All Hosts => click on VM name => under 'VM' tab.

Actual results:

 VM properties widget is overlapping

Expected results:

 VM properties widget should not overlap

Additional info:

Comment 3 Bryan Kearney 2019-12-03 05:00:31 UTC
Upstream bug assigned to apuntamb@redhat.com

Comment 4 Bryan Kearney 2019-12-03 05:00:32 UTC
Upstream bug assigned to apuntamb@redhat.com

Comment 5 Bryan Kearney 2020-01-22 21:00:37 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26499 has been resolved.

Comment 6 vijsingh 2020-02-11 10:09:48 UTC

@Satellite 6.7.0 snap 11.0

Observation:  VM properties widget does not overlap now.

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