Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1398276 - policy timelines breaks down if timelines settings are changed
policy timelines breaks down if timelines settings are changed
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
5.6.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.6.4
Assigned To: Harpreet Kataria
Ievgen Zapolskyi
ui:timelines
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-24 06:30 EST by Ievgen Zapolskyi
Modified: 2017-03-09 12:04 EST (History)
6 users (show)

See Also:
Fixed In Version: 5.6.4.0
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-09 12:04:31 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: Bug
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core


Attachments (Terms of Use)
screenshot (186.39 KB, image/png)
2016-11-24 06:30 EST, Ievgen Zapolskyi
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0474 normal SHIPPED_LIVE CFME 5.6.4 bug fixes and enhancement update 2017-03-09 17:03:14 EST

  None (edit)
Description Ievgen Zapolskyi 2016-11-24 06:30:58 EST
Created attachment 1223795 [details]
screenshot

Description of problem:
When I open Policy Timelines f.e. for vm first time, I see appropriate policy events. However, when I change any settings like Interval or Event Type (uncheck and check "Check All"), timeline control disappears from the view.
The only way to get Policy Events rendered correctly again is switching between Management and Policy events. (See screenshot)

Version-Release number of selected component (if applicable):
5.6.3.2

How reproducible:
100%

Steps to Reproduce:
1. Add some provider to appliance (I used vpshere55)
2. Create some Policy Profile + Policy with Conditions and Events (my conditions and events were related to changing VM Power State)
3. find any available vm
4. Assign just created policy profile to this vm
5. Power off and power on this vm
6. check that appropriate policy events showed up in policy_events table
7. Open Timelines for that vm
8. Change Timelines to display policy events
9. try to change Interval or uncheck and check again Event Type->Check All checkbox 

Actual results:
After 8 step, Policy Timelines displays appropriate events.
After 9 step, Timelines control disappears from Timelines view.
Reopening timelines doesn't help. Policy Timelines will be rendered correctly only after switch Management Events.

Expected results:
correct rendering of Policy Timelines when filtering settings are changed.
Comment 5 Harpreet Kataria 2016-11-30 17:08:27 EST
Please ignore https://bugzilla.redhat.com/show_bug.cgi?id=1398276#c4, created Darga only PR here: https://github.com/ManageIQ/manageiq/pull/12933
Comment 6 CFME Bot 2016-12-13 22:21:34 EST
New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/ebe93aff1d158b4ba7e8ffb52c09363cf37960e1

commit ebe93aff1d158b4ba7e8ffb52c09363cf37960e1
Author:     Harpreet Kataria <hkataria@redhat.com>
AuthorDate: Wed Nov 30 16:31:11 2016 -0500
Commit:     Harpreet Kataria <hkataria@redhat.com>
CommitDate: Wed Nov 30 17:05:01 2016 -0500

    Generate timelines if flash message was not set.
    
    Previously this code was not re-generating Policy timelines when Policy timelines options were changed on the screen. This issue does not exist on upstream or EUWE, it was addressed with PF timeline upgrade changes
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1398276

 app/controllers/application_controller/timelines.rb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Comment 8 errata-xmlrpc 2017-03-09 12:04:31 EST
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-0474.html

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