Bug 1722817 - Custom Button on the VM/Instance not able to get $evm.root["vm"]
Summary: Custom Button on the VM/Instance not able to get $evm.root["vm"]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - Service
Version: 5.10.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: GA
: 5.10.6
Assignee: Martin Hradil
QA Contact: Nikhil Dhandre
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1687061
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-21 12:03 UTC by Satoe Imaishi
Modified: 2019-11-19 22:36 UTC (History)
13 users (show)

Fixed In Version: 5.10.6.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1687061
Environment:
Last Closed: 2019-07-02 04:33:28 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1644 0 None None None 2019-07-02 04:33:31 UTC

Comment 2 CFME Bot 2019-06-21 12:17:04 UTC
New commit detected on ManageIQ/manageiq-ui-service/hammer:

https://github.com/ManageIQ/manageiq-ui-service/commit/5fe64d26c33c6e1af15b6194fd54cd2b268f4096
commit 5fe64d26c33c6e1af15b6194fd54cd2b268f4096
Author:     Harpreet Kataria <hkataria>
AuthorDate: Fri May  3 11:24:30 2019 -0400
Commit:     Harpreet Kataria <hkataria>
CommitDate: Fri May  3 11:24:30 2019 -0400

    Merge pull request #1542 from himdel/bz1687061-custombutton

    VM custom button dialog - use the VM instead of the parent service

    (cherry picked from commit 61c583c5a7cf63d86a6c30166f029559e060e8f1)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1722817

 client/app/states/services/custom_button_details/custom_button_details.state.js | 4 +
 client/app/states/services/custom_button_details/custom_button_details.state.spec.js | 291 +-
 2 files changed, 176 insertions(+), 119 deletions(-)

Comment 6 errata-xmlrpc 2019-07-02 04:33:28 UTC
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-2019:1644


Note You need to log in before you can comment on or make changes to this bug.