Bug 1686762
Summary: | Internal server error while creating schedule with 'EVM Group' | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Ganesh Hubale <ghubale> |
Component: | UI - OPS | Assignee: | Hilda Stastna <hstastna> |
Status: | CLOSED ERRATA | QA Contact: | Ganesh Hubale <ghubale> |
Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | medium | ||
Version: | 5.10.1 | CC: | bmidwood, dmetzger, hkataria, lavenel, mpovolny, obarenbo, simaishi |
Target Milestone: | GA | ||
Target Release: | 5.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.11.0.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-12 13:36:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | Bug | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1730750 |
Comment 5
Hilda Stastna
2019-03-08 16:34:00 UTC
Steps to reproduce: Go to Configuration > Settings > Schedules Configuration > Add a new Schedule For Action, choose Automation Tasks For Type, choose EVM Group or Tenant => error New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/306358693b869d8d8ba07b9c7bc61a912bb95a5e commit 306358693b869d8d8ba07b9c7bc61a912bb95a5e Author: Hilda Stastna <hstastna> AuthorDate: Mon Mar 11 09:58:03 2019 -0400 Commit: Hilda Stastna <hstastna> CommitDate: Mon Mar 11 09:58:03 2019 -0400 Fix internal server error while creating schedule Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1686762 Fix the error while creating schedule with EVM Group/Tenant option app/controllers/ops_controller/settings/automate_schedules.rb | 18 +- 1 file changed, 16 insertions(+), 2 deletions(-) Hi, Are we back-porting this fix for 5.10z because this issue is still reproducible on 5.10.6.1. Let me know, if we already have clone of this BZ for 5.10 Thanks, Ganesh 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:4199 |