| Summary: | AHC matching does not respect system type | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Roland Wolters <rwolters> |
| Component: | ahc-tools | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Shai Revivo <srevivo> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 (Kilo) | CC: | aschultz, bfournie, hbrock, jslagle, mburns, rhel-osp-director-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-13 08:57:31 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: | |
AHC is no longer supported. It has been superseded by automatic profile tagging - https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/#appe-Automatic_Profile_Tagging |
Description of problem: Currently the AHC report generates a lot of information. However, AHC match only checks for a limited subset of information of the AHC report. Fields like the system type ("Dell RX730") are identified by the AHC report but cannot be used to match systems against. The AHC matching should be extended to be able to match against all available information of an AHC report. Version-Release number of selected component (if applicable): RHELOSP 7 How reproducible: Create an AHC report, check for system type, and see that AHC does not match against that information piece. Steps to Reproduce: 1. create report file like [ ('system', 'product', 'name', 'Model Type'), ] 2. run ahc-match Actual results: It is not possible to match against system types and other information in the AHC report. Expected results: All fields listed in an AHC report should be available for matching. Further information: This problem came up when a customer used rather similar, but not identical machines for different types. The easiest would have been to differentiate by system type, which was identified by the ahc tools - but a matching wasn't possible. Thus we had to use work arounds to match the machines.