Description of problem: active ansible services are not displaying details on selection Version-Release number of selected component (if applicable): 5.8.3 How reproducible: all the time Steps to Reproduce: 1. go to services > my services 2. select a puppet service 3. Actual results: no data is loaded Expected results: able to see the details of the service Additional info: reproducer from customer database available
https://github.com/ManageIQ/manageiq-ui-classic/pull/4150
New commit detected on ManageIQ/manageiq-ui-classic/fine: https://github.com/ManageIQ/manageiq-ui-classic/commit/e7b41e9474633571ad6dd757617f4fbcd565f0e7 commit e7b41e9474633571ad6dd757617f4fbcd565f0e7 Author: Hilda Stastna <hstastna> AuthorDate: Fri Jun 15 08:46:30 2018 -0400 Commit: Hilda Stastna <hstastna> CommitDate: Fri Jun 15 08:46:30 2018 -0400 Call new raw_stdout in haml to fix displaying Child Services Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1590761 Call the new raw_stdout method in haml to fix displaying Child Services especially if Embedded Ansible role is not active. Define provision_job and retirement_job to make the code more readable. app/views/service/_svcs_show.html.haml | 13 +- 1 file changed, 7 insertions(+), 6 deletions(-)
Hi @Felix, I tried this with, 1. creating parent service with VMware type 2. creating child service with Ansible Playbook type 3. assigning child service to parent via rail console but it is not getting added, do you mean to create services from rail console? I also had discussion with @Hilda but I am not so clear on usecase you have mentioned here. Can you provide us proper steps to reproduction? Thanks in advanced!
Fixed in Version 5.8.5.0.20180821175127_9cfc0ea. I tried with restoring db from reproducer env, it works well! Thank you!
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:2745