Bug 1369917 - VMs configured under vApps do not show in Satellite 6.2's compute resources
Summary: VMs configured under vApps do not show in Satellite 6.2's compute resources
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.2.0
Hardware: x86_64
OS: Linux
medium
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 17:40 UTC by Rick Dixon
Modified: 2021-12-10 14:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:03:29 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Rick Dixon 2016-08-24 17:40:10 UTC
Description of problem:

VMs configured under vApps do not show in Satellite 6.2's compute resources


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

6.2.1


How reproducible:

Always, in customer environment.


Steps to Reproduce:
1. Create a VMWare compute resource in Satellite 6.2
2. In the webUI, view your list of virtual machines under this compute resource; all configured under a vApp will not be shown in the list


Actual results:

While VMware VMs configured under vApps are still correctly reflected as content hosts or hosts, and their subscriptions are current, they are not listed under the VMWare compute resource


Expected results:

VMs configured under VMware vApps should show under the virtual machines list in the compute resource.

Comment 4 Mark Watts 2018-02-15 09:12:22 UTC
Just adding my support for this; we use vApps to control startup/shutdown ordering, so it would be beneficial to be able to issue vApp shutdown/poweron actions through Satellite (for after patching reboots particularly).

Comment 5 Bryan Kearney 2018-09-04 18:03:29 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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