Bug 1245642
| Summary: | [RFE] Allow editing of taxonomy for discovered hosts | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Alexander Braverman <abraverm> | ||||
| Component: | Discovery Plugin | Assignee: | Lukas Zapletal <lzap> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Daniel Lobato Garcia <dlobatog> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.1.0 | CC: | bbuckingham, bkearney, bkorren, cwelton, dlobatog, kdixon, lzap, mwade, will_darton | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/4426 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-02-21 12:29:34 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: | 1338516 | ||||||
| Attachments: |
|
||||||
|
Description
Alexander Braverman
2015-07-22 12:54:49 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. Hello, in 6.1 we have actually introduced org/loc (we call a taxonomy) for discovery rules. Does this solve your requirement? I don't see how to apply the taxonomy on discovery rules in Satellite 6.1.1 Available fields for a new rule are: - Name - Search - Host Group - Hostname - Template - Hosts limit - Priority - Enabled Taxonomy wasn't added to 'Discovery Rule' filter (roles). Is this an API\GUI issue now? if not, then it doesn't solve the requirement. P.s this satellite was upgraded from 6.0.4 to 6.1 and then to 6.1.1 . Sorry for the delay, currently the only supported way of setting taxonomy for discovered hosts are: 1) Global setting discovery_location/organization under Settings->Discovered (for all incoming hosts). 2) Providing custom facts named organization/location. This must be set via custom extension of the image and it can be only done programatically during the discovery phase. Unfortunately, either via rules or when you do manual provisioning (Org/Loc on the Provision host screen is disabled) it is not possible to change taxonomy. This is a valid RFE. One extra thing: When global setting is not set (empty value), discovery uses the org/location for the subnet of the host (if there are multiple values, it takes the first one). *** Bug 1253025 has been marked as a duplicate of this bug. *** WORKAROUND: Org/Loc of discovered hosts can be changed via mass actions - select one or more discovered hosts via checkboxes on the left, then click on Select Action -> Assign Organization. "One extra thing: When global setting is not set (empty value), discovery uses the org/location for the subnet of the host (if there are multiple values, it takes the first one)." This might actually work in my case, as typically the org's have different subnets. "WORKAROUND: Org/Loc of discovered hosts can be changed via mass actions - select one or more discovered hosts via checkboxes on the left, then click on Select Action -> Assign Organization." It still requires a user to belong to discovered hosts org/loc. And it might create problems when multiple users from different org/loc will have such role. "One extra thing: When global setting is not set (empty value), discovery uses the org/location for the subnet of the host (if there are multiple values, it takes the first one)." this doesn't work Alexander, you are right and we've fixed that already. Will be part of upcoming errata of 6.1. Here is the relevant bug: https://bugzilla.redhat.com/show_bug.cgi?id=1258521 Moving to POST since upstream bug http://projects.theforeman.org/issues/4426 has been closed Let me explain. Two issues were reported in this BZ: 1) Missing taxonomy for discovery rules. We have added these in upstream and Satellite NEXT will contain this. 2) Allow changing taxonomy on Provision host screen. This is design limitation of how Discovery is implemented today, but we implemented a workaround or new screen called QUICK PROVISION which will be coming out as part of Satellite NEXT as well. It allows quick provisioning (assign hostgroup, taxonomy, submit). This was fixed in http://projects.theforeman.org/issues/4426 (associated with this BZ). Now the original issue that Provision host has taxonomy fields disabled that's part of bigger refactoring which is not yet planned. We are tracking this as: http://projects.theforeman.org/issues/14035 https://bugzilla.redhat.com/show_bug.cgi?id=1324539 So I suggest to close this one, please associate customer cases with bug 1324539 if they want to track this RFE. QA NOTES: Verify that taxonomy for discovery rules works. Verify that quick provision screen works and sets correct taxonomy. One more note, in Satellite 6.3 there will be possibility to set taxonomy also this way: 1) Find discovered host, click Provision 2) On the Quick provision modal screen select taxonomy 3) Click on Provision (not Quick provision) 4) Edit details, note the taxonomy was set correctly now (but it's disabled) 5) Submit QA NOTES: Please verify this as well. Verified. Version tested: Satellite 6.3 Snap 12 See the attached video, it tests steps in Comment 16 https://bugzilla.redhat.com/show_bug.cgi?id=1245642#c16 Created attachment 1317036 [details]
Provision discovered hosts w/ taxonomies
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-2018:0336 |