Bug 1363774
| Summary: | Reset Automate Datastore text misleading | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Christian Jung <cbolz> |
| Component: | Automate | Assignee: | Patrik Kománek <pkomanek> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Falešník <mfalesni> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.6.0 | CC: | benglish, gmccullo, hkataria, jhardy, mfalesni, mkanoor, mpovolny, obarenbo, simaishi, tfitzger |
| Target Milestone: | GA | ||
| Target Release: | 5.7.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | automate | ||
| Fixed In Version: | 5.7.0.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-04 12:58:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Christian Jung
2016-08-03 14:07:10 UTC
Suggested change: "Reset all components in the following domains: XXX, YYY" We will need a method in the MiqAeDatastore model to return the names which need to be read from the YAML files stored in fixtures/ae_datastore directory. Patrik - I would like to refactor the code in reset_to_defaults to create a new method that yields the domain_file. This new method can then be used in reset_to_defaults as well as a new method that returns the Domain name that is stored in the domain_file (which is yaml). The code I am referring to is here: https://github.com/ManageIQ/manageiq/blob/master/lib/miq_automation_engine/models/miq_ae_datastore.rb#L167 solved in PR: https://github.com/ManageIQ/manageiq/pull/10899 *** Bug 1373996 has been marked as a duplicate of this bug. *** Verified in 5.7.0.1 The text is now more descriptive. 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://rhn.redhat.com/errata/RHBA-2017-0012.html |