Bug 1793388 - Unable to click VM under CRs page VMs tab
Summary: Unable to click VM under CRs page VMs tab
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.7.0
Assignee: Aditi Puntambekar
QA Contact: vijsingh
Depends On:
Blocks: 1775890
TreeView+ depends on / blocked
Reported: 2020-01-21 08:46 UTC by Aditi Puntambekar
Modified: 2020-04-14 13:28 UTC (History)
1 user (show)

Fixed In Version: tfm-rubygem-foreman_azure_rm-2.0.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-04-14 13:28:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Foreman Issue Tracker 28814 Normal Closed Unable to click VM under CRs page VMs tab 2020-02-13 09:28:42 UTC
Red Hat Product Errata RHSA-2020:1454 None None None 2020-04-14 13:28:48 UTC

Description Aditi Puntambekar 2020-01-21 08:46:36 UTC
Description of problem:

Virtual Machine link under Compute Resources page in VM tab is disabled.

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

How reproducible:

Steps to Reproduce:
1. Go to Compute Resources page.
2. Select Virtual Machines tab

Actual results:
Link to Virtual Machine in the result table is disabled.

Expected results:
Link to Virtual machine should be enabled.

Additional info:

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

Comment 4 vijsingh 2020-02-10 10:12:43 UTC

@Satellite 6.7.0 Snap 11.0

Observation: Able to click on VM under CR.

Comment 7 errata-xmlrpc 2020-04-14 13:28:34 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.


Note You need to log in before you can comment on or make changes to this bug.