Bug 1785149 - Skip Orchestration steps when 'Import VM as managed host'
Summary: Skip Orchestration steps when 'Import VM as managed host'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-19 09:34 UTC by vijsingh
Modified: 2021-07-09 17:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-09 17:02:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description vijsingh 2019-12-19 09:34:56 UTC
Description of problem:

Skip Orchestration steps when 'Import VM as managed host' from all CRs which are supporting it.

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

@Satellite 6.7.0 snap 6.0

How reproducible:

Always

Steps to Reproduce:

1. Go to: Infrastructure => Compute Resources => Click on Created CR name 
2. Under 'Virtual Machines' tab => Click on any VM (which is not yet has any profile on Satellite) => Click 'Import as managed Host' => Submit


Actual results:

 Orchestration run for that host/vm , For more details on it check '/var/log/foreman/production.log' for run tasks
 
Expected results:

 Orchestration steps should not run for 'Import VM as managed host'

Additional info:

 Same is behaviour is checked/observed on : AzureRM , GCE , RHEV

Comment 6 Mike McCune 2021-07-09 17:02:24 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


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