Bug 1779004

Summary: Host create using check enable/disable of 'Power ON this machine upon creation' does not care of it.
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, UserExperience
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: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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1775890    

Description vijsingh 2019-12-03 03:22:45 UTC
Description of problem:

Host create using check enable/disable of 'Power ON this machine upon creation' does not care of it.

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

@Satellite 6.7.0 snap 4.0

How reproducible:

Always

Steps to Reproduce:
1. Create host using check enable/disable of(Under Virtual Machine Tab) 'Power ON this machine upon creation' does not care of it.

Actual results:

 VM always gets 'Power On' after created Successfully on Azure Cloud.

Expected results:

 Disable 'Power ON this machine upon creation' should not Power on VM after created Successfully on Azure Cloud

Additional info:

Comment 6 vijsingh 2019-12-17 07:17:20 UTC
ON_QA Verified

@Satellite 6.7.0 snap 6.0

Steps/Observations:
 - 'Power ON this machine upon creation' with 'checkbox' is no more available.

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.

https://access.redhat.com/errata/RHSA-2020:1454