Bug 1288146
| Summary: | all events on timeline appear only under the "power activity" event type | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Dafna Ron <dron> | ||||||
| Component: | UI - OPS | Assignee: | Mooli Tayer <mtayer> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.5.0 | CC: | cpelland, epacific, fsimonce, hkataria, jhardy, jprause, mpovolny, mtayer, nachandr, obarenbo, srevivo | ||||||
| Target Milestone: | GA | ||||||||
| Target Release: | 5.6.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | container | ||||||||
| Fixed In Version: | 5.6.0.0 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1289623 (view as bug list) | Environment: | |||||||
| Last Closed: | 2016-06-29 15:17:06 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1289623 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1103631 [details]
'status' events
We do have other types of events (see screenshot) This is our current list of events by categories; my suggestions in footnotes General Activity: POD_NODESELECTORMISMATCHING[1] Network: POD_HOSTPORTCONFLICT Power Activity: NODE_REBOOT POD_SCHEDULED[2] POD_FAILEDSCHEDULING[1] REPLICATOR_SUCCESSFULCREATE[2] REPLICATOR_FAILEDCREATE[1] CONTAINER_CREATED [2] CONTAINER_KILLING [1] CONTAINER_STARTED [2] CONTAINER_STOPPED [2] "Alarm/Status change/Errors": NODE_NODEREADY NODE_NODENOTREADY NODE_FAILEDMOUNT [3] NODE_INVALIDDISKCAPACITY [3] POD_FAILEDVALIDATION [1] POD_DEADLINEEXCEEDED [1] POD_FAILEDSYNC [1] POD_INSUFFICIENTFREECPU [1] CONTAINER_UNHEALTHY [1] "Storage": POD_OUTOFDISK POD_INSUFFICIENTFREEMEMORY Other categories: "Creation/Addition" "Configuration/Reconfiguration" "Deletion/Removal" "General Activity" "Import / Export" "Migration/Vmotion" "Snapshot Activity" "Alarm/Status change/Errors" [1] Move to Alarm/Status change/Errors [2] Move to Creation/Addition [3] Move to Storage submitted upstream: https://github.com/ManageIQ/manageiq/pull/5823/files >> John Prause 2015-12-17 09:05:04 EST
>> Status: POST → MODIFIED
I believe this was not merged
Mooli shouldn't this be on POST? (In reply to Federico Simoncelli from comment #5) > Mooli shouldn't this be on POST? right: merged upstream: https://github.com/ManageIQ/manageiq/pull/5823 (In reply to Mooli Tayer from comment #6) > (In reply to Federico Simoncelli from comment #5) > > Mooli shouldn't this be on POST? > > right: > merged upstream: > https://github.com/ManageIQ/manageiq/pull/5823 Can you move it to POST? (same for any other 5.6.0 BZ you may have in this state) 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-2016:1348 |
Created attachment 1101857 [details] logs and screenshots Description of problem: All the events in my setup appear under "power activity" while the events range form create to delete for example. Version-Release number of selected component (if applicable): cfme-5.5.0.13-1.el7cf.x86_64 How reproducible: 100% Steps to Reproduce: 1. create pods and containers 2. navigate to providers -> select the provider -> select the event type power activity 3. navigate to providers -> select the provider -> select the event type creation/Addition 4. navigate to providers -> select the provider -> select the event type power activity -> select the event -> look at the event details **this happens for pods and container pages as well** Actual results: All the events appear under the same type which is power activity Expected results: they should appear under the appropriate event Additional info:screenshot and logs