Bug 1219577

Summary: Hosts should be able to be created unmanaged from UI
Product: Red Hat Satellite Reporter: Justin Garrison <justin.garrison>
Component: HostsAssignee: Ohad Levy <ohadlevy>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: bbuckingham, bkearney, daniele, daobrien
Target Milestone: UnspecifiedKeywords: ReleaseNotes, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-13 20:52:30 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: 1190823    

Description Justin Garrison 2015-05-07 17:08:52 UTC
Description of problem: If I want to create an unmanaged host I have to first select a managed host (with os, arch, etc) and then edit the host and make it unmanaged. The API allows for creating a host unmanaged from the start.

It also might be helpful to have the UI clearly state what a managed v unmanaged and disassociated host is


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


How reproducible: always


Steps to Reproduce:
1. Create an unmanaged host without needing to specify OS

Actual results:


Expected results: Uncheck a box to manage the host during creation.


Additional info:

Comment 1 RHEL Program Management 2015-05-07 17:12:36 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 5 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 Bryan Kearney 2016-07-26 15:45:33 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 8 Bryan Kearney 2017-01-13 20:52:30 UTC
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.