Bug 1523663

Summary:	Unexpected error encountered while accessing policy event timeline in availability zones
Product:	Red Hat CloudForms Management Engine	Reporter:	thiebaut fischer <tfischer>
Component:	UI - OPS	Assignee:	Zita Nemeckova <znemecko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dave Johnson <dajohnso>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.8.0	CC:	cpelland, gblomqui, hkataria, ikaur, jhardy, mpovolny, obarenbo, simaishi, znemecko
Target Milestone:	GA	Keywords:	TestOnly, ZStream
Target Release:	5.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.10.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1531308 1533167 1549650 (view as bug list)		Environment:
Last Closed:	2018-06-21 21:21:37 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:	1531308, 1533167, 1549650

Description thiebaut fischer 2017-12-08 14:52:53 UTC

Description of problem:
Getting the error page when selecting the policy event timeline of an availabilty zone. Tested/found on Amazon cloud

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


How reproducible:
Always

Steps to Reproduce:
1. Setup Amazon Cloud provider
2. Create a policy 
3. Create an instance
4. assign the policy to the instance, execute it
5. go to the instance's availability zone/timeline
6. select policy events, all categories/click apply

Actual results:
Getting on the error page

Expected results:

Should see the TL and the policy events of the instance


Additional info:

Comment 2 thiebaut fischer 2017-12-11 09:37:34 UTC

Bug also found on Azure

Comment 3 Zita Nemeckova 2017-12-19 13:29:55 UTC

GregB,

it seems that you should know more about this one. In UI you cannot access Timelines in Availability zones for Policy events but you can do it for ems_events. It crushes on unknown column availability_zone_id for policy_events. You introduced availability_zone_id for ems_events but not for policy_events. Either it's missing from policy_event or UI shouldn't show timelines for Availability zones. Can you assign it to someone or let me know if it shouldn't be shown in UI?

Thanks,
Zita 

PS: I'm not sure it's a blocker as it doesn't work in Fine or Darga either.

Comment 4 Greg Blomquist 2017-12-19 19:43:01 UTC

Heh, if this goes all the way back to Darga, then it's definitely a long standing bug that no one has ever hit.  I agree we should remove the blocker flag.

As far as fixing it, I'm guessing that there's some work involved in making sure that Availability Zones play nicely with policies at all.

My suggestion is to not show timelines for Availability Zones.  And, then we would later revisit this to make sure Availability Zones work with Policies and re-enable timelines for Availability Zones.

I'll run this by PM for validation before re-assigning back to UI for hiding the timelines.

In the meantime, Thiebaut, can you tell us the policy you assigned to the instance?  A screenshot of the policy page would be most useful.

Comment 5 thiebaut fischer 2017-12-20 11:00:43 UTC

Hello, 

I don't have a screenshot, but i can tell you what was inside, it is very easy:
condition: if vm/instance power state is off
action: power off/powering off -> run smart state analysis

Comment 6 Greg Blomquist 2018-01-02 18:47:16 UTC

Zita,

I asked Loic if we could remove blocker from this BZ, but he said "no".

Is there an easy way to hide to ability to hide the timelines options for Availability Zones?  If so, I think that's what we should do for now.

Comment 7 Zita Nemeckova 2018-01-02 18:59:27 UTC

Greg,

it should be easy. I will work on it asap. Thanks for info.

Comment 8 Zita Nemeckova 2018-01-03 13:35:15 UTC

https://github.com/ManageIQ/manageiq-ui-classic/pull/3154

Comment 9 Greg Blomquist 2018-01-03 15:10:34 UTC

*** Bug 1528559 has been marked as a duplicate of this bug. ***