Bug 1287158
Summary: | [RFE] Display MIQ/Red Hat Automate domain versions in the UI | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Chris Pelland <cpelland> |
Component: | Automate | Assignee: | mkanoor |
Status: | CLOSED ERRATA | QA Contact: | Ramesh A <rananda> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.5.0 | CC: | cpelland, dajohnso, fdewaley, jhardy, jocarter, jprause, mfeifer, mkanoor, obarenbo, snansi, soconcar, tfitzger |
Target Milestone: | GA | Keywords: | FutureFeature, ZStream |
Target Release: | 5.5.2 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | 5.5.2.1 | Doc Type: | Enhancement |
Doc Text: |
The new version of CloudForms Management Engine now displays the MIQ and Red Hat Automate domain versions in the user interface. This provides an easy way to lookup the MIQ and Red Hat domain versions after updating the CloudForms rpm packages. This is necessary as the admin needs to reset the automate model to update the MIQ and Red Hat domains after the CloudForms rpm package update.
|
Story Points: | --- |
Clone Of: | 1283037 | Environment: | |
Last Closed: | 2016-02-10 15:20:32 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: | 1283037 | ||
Bug Blocks: |
Comment 1
mkanoor
2015-12-03 22:12:55 UTC
Good to go. Verified and working fine in 5.5.2.1.20160114044944_395c086. Steps followed to verify this issue. 1. SSH into the appliance 2. cd vmdb/db/fixtures/ae_datastore/RedHat/System/About.class 3. Edited the default_value in __class__.yaml 4. In web-ui navigated to Automate==> Explorer ==> Datastore 5. Click on Datastore and RedHat Displays below mentioned message: "RedHat domain: Current version - 5.5.2.1, Available version - 5.5.2.5" 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/RHBA-2016:0159 |